Defining Configuration In-Page

where I insert configurations?

The best way to set the CKEditor configuration is in-page, when creating editor instances. This method lets you avoid modifying the original distribution files in the CKEditor installation folder, making the upgrade task easier.

example:

CKEDITOR.editorConfig = function( config )
{
config.language = 'fr';
config.uiColor = '#AADC6E';
};

In what document do I enter the text string?

Sat, 05/07/2011 - 23:49

datalink

Joined: 18/10/2007

Posts: 149

Re: Defining Configuration In-Page

You can use config.js as default for ALL of your editors, or better set your config to the replace function after your textarea.

Tue, 05/10/2011 - 11:04

Anna

Joined: 14/12/2010

Posts: 1369

Re: Defining Configuration In-Page

The best way to figure it out is to look at the source code of the samples from your CKEditor "_samples" folder.

You can define the configuration of a CKEditor instance by inserting the config values in the "replace" function that replaces your textarea element with the editor. Like, for example, here -- for the Autogrow plugin sample:

<script type="text/javascript">
//<![CDATA[
   CKEDITOR.replace( 'editor2', {
      extraPlugins : 'autogrow',
      autoGrow_maxHeight : 400
   });
//]]>
</script>

Where "editor2" is the ID of the textarea element that you are trying to replace.

This code will obviously be placed on the page that contains your textarea/ editor instance -- hence the "in-page" name.

Documentation Manager, CKSource

See CKEditor 5 docs, CKEditor 4 docs, CKEditor 3 docs, CKFinder 3 docs, CKFinder 2 docs for help.
Visit the new CKEditor SDK for samples showcasing editor features to try out and download!