Closed Bug 610504 Opened 14 years ago Closed 14 years ago

Unable to invoke the editor on staging server

Categories

(developer.mozilla.org Graveyard :: General, defect)

defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: craigcook, Assigned: sheppy)

References

()

Details

When attempting to edit any page on the staged wiki, the WISYWIG editor fails to load completely, throwing the JavaScript error 'Toolbar set "MDC" doesn't exist.' This refers to a custom editor toolbar that should be configured in LocalSettings.php and possibly also in some FCKEditor configuration files.
Target Milestone: --- → 0.9.2
Assignee: nobody → jeremy.orem+bugs
assigning to oremj to have a look around for any FCKEditor config files we might need to compare.

oremj said the localsettings.php files on both stage9 and prod looked "about" the same... see http://oremj.pastebin.mozilla.org/843363

but it will be good to do a thorough review of that diff.  sheppy?
Sheppy, let me know if anything in the config is messed up.
Assignee: jeremy.orem+bugs → eshepherd
Looking at production, the MDC toolbar is set up in https://developer.mozilla.org/editor/fckeditor/editor/fckconfig.php

That PHP file just compiles a few separate JavaScript files, one of which seems to be a dynamic file I can't load directly so it may not even exist as a tangible file but is generated server-side. If it's generated server-side, I'm not sure how that file is populated with code.

And looking at the same config file on stage9 (https://developer-stage9.mozilla.org/editor/fckeditor/editor/fckconfig.php) note the comment at the top:

/* ETagCache Error: Missing file: cache-default.9.12.3-b6e0d5d41d74cfbff161e14a075d3267 */

And that's where the MDC toolbar should be defined. I don't fully grok the inner workings of Mindtouch so I'm not sure how helpful this is.
Well, looking at the Editor configuration in the Control Panel, the MDC toolbar set is in fact defined correctly. So there's something going on on the server that I don't understand.
As with the custom CSS, I'm thinking this is also caused by an unwritable folder, presumably /editor/fckeditor/editor/. Making that folder server-writable might fix it. 

It doesn't look like all the other files inside need to be writable, Deki just needs permission to create cache files inside the folder.
oremj:  did you make that dir writeable already?  I was able to get an editor window open without any errors just now on stage9.
I can confirm that the editor is working now, not only to open, but to perform edits and save them. Also did some tag editing. Works.
r.fixed on stage9, our official fully integrated staging server.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Version: MDN → unspecified
Component: Deki Infrastructure → Other
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.