Skip to main content
A
aosipartner
Participant
August 5, 2009
Question

Enable fckeditor - UPLOAD

  • August 5, 2009
  • 2 replies
  • 2773 views

After applying the patch in advisory  APSB09-09, we need to allow uploads via fckeditor. Following these OPTIONAL steps to enable, we're not able to start ColdFusion. The specific step that is applied causing CF to not start is:

Edit jvm.config file and add the JVM argument “–Dcoldfusion.fckupload=true”

I have verfied that the "update" hf800-77218.jar was active and that the default JVM was being used for ColdFusion. Anyone else try enabling the upload and run into this problem?

Thanks for any help,

Jon C.

    This topic has been closed for replies.

    2 replies

    A
    Adam Cameron.
    Inspiring
    September 15, 2009

    Is anything helpful being stuck in the log files when the CF start-up fails?

    --

    Adam

    A
    aosipartnerAuthor
    Participant
    August 5, 2009

    Also wanted to mention that I've verified this on two servers, same results. Adding "–Dcoldfusion.fckupload=true" (with or without quotes) keeps CF from starting.

    A
    Anonymous725
    Participant
    September 15, 2009

    I'm guessing fileuploads with the cftextarea will not be used anymore for hostek.com?

    M
    MaximumCookie
    Participant
    September 15, 2009

    In order to use the upload features of the cftextarea, you simply need to upload your own copy of the FCKeditor into a folder named something other than FCKeditor(it seems the hotfix blocks certain files underneath any folder named FCKeditor).  You then, simply set the basepath parameter of the cftextarea tag to the site-relative path to where you uploaded the FCKeditor files.

    There is a forum post at the following URL that goes through setting up your own FCKeditor, step by step:

    http://forum.hostek.com/showthread.php?t=84

    Configuring the default FCKeditor installation to allow uploads using Adobe's work-around is basically like undoing the patch in the first place, which is why they specify to password protect all pages with a cftextarea tag as part of the work-around.  Since that is not something that is possible on a shared hosting server, using your own copy of the fckeditor and using the basepath attribute of the cftextarea tag to point it there is the way to go.

    -David D.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices