Super Cache working fine, but install required wp-content chmod 777

Viewing 4 replies - 1 through 4 (of 4 total)
  • Donncha O Caoimh (a11n)

    (@donncha)

    16 years, 4 months ago

    Of course, there is a risk. The cache plugin will work fine if wp-content isn’t writeable but you won’t be able to change any of the settings.
    I need to do some testing of this to figure out what can be set to 755 and what needs to be 777, and when. The config file needs to be writeable but it might be ok to make wp-content 755 after the file is created.

    ateam

    (@ateam)

    16 years, 4 months ago

    I think your issue is the OWNER of wp-content.

    You DO NOT WANT chmod 777! I would only go as far as 775.

    So, wp-content needs to “chown apache” (or whatever is the appropriate user for your system).

    You could get away with “chgrp apache” with the chmod 775.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    16 years, 4 months ago

    After you get it setup and working, you don’t need to leave wp-content at 777. You just need to leave the cache directory itself writable. Change wp-content back to 755 or 644.

    blakkjakk

    (@blakkjakk)

    16 years, 3 months ago

    Ateam, some of us our noobs from shared hosting. I think you should specific that when you talk about changing the owner you mean that the admin needs to be logged into the ROOT access to change the owner premssions of the file or you will have to open a service ticket with your host.

    For me apache 775 worked on WP-Content.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Super Cache working fine, but install required wp-content chmod 777’ is closed to new replies.