When ckeditor is updated the file ckeditor.config.js is overwritten by the copy in the distribution. This file may contain customisations which will thus be lost. I know this is covered in "Upgrading Instructions" but it's a gotcha anyway.

It would be nice if some way to circumvent this was provided. For example the distribution version of this file could be called default.ckeditor.config.js which the installer would have to copy or rename initially. Alternatively if e.g custom.config.js existed ckeditor would use that in preference. I'm sure there's other ways too.

Thanks

Comments

jcisio’s picture

jcisio CreditAttribution: jcisio commented
Status: Active » Closed (works as designed)

If you change ckeditor.config.js, it'd better leave that file in your theme folder (and change settings so that CKEditor read in that folder).

Whatever you name ckeditor.config.js in the module folder, the "correct" upgrade process is to completely remove the module folder, then copy the new folder over. Your change won't be saved when you leave it in the module folder.