I've heard this from others and I've now experienced it myself. I can't get the CF connector working for the file manager. Has anyone got it going and, if so, how did you do it?
Fri, 09/09/2005 - 12:05
#1
RE: Who can get the ColdFusion connector working?
RE: Who can get the ColdFusion connector working?
1. update fckconfig.js-- need to add cfm connector reference to FCKConfig.LinkBrowserURL and FCKConfig.ImageBrowserURL; just copy the asp line and change all references of "asp" to "cfm".
2. create the application variables mentioned in connector.cfm, which create paths to the default file directories.
RE: Who can get the ColdFusion connector work
Same issue tho, think it's set for 6.1 or so, although, it should be really easy to get it to work with 5.
You could even use JS to start the editor, and a simple CF file (any version) for the connector.
The connector XML stuff is well documented, and I've had good luck (besides having to add debug info, but grant's connector has a nice (last time i checked) debug feature.) setting 'em up, converting 'em, tweaking 'em, etc.
May [good] luck follow you wherever ya go!
___
dEN was here
RE: Who can get the ColdFusion connector work
Ugh.
RE: Who can get the ColdFusion connector work
Thanks to everyone for fixing this!.
RE: Who can get the ColdFusion connector work
RE: Who can get the ColdFusion connector working?
If I may make a suggestion: Add the session scope to your potential scopes for location variable storage. Using just application or server assumes a global, single upload folder, where a cms is likely to have more than that. On my own system, upload folders are different for each page as the user editing Page X may not have permission to see the uploads for Page Y. As such its a security breach to let them both be visible to all users by dumping the info into common folders.
Which makes the new file structure especially cumbersome. I'm going to have to make some adjustments to the connector and dialogs or I'd be creating literally hundreds if not thousands of subfolders to match up with this.
RE: Who can get the ColdFusion connector working?
The developer documentation demands an absolute "server" wide path, e.g. in the asp model it's in the server scope. I've already switched it to the application scope with a "fallback" to the server scope in coldfusion, because the asp server scope is a bit different from the cfml server scope.
So feel free to modify the connector to your own version and switch from Application to Session Scope. The only thing to do for it is to replace all appearances of "Application." in the connector.cfm to "Session.".
For most of the advanced coldfusion users, it's not too tricky to fully replace the file connector.
Not everybody liked the idea of uploading just files without a database insert of the data structure and to allow x levels of subdirectories without security.
For your own version of the connector, you just have to
1. replace the "browser.html" with your own version of an image picker / file upload variant.
2. Call "window.top.opener.SetUrl( fileUrl ) ;" with "fileurl" as the full url to the selected image or file to get the selected image/file back to FCKEditor 2.0.
RE: Who can get the ColdFusion connector working?
Thanks very much for the replacement info. That may come in very handy. My js skills are very weak.
RE: Who can get the ColdFusion connector working?
Hi,
I'm the developer of the coldfusion version. The biggest challenge is to change the connector for the different versions (asp/php/cfm) in fckconfig.js. I'm in contact with Fred to have an easier way to automatically configure the correct connector from fckeditor.cfm.
Here are the things to get it working:
1. The file connector for image uploading and managing needs UTF-8 XML Files,
which can only be handled by ColdFusion MX 6 and above. This is a demand by the javascript in the core editor. If you have your own version of the fileconnector, the fckeditor.cfm should work also in older versions.
2. Please edit fckconfig.js and make a comment sign (// ) before the asp connector in line 104 (??) and uncomment the cfm connector line below to use the cfm connector instead of the asp connector!
3. Set the Application variable "userFilesPath" to the root folder for the uploaded media files relative to your website
Under this directory, all media files will be placed automatically.
e.g. <cfset Application.userFilesPath = "/UserFiles/">
The folder (sub-)structure is demanded by Fred and is used by all standard versions.
4. Create the necessary folder you've set in 3. under your webroot (in this example "{webroot}\UserFiles" )
Then everything should work. You can get an updated version of the coldfusion files from RC3 as a zip archive (no official version!) here:
http://www.hotelwebservice.de/fckeditor.zip
FCKEditor for CF RC3 : XML request error
- ImageProperties > Browse Server
The FCK Resource Browser windows opens with an error message :
"XML request error: Internal Server Error (500)"
Please advice. ThankYou
ContiW