In a middle of a updgrade, I'd forgoten to remove de adapter from 3.4 when installing 4.0. So... it worked!
I'd realized that when I was removing the old adapter and suddenly I received a jQuery error. So, you can copy the old adapter and write something like:
If you will check examples in the download package, there is an example how to make it work by just adding a class to textarea + including main ckeditor.js file.
We have a plugin which helps integrate CKEditor onto the page with jQuery, but it goes further and also integrated it with the form plugin (for ajax submissions) and the validation plugin.
I was wondering this aswell,
I was wondering this aswell, however the old jquery.js for 3.6 seems to work aswell for 4.0.
+1
+1
I've found a way... []
In a middle of a updgrade, I'd forgoten to remove de adapter from 3.4 when installing 4.0. So... it worked!
I'd realized that when I was removing the old adapter and suddenly I received a jQuery error. So, you can copy the old adapter and write something like:
$('textarea.editor').ckeditor(function() {}, {skin : 'kama', toolbar: 'crToolbar'});
The configuration is available as usual, in the above example I've used a custom toolbar.
[]'s
Rafael Goulart from Brazil.
There is no need for that ...
If you will check examples in the download package, there is an example how to make it work by just adding a class to textarea + including main ckeditor.js file.
CKEditor jQuery Plugin
We have a plugin which helps integrate CKEditor onto the page with jQuery, but it goes further and also integrated it with the form plugin (for ajax submissions) and the validation plugin.
Check it out: jQuery CKEditor Plugin
Or just use the official
Or just use the official jQuery adapter for v4. It's slated for CKEditor 4.2 but it's already available on GitHub:
https://github.com/ckeditor/ckeditor-dev/tree/major/adapters
Customer and Community Manager, CKSource
Follow us on: Facebook, Twitter, LinkedIn
If you think you found a bug in CKEditor, read this!
Better integration with jQuery plugins
There are a couple of reasons actually...
1. Our plugin loads CKEditor dynamically.
Our CMS uses this to to better integrate CKEditor with our dynamically generated forms.
2. Our plugin overrides the $.fn.val() function as well as other plugins
jQuery Form plugin and the jQuery Validation Plugin, both of which we need to submit the form data via ajax.