upgrading FCKeditor is laborious:

one has to find and save all changes to the config files like
FCKeditor/fckconfig.js
FCKeditor/editor/filemanager/connectors/php/config.php
and maybe some others.

So I suggest to store all configuration parameters in the database and write to a file like FCKeditor/fckconfig.js (it must not be this file for security reasons, the path could be a protected folder) and create this file during installation or update of the modul.

All (neccessary) parameters and their description could be exposed in the admin -interface of the Editor-Modul - so it would be easier to manage.

Hope you like the idea.

Best
Thomas Zahreddin

Comments

Thomas_Zahreddin’s picture

Thomas_Zahreddin commented

hi,

i found some description about this topic:
http://docs.fckeditor.net/FCKeditor_2.x/Developers_Guide/Configuration/C...

though on this page method 2 is rated better than method 1 - I can't see why it would be better:
I think reading the custom config file on the server (method 1) is much faster than sending it also to the client and let the javascript interpreter do the job, specially if the configuration file gets bigger.

The list of all avialable Parameters:
http://docs.fckeditor.net/FCKeditor_2.x/Developers_Guide/Configuration/C...

hope this helps.

Best
Thomas Zahreddin

Jorrit’s picture

Jorrit commented

This would require the fckeditor module maintainers to closely monitor changes in the syntax of the fckeditor configuration file, which is at this point not possible. Perhaps in a later version.

wwalc’s picture

wwalc commented

Instead of changing fckconfig.js add configuration options to fckeditor.config.js. Anyway some upgrade instructions would be useful, added to #277657: TODO list for 6.x-2.x and 5.x-3.x.

Jorrit’s picture

Jorrit commented
Status: Active » Closed (fixed)

Closed because of inactivity. If it is still a problem, please reopen.