Why on earth didn't Adobe provide CF options to for turning this feature on? This is an essential option for rich text editors in my opinion as there is usually a need to allowing images to be uploaded - especially in CMS systems.
While Rakshith's instructions work it is somewhat long winded and requires messing with Coldfusion system files.

I hope they address this in a future update.. Seems somewhat of an oversight if you ask me.

James,

I believe I read something from Adobe about security concerns in a shared hosting environment during the beta testing.

Ah I see.

I still think they could have simply disabled it by default but given people the option of enabling it. Or providing an option in the administration system to turn it off on a shared hosting basis.

@ James, I think Adobe just wanted to get this feature out there rather than worrying about the security aspects of the editor.

This 3rd party app is so small, that I don't think they would want to bother putting admin settings in the CFIDE/Administrator. Plus, the way it's written, there's no real way they could have and shared hosting issues is an even bigger bag of worms (the way it's written).

If you really needed the ability to upload, FCKEditor can be implemented without using cftexarea. So, it's a convenience.

@ Todd I know what you mean, but I just think it's a shame such an important feature is missed out. Yeah, it can be implemented fairly easily without using the built in function but it feels a little silly to have to do this to fully leverage the features.

If someone goes the route of using richtext=true but then later needs image upload they either have to try and edit the system files (a big no no on shared hosting) or scrap their code and re-do it manually..

Just a shame it couldn't be a fuller implementation. I still think it's cool Adobe added this feature in, but I would like to see the full feature set covered.

I've been using rich text editors in shared hosting for years and not had any security issues so far. I thought CF7+ made it alot easier to tie users into the sandbox..

@James, Download the FCKEditor code and take a look through the CFM pages. Now ask yourself how Adobe can make that part of CF Server (full featured, sandboxing, etc.) without just scrapping it and building their own. I don't think it's worth Adobe's time.

I wonder if the Spry team is working on something (probably not) or if that's out of scope.

You do have a point Todd. I suppose I'm just finding it hard to see the security implications as I've been using a rich text editor on my sites which run on shared hosting for years without issue.

Although I agree that it is a pain that this is not included by default, the ColdFusion team did a wonderful thing. If you load FCKEditor on your site you can take full advantage of the cftextarea tag by using the basepath attribute and pointing it to the installed location. This give you every option available. The new 2.5 version is so much better than the current CF installation.

@Steve Now that is very cool! I do like how they've done that. Nice to be able to upgrade the FCK code and still leverage the hooks in CF. Top job.

My client is on HostMySite (shared environment) and I love the option of uploading a file when creating links -- makes life sooooo much easier for me that feature is incorporated into cfk editor. However, I don't think HMs has this option enabled. Is there a way I can use this feature for my client?

Well, remember that this is just a 'wrapped up' version of fckEditor. You can always upload the full package yourself.

Ray, that's what I was thinking, but reading through the docs it's not very clear how to implement this. I mean compared to TineMCE (which is incredibly simple to use and work with) i'm not sure where the fckeditor folder should be uploaded to, how to change the upload directory path, and how to use the code on the textarea style.

Ketan - I don't use fckEditor. I can't really help you here.