As described in the Integration article, to make CKEditor work it is enough to include the
ckeditor.js file in your pages. However, there are some situations when the original editor file name may not be used:
- The file must be renamed, for any reason.
- The original editor script is merged with other scripts used in the page, to reduce the number of files being downloaded. This single file will also have a name that is different from
ckeditor.js. This is the most common case.
- You have yet another file named
ckeditor.jswhich is not placed in the editor installation directory.
In order to work correctly CKEditor needs to know where in the website it is installed. Thanks to that information the editor is able to load other resource files like skins, language files, plugins, etc. In other words, the editor installation path is needed.
By default, CKEditor is looking for the
ckeditor.js file in the
<script> tags present in the page in order to automatically retrieve its installation path. If it is not able to find it, just like in the cases presented above, the editor will simply not work.
The Solution: CKEDITOR_BASEPATH
When loading the editor script, CKEditor is looking for the global
CKEDITOR_BASEPATH variable. For example:
all_my_scripts.js file, at the start of it (or in any case — before the editor code).