OK, my problem is that they use different config mechanisms - FCKeditor itself is fine because it uses a class I can override. The standard file manager and CKFinder use static config files, and effectively require me to put bits of my app code inside them. This is not good for reliable integration. It should be possible to use a library without having to edit it (though setting 'enabled' is reasonable from a security point of view). Would it be a reasonable feature request to improve the config mechanism so it can be used more easily, or even enable the file manager and CKFinder to get config data from the editor?
At this moment the only way to assign different dynamic paths in CKFinder is to use config.php (similar situation as in built-in file browser). Note that if you could set paths in the FCKeditor/CKFinder object, they would have to be passed somehow to the server connector on each request. The only secure way to do this would be to use sessions. Because we didn't want to force anyone to use sessions in FCKeditor, it is impossible to do it. Anyway, I know what you mean and I agree that in some situations it could be useful.
Re: Getting file locations from FCKEditor
Re: Getting file locations from FCKEditor
Re: Getting file locations from FCKEditor
Note that if you could set paths in the FCKeditor/CKFinder object, they would have to be passed somehow to the server connector on each request. The only secure way to do this would be to use sessions.
Because we didn't want to force anyone to use sessions in FCKeditor, it is impossible to do it.
Anyway, I know what you mean and I agree that in some situations it could be useful.
Wiktor Walc
CTO, CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+