The code uses path_to_theme() to check and load the fckeditor.config.js from the default theme directory when the "use config from theme path" option is on.

However, due to the nature of how the path_to_theme() function works, the path returned may not be always the path to the actual theme of the site/user.

This will prevent the module from loading the theme specific fckeditor.config.js in a seemingly random way.

Please see #194098: path_to_theme() returns path to module that calls it for more info, and also the path_to_theme() function description.

Two solutions comes to mind:

  1. Get the path to current theme using other methods. See and for some alternative ways that may work. This may be also done using drupal_get_path('theme', $conf['theme_default'])
  2. Replace the true/false switch with a text field where the admin can specify the URL path to the .js they want to use


flaviovs’s picture

Did some basic research and found the following workaround: disable "Load fckeditor.config.js from theme path" and put the following snippet in "Custom javascript configuration":

CustomConfigurationsPath = '/sites/';

Change the value inside the quotes to point to your fckeditor.config.js inside your theme directory (or any other .js that contains your FCKEditor configuration).

Jorrit’s picture

Status: Active » Fixed

Will be fixed in CVS, for version 6.x-2.x

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.’s picture

I am getting this problem in 6.x-2.1 - so does not appear to be fixed.’s picture

Hmm - maybe it is fixed. Been clearing caches I did not know I had, and I think it is now working as expected. Doing some more testing - if you do not hear back, it is okay.

Sorry if I caused any panic attacks :-)