Complete the ColdFusion integration

[Frederico Caldeira Knabben]

The ColdFusion integration must be compliant with our standard "Server Side Integration" requirements, as defined at ServerSideStatus.

[Joseph]

We would need some sort of connector for ColdFusion that would handle this. The fckeditor.CFC seems to be a wrapper class for the config.js file that by default uses ASP so when wanting to do file/image uploads the editor uses ASP to do it instead of using a ColdFusion connector with CFFILE and CFDIRECTORY tags.

THE ColdFusion INSTANCE OF THE EDITOR SHOULD NOT USE ASP TO UPLOAD AND BROWSE FILES, DOESN'T ANYONE ELSE THINK THATS FUNKY?

[Marc R Jacobs]

Particularly "funky" on a linux server that lacks ASP.

[Frederico Caldeira Knabben]

Replying to zerocool:

We would need some sort of connector for ColdFusion that would handle this. The fckeditor.CFC seems to be a wrapper class for the config.js file that by default uses ASP so when wanting to do file/image uploads the editor uses ASP to do it instead of using a ColdFusion connector with CFFILE and CFDIRECTORY tags.

THE ColdFusion INSTANCE OF THE EDITOR SHOULD NOT USE ASP TO UPLOAD AND BROWSE FILES, DOESN'T ANYONE ELSE THINK THATS FUNKY?

Just set _FileBrowserLanguage and _QuickUploadLanguage to "cfm" in fckconfig.js and you will have the ColdFusion integration files playing, instead of the ASP ones.

There is no need to start screaming.

[Marc R Jacobs]

The ColdFusion integration using _FileBrowserLanguage and _QuickUploadLanguage is not working. I described this in detail in Ticket #499. For those of us in Linux servers ASP is not even an option. I did try using php for _FileBrowserLanguage and _QuickUploadLanguage, using the ColdFusion frontend. The image portion worked perfect, but would not return it to sample02_mx.cfm. Do you have any other ideas???

[Marc R Jacobs]

Thanks a lot for the update. Is there an approximate schedule for v2.6? Thanks.

[Wiktor Walc]

I have rewritten CF connector using CF MX server for testing purpose. It obviously doesn't work in CF5 because of limited support for user defined functions, local variables etc. in that archaic CF version.

My proposal is to include previous files from version for CF5 and new files for CF6 and above, like it's done for php4 and php5, with one difference - that we simply inform users that we stop supporting CF5 (I mean in a way that we will not implement all new features into it).

[Frederico Caldeira Knabben]

For me your proposal is ok Wiktor.

I'm would curious to know how important is the three generations old ColdFusion 5 (2001).

[Wiktor Walc]

Hmm I can't find any fresh rankings.

Googling for "coldfusion hosting" resulted in wide Coldfusion MX 7 support (and sometimes 6.1).

I just forgot to mention that in fact current implementation isn't fully CF 5 compatibile (upload functionality is written using cffunction tag not available in CF5, so only file browser works in CF5). So my conclusion is that we may stop supporting CF5.

[Frederico Caldeira Knabben]

It would be a little bit radical to drop CF5 support right now. We can plan that for version 3.0, when drastic changes are expected.

Curiously, I've just received a message from a CF5 developer regarding some issues in his installation. So, "Yes!" there are still real persons using it.

[Alfonso Martínez de Lizarrondo]

If the CF gets the new options to specify the folders for each file type (as it seems to be in the latest checkins) then this patch can be closed: ​https://sourceforge.net/tracker/index.php?func=detail&aid=1312834&group_id=75348&atid=543655

wwalc, do you have permissions in sourceforge to do it or do you need someone else to do it?

[Wiktor Walc]

I'm not registered at sourceforge.net so I would be grateful if you could do this for me.

[Alfonso Martínez de Lizarrondo]

Ok, ​https://sourceforge.net/tracker/index.php?func=detail&aid=1312834&group_id=75348&atid=543655 has been closed.

There are still a few patches there that should be reviewed or moved.