I have a situation where there is a 3rd party windows app that has ckeditor3 embedded in it. The app itself writes the config.js, so i don't have the ability to modify it because it just gets overwritten every time the editor initialises.
The author of the app is unwilling to modify their app to allow me to merge configs, so I need another way of making my changes. The ckeditor folder is available and I've already customised the templates successfully, so it's really only the config file being generated. Everything else is free for me to modify.
I'd like to first add "helper" stylesheets to the page that apply only while editing the document; these would not be saved into the final document, and contain various helpers and hacks to enable visibility of items during editing or to make them easier to access while editing (particularly with floated layouts, which render poorly in editors, but a crucial for me); i can alter the layout specific to editing but have the correct sheet render correct for display in the browser later on.
I also want to customise the appearance and icons on the toolbar.
Basically I need a way to let the editor initialise the default config (e.g. CKEDITOR.editorConfig = { ... stuff ... }) and THEN to apply my extra changes to it - e.g. change config.contentsCSS to an array with my extra styles in it, and modify the config.toolbar_Full array how I see fit.
/EDIT
http://docs.cksource.com/CKEditor_3.x/D ... ding_Order
does not do what I want. Unfortunately, the app rewrites config.js every time the editor is initialised. I then need to load my custom config page in order to overload some of the settings.
As I am unable to define a customConfig value in the default config.js, I can use the load stacking feature. Loading custom_config.js first then config.js doesn't help since it overwrites my settings.
So I am looking for the exact reverse of the situation that is described in the aforementioned documentation link.
A plugin to handle this might be in order, or a change in the source. Since the editor source stays the same and only the config.js is modified each time, touching the editor source as a safer option if required. I'm still hopeful that there is an easier solution.
Thu, 05/03/2012 - 05:11
#1