Allow choice of ckeditor.config.js as per ckeditor.styles.js

+1 for this feature. I'm often using an existing admin theme like Rubik, so adding the config there does not make sense. Ideally I would be able to store ckeditor.config.js with my main site theme.

Allowing the ckeditor configuration to be modified, outside of the module directory, is essential for version controlled installations.

The current option of loading an alternate configuration file is problematic for several reasons.

1. Loading from the theme is the only option provided.
2. The theme is the least desirable location to place editor configuration because it has nothing to do with the theme and is problematic if multiple themes are used (e.g., administration theme, user selectable theme).
3. Loading toolbar options in the ckeditor profile settings doesn't work if the admin theme is different than the theme hosting the configuration.

I propose to add an option to the global settings which captures a custom path for ckeditor.config.js.

Attached is a first run at a patch which implements such a setting.

The patch changes some of the field descriptions to better explain how to create a custom configuration.

Forgot to change status

Can someone please comment on my patch? I'd like to gauge if my approach is reasonable or if I will have to fork the module locally so future module updates won't destroy my solution.

I didn't review this patch, but currently there is an option "Load ckeditor.config.js from theme path". In my site, I put both ckeditor.config|style.js in my theme folder and it works.

@jcisio, I explained in comment #2 why the theme path option is insufficient.

#6 I'm using Garland in admin and my custom theme for "frontend", and it currently works in my frontend. It's bizzare, huh?

@jcisio, my patch attempts to offer a more intuitive (for typical site builders) and rational (content editor settings are not theme related) solution. The help text changes may not be perfect but discussion can resolve that. There may be an existing, hackish, solution but it is far from ideal. I am happy to continue working on the patch to bring it to an ideal state if current maintainers lack the time to do anything further than commit it.

I'm so +1 on this. I've been trying to find a way to specify, just as you say, a unique config file for each profile in CKEditor. Each profile can be assigned a unique role. This means that I can have a profile for each role which specifies unique file paths, template snippets, styles for the editor, and anyhing else specific to that role.

This would be super powerful. Can this be done now any other way? I tried adding a custom config path to the bottom textarea of each profile, but some commands just don't work in that box.

Subscribing.

I just updated CKEditor to 6.x-1.4 and now my customConfig path no longer works. This feature is now critical or this regression needs to be fixed. For those interested, below are my custom javascript settings to load the editor configuration from the "default" site path.

customConfig = '../../../default/ckeditor.config.js';
config.toolbar = 'Custom';

Pls try to update to last DEV version and write than does it help or not... It was some bugs in 6.x-1.4 and all we fix in last DEV version.

Greetings

Sorry for the delay but I just updated to -dev and the bug is still present.

In ckeditor 6.x-1.4 the contents of my custom javascript configuration was this.

customConfig = '../../../default/ckeditor.config.js'
config.toolbar = 'Custom'

After updating this results in the editor loading the default profile. I tried adding semi-colons as they now seem to be required but that causes the editor to fail to load entirely. It looks like the "customConfig" line no longer works because only commands that begin with "config." are caught by the new regex pattern.

Seem to have same "bug" here. (Personally: Forking to custom version of module in sites/example.com/modules/ckeditor/~ until worked out.) Thanks!

I'm sticking with ckeditor 1.3 until this regression is fixed. I don't have time to roll a patch to fix this at the moment.

As of 6.x-1.8 it is possible to configure a custom toolbar and most other custom features in the js_conf field. However, I still have a need to alter CKeditor event behavior and this can only be done, without hacks, by using a customized ckeditor.config.js file which is no longer possible. Some modifications which I need to do are:

• alter whitespace rules for HTML source for certain elements
• alter ckeditor dialogs

I was using the CKEDITOR.on() method in ckeditor.config.js to do this.

CKEDITOR.on( 'instanceReady', function(ev) {
  els = ['p','li','h1','h2','h3','h4','h5','h6','caption','div','td','th'];
  for (i in els) {
    ev.editor.dataProcessor.writer.setRules(els[i], {
      indent : false,
      breakBeforeOpen : false,
      breakAfterOpen : false,
      breakBeforeClose : false,
      breakAfterClose : true
    });
  }
});

Removing the ability to use the "customConfig" parameter in js_conf and not providing this ability somewhere else is a regression that must be fixed.

@tangent,
I am not sure if this is what you want to achieve, but try add config.customConfig='path/to/your/ckeditor/custom/config.js'; in "Custom JavaScript configuration" option of CKEditor profile.
In this way you should load your customized config (http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.config.html#.cust...) to CKEditor. I tried this solution with your attached code at http://drupal.org/node/887896#comment-5214794 and it works. Please check and write if this is what you want to achieve.

@michal_cksource,

That option does indeed work. I believe I had tried that syntax in the past and it didn't work but it does work now. This option is not for the faint of heart and should be well documented if it will remain like this but it does work. Thanks for the tip.

@tangent
I think this option can stay in this way. Remember that only more 'advanced' user will try to use something like this. Of course documentation can be better.