[Plugin: W3 Total Cache] Plugin could not be activated because it triggered a fatal error?

  • I got this message

    +++
    /home/wp-content/uploads could not be created, please run following command:
    chmod 777 /home/wp-content
    then
    +++

    what’s wrong? I was chmod 777 wp-content but the problem still appear

    Best Regards

    Jauhari

Viewing 5 replies - 1 through 5 (of 5 total)

  • Using WP MU? Try: # chmod 777 wp-content/uploads/

    Frederick,

    I’m trying to get this working on an MU install and can’t get by the ‘fatal error’ message. All folders are chomd properly.

    I’ve noticed a few other forum posts about this – have you found anything that might be causing the issue?

    Can you guys send me an email through my web site so I can look at your particular cases. This is not a common issue, but I would like to understand it.

    I’ve seen a few posts about this issue and you keep referring to a wp-content/upload folder that I don’t have.

    Also, I haven’t seen a fix yet. Is there one, or are we waiting for the next release?
    I don’t mind either way, I appreciate your work, but if we are waiting, then I can stop spending time combing the internet looking for a fix.

    Well right now W3TC needs wp-content/uploads/ or whatever is defined in your WP Admin settings.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: W3 Total Cache] Plugin could not be activated because it triggered a fatal error?’ is closed to new replies.