CKEditor for jQuery

Posted by tobiasz.cudnik on Releases

The new jQuery Adapter is our first integration effort for popular JavaScript libraries. We're proposing features tightly integrated with jQuery, while not introducing too many new methods to it. This article illustrates it, including some sample code snippets.

Creating editor instances

To create editor instances, other than the usual CKEditor core script, you need to load the jQuery Adapter file in the page, in the following order:

<script type="text/javascript" src="/ckeditor/ckeditor.js"></script>
<script type="text/javascript" src="/ckeditor/adapters/jquery.js"></script>

At this point, any textarea, p or div element can be transformed into a rich text editor by simply using the ckeditor() method:

$( 'textarea.editor' ).ckeditor();

jQuery chaining can also be used:

$( '.section-x' )
    .find( 'textarea.editor' )
    .find( 'a' )
        .addClass( 'mylink' )

The ckeditor() is the main method in the jQuery adapter. It accepts two optional parameters:

  1. A callback function to be execute when the editor is ready;
  2. Configuration options specific to the created editor instance.

The configurations options are passed through a simple object containing properties, each one related to a specific editor setting.

    .ckeditor( function() { /* callback code */ }, { skin : 'office2003' } );

The "this" reference inside the callback function points to the the CKEDITOR.editor object representing the editor instance.

Code interaction with editor instances

As soon as an editor instance is ready (after the above callback call), the ckeditorGet() method can then be used to retrieve a CKEDITOR.editor object that represents an editor instance. For example:

var editor = $('.jquery_ckeditor').ckeditorGet();
alert( editor.checkDirty() );

Because setting and retrieving the editor data is a common operation, the jQuery Adapter also provides the dedicated val() method:

// Get the editor data.
var data = $( 'textarea.editor' ).val();
// Set the editor data.
$( 'textarea.editor' ).val( 'my new content' );

This feature can be disabled by setting CKEDITOR.config.jqueryOverrideVal to false, before loading the adapter code.

For textareas, the editor will automatically return it's content back to the form when it is submitted. CKEditor also works with the official jQuery Form Plugin for AJAX based forms. It doesn't require anything from the developer side.

Events handling

Although CKEditor uses its own event system, there are four main events which we're exposing to the jQuery event system. All events use the event namespace, which is simply named ".ckeditor".

The following events are available:

  • instanceReady.ckeditor: fired when the editor is created, but before any callback being passed to the ckeditor() method.
  • setData.ckeditor: fired when data is set into the editor.
  • getData.ckeditor: fired when data is fetched from the editor. The current editor data is also passed in the arguments.
  • destroy.ckeditor: fired when the editor gets destroyed. It can be used, for example, to execute some cleanup on the page.

The editor instance is always passed as the first data argument for the listener. Both getData and setData are often used internally so listening to them should be done with care.

jQuery events DO bubble up through the DOM, so they can be listened selectively on certain parts of the document.


Share your thoughts about our very first adapter. What's the best feature? What's missing? Which other adapters should we work on? Stay in touch!


      Right, there's no need for ckeditorGet() although it's more intuitive and easier to document, so we've decided to provide it as the second one.

      Now you can get to editor instance binded to element by using .data( 'ckeditorInstance' ). Although running it right after ckeditor() method most probably will end in error.


      Such things as CKEDITOR_BASEPATH are not touched by adapter at all, but generally you have to set it before loading CKEditor.

      What "save" function you have on mind ?

    • There shouldn't be any change for CKFinder integration. You can still do it in 2 ways:

      1. Pass existing instance when it's available. Eg:

      $( 'textarea.editor' ).ckeditor( function()
        CKFinder.SetupCKEditor( this );

      2. Just use SetupCKEditor without passing editor instance, then it will be automatically attached to every new one (using CKEditor event system).

    • You should use callback always when there's the POSSIBILITY of editor not being ready. Mostly it's up to you to know your code and what's happening when. For eg in multi-step form, in 5th step when editor is instanced in 2nd, it's almost sure that editor IS ready then. On the other hand, when everything is binded to onDocumentReady, you should use callback.

      You can use callback even on existing editors and have them as many as you need to.

      Checking if editor is ready is not so useful information, because you shouldn't write 2 versions of the same code. Although you can check if editor is ready like this:

      $ 'ckeditorInstance' ) && ! $ '_ckeditorInstanceLock' )

      You are also able to know when editor get's instanced using:

      $el.bind( 'instanceReady.ckeditor', function( el ) { alert( ) } )