Creating editor even if seemingly incompatible

We just discovered, when a developer inadvertantly overrode their UA string in Chrome, that when CKEDITOR.env.isCompatible is false, the editor is not created at all. Is there any way to force the editor to always load, even if UA string sniffing fails?

Fri, 12/07/2012 - 10:16

fredck

Joined: 19/01/2007

Posts: 898

Force it!

Just force isCompatible to true at the top of your page, right after loading the ckeditor.js file:

<script>
	CKEDITOR.env.isCompatible = true;
</script>

Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn