(New page: == CustomConfigurationsPath == When making changes to the fckconfig.js file, you have to remember to reapply those changes in the file when upgrading FCKeditor to a newer version. This co...) |
|||
| Line 5: | Line 5: | ||
To make thinks easier, you can simply use this setting to point the editor to a secondary configuration file that overrides the configurations defined in the default fckconfig.js file. So, you can place that file anywhere outside the FCKeditor installation directory. | To make thinks easier, you can simply use this setting to point the editor to a secondary configuration file that overrides the configurations defined in the default fckconfig.js file. So, you can place that file anywhere outside the FCKeditor installation directory. | ||
| − | You don't need to make a copy of the fckconfig.js file. Just include the configurations you want to change in your file. | + | You don't need to make a copy of the fckconfig.js file. Just include the configurations you want to change in your file. |
Example: | Example: | ||
| − | <pre> | + | <pre>FCKConfig.CustomConfigurationsPath = '/myconfig.js' ; |
| − | FCKConfig.CustomConfigurationsPath = '' ; | ||
</pre> | </pre> | ||
Revision as of 10:10, 10 January 2008
CustomConfigurationsPath
When making changes to the fckconfig.js file, you have to remember to reapply those changes in the file when upgrading FCKeditor to a newer version. This could be tedious or you could even not remember this.
To make thinks easier, you can simply use this setting to point the editor to a secondary configuration file that overrides the configurations defined in the default fckconfig.js file. So, you can place that file anywhere outside the FCKeditor installation directory.
You don't need to make a copy of the fckconfig.js file. Just include the configurations you want to change in your file.
Example:
FCKConfig.CustomConfigurationsPath = '/myconfig.js' ;