PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Running in MultiSite mode - Upload folder is not writable.

Gravity Support Forums » Plugin Support » Gravity Forms

  1. wpfmon75
    Member

    I'm getting the following error in WordPress 3.1.4 running in MultiSite mode with Gravity Forms version 1.5.2.8

    Upload folder is not writable. Export and file upload features will not be functional.

    Based on my searching around on the Forums, I believe this has something to do with where WordPress has the upload folder set for the blogs I have setup but I am unable to determine with certainty where this is set under the Network Admin area.

    I have navigated over to the 'Edit Site' area and see the following area referenced for upload:

    Upload Path wp-content/blogs.dir/2/files

    Is this the setting? If so, it is owned and writable by the user that owns WordPress.

    Any assistance would be appreciated. Thanks!

    Posted 13 years ago on Monday July 4, 2011 | Permalink

  2. Carl Hancock
    Administrator

    You need to make sure the wp-content/uploads folder is writeable. That is most likely where the error is coming from because that is the folder it's checking for.

    Posted 13 years ago on Tuesday July 5, 2011 | Permalink

  3. wpfmon75
    Member

    Carl,

    Thanks for the suggestion. That folder/directory is writable by the owner of Wordpress, that was the first thing I looked at. Could this be sourced from anything else?

    Posted 13 years ago on Wednesday July 6, 2011 | Permalink

  4. Carl Hancock
    Administrator

    It's going to be a file permission issue of some sort. One possible issue is the user that the file permissions are set for is not the same user that PHP is executing as, meaning you may view the permissions on the folder and they seem correct but they are different for the user that PHP is executing as. We encountered this ourselves with our own web host. But that error is triggered by file permissions not being correct so there is definitely something wrong with the file permissions.

    Posted 13 years ago on Wednesday July 6, 2011 | Permalink