Drupal Association members fund grants that make connections all over the world.
The other day I spent an hour ripping my hair out over why FCKEditor refused to even load on an edit node page, when a colleague pointed out that since I:
- not only used a separate admin theme,
- but also had set the admin theme to be used for node editing
- and had told the FCKeditor module to load its fckeditor.config.js file from the theme directory
I should have put fckeditor.config.js in the admin theme's directory, not the front-end theme's directory.
OK, stupid mistake on my part, but the debugging would have gone so much smoother if the Settings page for FCKeditor showed the path to the current theme beneath the fckeditor.config.js setting.
So that is my feature request: please display the path(s) FCKeditor will be looking for underneath the fckeditor.config.js setting.