murraybiscuit

thanks for the response michal.

the point is that i don’t want to have to back the config file up or fiddle in the plugin directory. if i’m building a theme/sites for multiple clients, it’s easier for me to just install a theme, put all the config/styles stuff in the theme and point the plugin to it. that way, i could create a theme, tell a client to install ckeditor plugin, and all of my customisations for that theme become available without them having to use ftp, and if they delete or update the plugin, there’s no risk of config being overwritten.

by default, there would be a search logic to find config/styles/editor-css files:
– check user specified directory
– if doesn’t exist, check current theme root
– if doesn’t exist, check plugin root.

Then you just add a field where the user can specify the config dir in the frontend and the script figures out the rest.

hope that makes sense.