Viewing 15 replies - 1 through 15 (of 16 total)
  • Thread Starter kuene

    (@kuene)

    Sorry for the mess. I will explain it better I hope…

    I run debian stable with PHP 5.4.4-14+deb7u14 and Mysql Server version: 5.5.38-MariaDB-1 with safe mode off.

    I run a multisite-installation for a university.
    after the upgrade to wordpress 4 and to the latest nextgen gallery when a user creates a new gallery the following error occurs (Manage Galleries-> Add a new Gallery):

    Directory /path to wordpress root/ is not writeable! (in my case: /home/blog/public_html/)
    Check this link, if you didn’t know how to set the permission : http://codex.wordpress.org/Changing_File_Permissions

    it is possible to Add new album .
    The file permissions are correct.

    Steps to reproduce:

    1. Multisite WordPress

    permission on the files:
    the root dir:

    drwxr-xr-x 5 blog blog  4.0K Jun 29  2011 public_html/
    ls -lah public_html/
    -rwxrwxrwx  1 blog www-data  508 Sep  8 14:24 .htaccess*
    -rw-r--r--  1 blog    blog      418 Oct 30  2013 index.php
    ...
    drwxr-xr-x  9 blog    blog      12K Jan 28  2013 wp-admin/
    ...
    -rw-r--r--  1 blog    blog     3.8K Sep  8 14:28 wp-config.php
    drwxr-xr-x 10 blog    www-data 4.0K Sep 21  2010 wp-content/
    ...
    drwxr-xr-x 12 blog    blog      12K Sep 11 14:55 wp-includes/
    ...
    -rw-r--r--  1 blog    blog      33K Sep 11 14:55 wp-login.php
    ...
    -rw-r--r--  1 blog    blog      11K Sep 11 14:55 wp-settings.php
    -rw-r--r--  1 blog    blog      26K Sep 11 14:55 wp-signup.php
    ...

    inside the wp-content folder:

    drwxrwxr-x 12 blog  www-data 4.0K Sep 17 11:11 blogs.dir/
    drwxrwxr-x  3 www-data www-data 4.0K Feb 10  2009 uploads/
    ls -lah blogs.dir/1/
    drwxrwxr-x  3 www-data www-data 4096 May 16 15:23 files/

    www-data is the apache user and blog is the ftp user.
    … I skipped irrelevant files.

    2. Path
    Network Options
    Gallery path

    is: wp-content/blogs.dir/%BLOG_ID%/files

    the error does not occur when the public_html is writable too. This seems to be a bug.

    Thread Starter kuene

    (@kuene)

    Version 2.0.66.29 still has the same problem πŸ™

    @kuene – A standard installation for WordPress has the /public_html/ folder as writable with an equivalent permission of 0750, what permissions are you using for your WordPress installation?

    – Cais.

    Thread Starter kuene

    (@kuene)

    as stated above:
    drwxr-xr-x 5 blog blog 4.0K Jun 29 2011 public_html/

    that would be 0755. writable for the ftp-user.
    the public_html of a large multisite installation should never be writable for the webserver user check here:
    http://codex.wordpress.org/Hardening_WordPress
    or
    http://codex.wordpress.org/Changing_File_Permissions

    my wordpress multiblog installation worked fine with this file-permssions since 2009.

    this is a bug in nexgen gallery. if I make the public_html folder world writable or writable for the webserver user the plugin works fine. but it must never write to the public_html folder.

    Plugin Contributor photocrati

    (@photocrati)

    @kuene – You have already submitted a Bug Report for this issue. It would probably be best to carry on the conversation there.

    Thanks!

    – Cais.

    Thread Starter kuene

    (@kuene)

    @photocrati: thanks I will do that. But I did not get any feedback there…
    Do you have a bug tracker where I can follow the progress on this bug?

    Plugin Contributor photocrati

    (@photocrati)

    @kuene – I have responded twice to your Bug Report … our system currently in place, especially for “free” support is via emails only.

    – Cais.

    @photocrati:
    @kuene:
    I have the same problem as mr. kuene.
    I have a multi site sub-directories and presents me the same error.
    when they can help fix this error?

    Plugin Contributor photocrati

    (@photocrati)

    @jortex696 – As it is not the same site and there are always a lot of moving parts with Multisite installations it is best if you start your own topic per the forum rules here: http://codex.wordpress.org/Forum_Welcome#Where_To_Post

    Thanks!

    – Cais.

    There is definitely a bug in NextGEN Gallery 2.0.66.29. Here’s a patch:

    --- a/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ngglegacy/admin/functions.php
    +++ b/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ngglegacy/admin/functions.php
    @@ -37,7 +37,8 @@
     		$txt = '';
    
             $galleryObj = new stdClass;
    -        $galleryObj->path = '';
    +#        $galleryObj->path = '';
    +	global $ngg; $galleryObj->path = $ngg->options['gallerypath'];
             $nggRoot = $storage->get_gallery_abspath($galleryObj);
    
     		// No gallery name ?
    Plugin Contributor photocrati

    (@photocrati)

    @kb0 – Thanks for sharing your work-around.

    We have also committed a correction that will be in our next (major) releases.

    – Cais.

    Don’t know if it is the same issue. I use latest version 2.0.66.37. My galleries are located inside a directory ‘images’. I have noticed that setting this directory as 0775 is not enough. I also have to set the root directory of the site as 0775. You can realise that this is not acceptable and must be resolved immediately.

    Plugin Contributor photocrati

    (@photocrati)

    @fesarlis – Additional corrections were added to our latest branch. You are welcome to use the latest public beta version which contains these modifications.

    Link: http://nextgen-gallery.com/nextgen-gallery-latest-beta/

    Otherwise, please start your own topic for this specific issue on your specific site.

    Thanks!

    – Cais.

    I am not a programmer but I don’t see anything relevant in the changelog. I don’t really understand why you want a new thread for the same issue, but will do it.

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    It’s forum policy.

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Error: "Directory / is not writeable" after upgrade’ is closed to new replies.