After upgrading to v3.1, I have not been able to use the customConfig configuration for the life of me....
I have created a testbed website that contains just an index.html file, a config.js file (the external custom config), and the ckeditor folder from the 3.1 download. Over 95% of the code was taken straight from the Configurations documentation.
The strangest thing is that FireBug records no javascript errors or anything....in addition, I have tested it in Firefox v3.6b5 and Chrome v4.0.288.1 dev, both are not respecting the external configuration file. I just installed IE8 for the purpose of testing in that browser and I can't even get CKEditor to load....sigh just not my day.
I have attached the full index.html and config.js file to this post, but here are the pertinent snippets:
In index.html, I included the ckeditor.js script and a textarea:
<textarea name="editor1"></textarea>
<script type="text/javascript">
window.onload = function ()
{
CKEDITOR.replace("editor1",
{
customConfig: 'config.js'
});
};
</script>
Re: customConfig Issues
<textarea name="editor1"></textarea> <script type="text/javascript"> window.onload = function () { CKEDITOR.replace("editor1", { customConfig: '../config.js' }); }; </script>Just remember that the path to the customConfig is relative to the CKEditor script, so you should have looked at the Net panel in Firebug to check for a 404
Re: customConfig Issues
Strange....that did resolve the issue. What strikes me as odd though is that this broke after the update to v3.1. Using v3.0.2 with the same exact config resulted in a functioning external config (that is, the path being relative to the file containing CKEditor). After just updating only ckeditor, allow external configurations broke. Was this a change in the latest version? I can't believe it was, but I am kind of wondering why it would work prior to v3.1...
Well thanks for your help, I was right, it was a stupid silly easy thing to resolve, just sorry to have wasted your time with it!
Re: customConfig Issues