editor fails to load with 2.4.3 config file

[Alfonso Martínez de Lizarrondo]

Yes, it's foolish, but we know that people don't read docs, so I've tried to place the fckconfig.js file from 2.4.3 in the SVN and it failed the first time in fcktoolbarfontformatcombo.js line 75 as it returns null for the style object.

Maybe putting a check there and an alert box "Read the upgrade guide" is enough (or even directly loading the page in a new window) and the rest of the configuration changes will be done properly.

Maybe we could check also what happens if there are extra commas or things like that.

[Frederico Caldeira Knabben]

For now, we can hardcode messages like "The FCKConfig.SomeSetting setting was not found. Please check the fckconfig.js file", which would at least address developers to that file. I've implemented it with [1007].

It would be wonderful if we could do configurations validation, but this would impact in the editor code size. To avoid overloading the code, we are not making configuration checks. So, with the above changes, the editor will load, but will not be properly functional.

This is a problem we always had. The conceptions I have for the configuration system for version 3 would help us avoiding such problems. I think we should have a standard configurations set, compressed with the core code, which would them be overloaded by customized settings. In this way we would at least avoid having missing configurations, making also the maintenance a bit simpler.