When first time deploy, the ckeditor-rails will create a digested config.js and no-digested config.js. The browser will cache the no-digested config.js while it hit by someone first time. If the content of config.js is changed again, the browser will still use the old no-digested config.js. This is a bug.
There are two ways to resolve this issue.
monkey patching the value of customConfig in ckeditor.js while compiling the ckeditor.js by parsing the asset manifest file.
overwrite the CKEDITOR.config.customConfig by rails asset file path helper in a js.erb file. The only consideration is where to put this file.
When first time deploy, the ckeditor-rails will create a digested config.js and no-digested config.js. The browser will cache the no-digested config.js while it hit by someone first time. If the content of config.js is changed again, the browser will still use the old no-digested config.js. This is a bug.
There are two ways to resolve this issue.
customConfiginckeditor.jswhile compiling the ckeditor.js by parsing the asset manifest file.CKEDITOR.config.customConfigby rails asset file path helper in a js.erb file. The only consideration is where to put this file.