Add a field to set the ckeditor.config.js path as already in CSS and styles path

The last patch was generated from my Drupal root. Now, a patch from CKEditor module root, just maintaining the happiness of the maintainer and the drush make people :)

jcisio: Let me clear something about the patch. The point I made was that, in admin/settings/ckeditor/edit/PROFILE, I am not able to select a toolbar specified in my theme's (I use a different theme in admin section) ckeditor.config.js.

Then, I created the patch to read the toolbars names from the ckeditor.config.js in the site theme path. But only now I remembered that in D6, we can use the admin theme to edit nodes. This invalidates my patch.

Looking carefully in the profile edit page, I found that we could provide a more standard way to include a custom ckeditor.config.js. I already use the CSS path and Styles path fields to customize my CKEditor.

I think a field to set the ckeditor.config.js path, like the aforementioned fields, would provide a better way to allow the CKEditor customization and also would make the configuration options more homogeneous.

I made another patch to demonstrate my point of view with regarding this issue.

The main problem I see nowadays, it's that the admin interface gives good ways to CSS and config.styles.js overriding and any good option for ckeditor.config.js. Explaining:

When I choose "Load ckeditor.config.js from theme path", I am presented to a wide range of posibilities. If I choose a toolbar, (DrupalFull, e.g.):

• the CKEditor could not be presented, since I cannot guarantee that the ckeditor.config.js in the theme path will be a exact copy (or customized copy)
• if I use different themes for admin and site, the toolbars names listed in "Toolbars" field will not contains toolbar(s) defined in themes' ckeditor.config.js
• and finally, if a site have multiple themes and users can change them, probably they will see a textarea without the editor

However, if I choose all the related options to use the theme version (CSS, styles and ckeditor.config.js), I can have an unlimited number of specific CKEditors in a unique site.

Well, all of these is good in theory but if you try (with multiple themes, i.e.) create specific CKEditor profiles, you will never get your toolbar listed in the "Toolbar" field.

An abstract of this is that it creates too much unnecessary confusion (I'm also confused!). I preffer to create my profiles setting explicitly my CSS and Styles path (and if I need to support various themes, I just create more profiles). Then I found that setting the desired path for ckeditor.config.js would be good also.

This patch adds two new fields to the profile admin page ("Custom CKEditor configuration", "CKEditor configuration path") and removes the "Load ckeditor.config.js from theme path" field. It scans for toolbar definitions in the defined CKEditor configuration file also, then everyone can define new toolbars with different names (not restricted to Full, Basic, DrupalFull anymore).

The only drawback for this solution is that it need the CKEditor ckeditor.config.js path ("CKEditor configuration path") configured in order to scan the defined toolbars (if any).

The patch does not provide an update path (hook_update()). If this idea get approved, I can work it a little more and provide a more complete patch.

Ops, the patch was incorrect. Here we go again.

I found my patch wasn't replacing the placeholders (%h, %t, %m). Here is an updated patch. Tested against 6.x-1.6.

I found that I created a bug with the latest patch. Fixed in the new attached one.

In a couple of weeks I will release a project that uses this module and the patch. I hope the reason behind it will get more clear.

Updated patch to 6.x-1.8.

This patch is used in the Drüpen distribution that ships with a JavaScript file that configures the editor instance. For distributions, using the theme directory to ship this kind of file is not effective.

Updated patch to 6.x-1.11 (discosider this patch, see the next comment).

The right patch file. Updated to 6.x-1.11 version of the module.