Toolbarset changes and additions ignored [#299404]

If I add a new toolbarset to fckeditor.config.js then I can select that toolbarset as the Toolbar for an FCKeditor profile. For example:

FCKConfig.ToolbarSets["ReallyBasic"] = [
['Bold','Italic','-','OrderedList','UnorderedList','-','Link','Unlink']
] ;

However, when a user of the role to which this profile is associated visits a page with an appropriate textarea, they get the following message:

Toolbar set "ReallyBasic" doesn't exist

Furthermore, if I edit a toolbarset in fckeditor.config.js, then these edits have no impact. For example, if I change

FCKConfig.ToolbarSets["DrupalBasic"] = [
['FontFormat','-','Bold','Italic','-','OrderedList','UnorderedList','-','Link','Unlink', 'Image']
] ;

FCKConfig.ToolbarSets["DrupalBasic"] = [
['Bold','Italic','-','OrderedList','UnorderedList','-','Link','Unlink']
] ;

the DrupalBasic toolbarset does not change!

I have emptied my browser's cache and Drupal's cache. But this has not helped.

Comments

Comment #1

Jorrit CreditAttribution: Jorrit commented 24 August 2008 at 19:24

Is is possible for you to check whether the fckeditor.config.js is actually loaded? for instance by looking up the access logs or using FireBug?

Comment #2

oldrobb CreditAttribution: oldrobb commented 24 August 2008 at 19:56

Status:

Active

» Closed (fixed)

Thanks for the pointer. I installed FireBug and that showed that the loaded script did not contain my changes. So I loaded the script URL directly in Firefox and forced a reload - at which point my changes appeared. So I went back to the page, reloaded, and now it worked as it should.

It seems very odd, given that I'd flushed my browser cache and my site's cache, and had even tried different browsers that had never visited the site before. But it looks like it must have got cached somewhere along the route.

So it seems fine now. Thanks for your help.

Comment #3

patrickharris CreditAttribution: patrickharris commented 27 August 2008 at 04:59

Thanks robbm - I had exactly the same problem in Firefox, and only loading the script URL directly and forcing a reload as you described fixed things.

Comment #4

filiptc CreditAttribution: filiptc commented 2 September 2008 at 16:20

Status:

Closed (fixed)

» Postponed (maintainer needs more info)

Exactly the same problem. Where is this js cached? This is very confusing. As robbm said, even browser cache flushing does not work. Is there any way to avoid this behavior from within code? If not, consider adding a note to readme or to fckeditor.config.js.

Comment #5

wwalc CreditAttribution: wwalc commented 4 September 2008 at 11:23

Status:

Postponed (maintainer needs more info)

» Fixed

Ok, this may be quite an annoying thing, especially if user is unaware of that someone added new toolbar to FCKeditor configuration and that he should clear his cache to use FCKeditor properly. I have mentioned about this in documentation and filemtime() is appended to the fckeditor.config.js file to protect against caching. Let's see if that helps.

Another idea is to point FCKeditor to php file that includes fckeditor.config.js, but before that also sends special headers telling browsers and proxy servers to not cache this file, anyway let's try this simpler approach first.