2015-01-13, 04:56:07
The plugin turns it off, not you.
Its a kludge, there is no way to stop the ckeditor code from executing, so the plugin disables the editor before so that it doesn't insert the cke code, then we insert our own js to bind to post-content
The alternative is to destroy ckeditor after it initializes, but thats silly since it will still load and be slow and flash for a second.
This will be better in 3.4 and allow removing ckeditor entirely and injecting your own editors for all instances.
Its a kludge, there is no way to stop the ckeditor code from executing, so the plugin disables the editor before so that it doesn't insert the cke code, then we insert our own js to bind to post-content
The alternative is to destroy ckeditor after it initializes, but thats silly since it will still load and be slow and flash for a second.
This will be better in 3.4 and allow removing ckeditor entirely and injecting your own editors for all instances.