WP-Cache Security Flaw

  • spiderbiteman

    (@spiderbiteman)


    16 years ago

    The wp-cache plugin is asking me to make the wp-content directory writable. Is that really good security practice?

    The error is:
    Error: wp-content directory ([…/user/site]/wp-content) is not writable by the Web server.

    Someone had suggested a solution would be to give 777 to wp-content, activate the plugin, then change the permissions and that would solve the problem. It didn’t work.

    Is giving 777 to the wp-content area a concern to anyone else?

    Is there another way or is 777 a must?

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    16 years ago

    The plugin has to be able to write files. It doesn’t matter if it’s 777 or not, but it has to have enough permission for the webserver to be able to write files to the directory. That might be 644 or 664 or 666, depending on the configuration.

    wp-content doesn’t necessarily have to be writable, but the cache directory that it creates will have to be writable. It’s just complaining because it’s trying to create the cache directory.

    Thread Starter spiderbiteman

    (@spiderbiteman)

    16 years ago

    Hello Otto32 and thanks for the fast response, but that doesn’t work.

    I have the cache set to be writable and yet it does not work. Only when I use 777 on wp-content does it work.

    Any suggestions?

    ipavkovic

    (@ipavkovic)

    16 years ago

    See

    http://wordpress.org/support/topic/163325?replies=2#post-721436

    Best Regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WP-Cache Security Flaw’ is closed to new replies.