I take that back. I had a separate non-FCKEditor issue, putting an Application.cfc at the beginning of FCKEditor's directory and messing with the config.cfm fixed my issue. The cfcontent issue below did nothing. So... it was more environmental than FCKEditor.
On Dec 11, 2007 11:28 AM, Todd <[EMAIL PROTECTED]> wrote: > > Using the FCKEditor CFC downloaded from FCKEditor site. This isn't a > permission issue as I found a separate non-FCKEditor issue interfering with > the FCKEditor. However, I'm still getting an invalid XML, but I'm close to > working it through. > > I found my issue. I changed in cf_basexml.cfm: > <cfcontent reset="true" type="text/xml; charset=UTF-8"> > > To: > <cfcontent type="text/xml; charset=UTF-8"> > > I'm not sure why my server didn't like that, but it didn't. Filebrowser > is up and working now. The code for the filebrowser, for what it is, isn't > pretty. At all. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Check out the new features and enhancements in the latest product release - download the "What's New PDF" now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:294525 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
