Wp-content folder is not writable or does not exists

  • Resolved Leah

    (@gezan)


    10 years, 3 months ago

    Hi,

    In previous versions there were very detailed instructions on how to handle this kind of warning. I believe you had to change permissions on an .ini -file.

    Now you are adviced to loosen permission settings on wp-content. In my case it’s set to 0755. I tried 0775 to no avail.

    Do you have any other advice on specific folders/files?

    Thanks 🙂

    http://wordpress.org/plugins/advanced-access-manager/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Leah

    (@gezan)

    10 years, 3 months ago

    Also tried 0777 but no difference. Guess this has to do with whether I set it recursively, and 0777 throughout the subfolders seems unsafe.

    Perhaps something changed because the “Wp-content folder is not writable or does not exists” disappeared in exchange for:

    Warning: rename(/home/xxxxxx/public_html/wp-content/plugins/advanced-access-manager/application/core/update.php,/home/xxxxxx/public_html/wp-content/plugins/advanced-access-manager/application/core/__update.php) [function.rename]: Permission denied in /home/xxxxxx/public_html/wp-content/plugins/advanced-access-manager/application/core/update.php on line 91

    One last thing; All files and folders in my WP install has the same user ID except for the aam folder in wp-content. Odd?

    Thanks 🙂

    vasyl_m

    (@vasyl_m)

    10 years, 3 months ago

    Hi Leah,
    This obviously has something to do with the way your PHP script is executed. I believe for security reasons, you hosting administrator disallowed PHP to do any filesystem manipulations.
    If you are not planning to use ConfigPress Tab, you can disregard the wp-content message. For other Warning, please go to advanced-access-manager/application/core and remove with update.php (this file is responsible for any kind of action that takes place after you updated AAM).

    We already realized that any kind of filesystem interaction will always cause issues, so we are refactoring the code now to eliminate filesystem operations. This is going to be included in next release 2.1.

    Regards,
    Vasyl

    Thread Starter Leah

    (@gezan)

    10 years, 3 months ago

    Ok! Looking forward to the 2.1 release.

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wp-content folder is not writable or does not exists’ is closed to new replies.