• Resolved penfil

    (@penfil)


    I just upgraded to WordPress 2.7 and everything seems to be working smoothly, except the auto-update feature.

    I tried to upgrade a plugin automatically and after entering the correct FTP info I get the following error message:

    Warning: ftp_rawlist(): open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/usr/local/pem/vhosts/154599) in /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-admin/includes/class-wp-filesystem-ftpext.php on line 203
    Warning: ftp_rawlist(): Unable to create temporary file. Check permissions in temporary files directory. in /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-admin/includes/class-wp-filesystem-ftpext.php on line 203
    
    Unable to locate WordPress Plugin directory.
    
    Plugin upgrade Failed

    This happens with any plugin that is already installed and I try to upgrade. It also happens if I try to install a new plugin through WordPress.

    I tried adding the define function to the config file as one of the bug fixes from 2.7 RC1 and RC2 recommended, but it didn’t help.

    The site I am working with is hosted by AllDomains and they are not very client friendly. (I don’t recommend them). I am almost sure I do am not allowed access to php.ini unless there is some way to bypass it.

    Can anyone help me fix this?

Viewing 10 replies - 16 through 25 (of 25 total)
  • Create a /tmp directory in your web directory, chmod it to 777 and refer to it in the following function.

    putenv('TMPDIR=/path/to/my/web/hosting/directory/www/tmp/');

    Put this in your wp-config.php

    For cezarneaga it could be something like

    putenv('TMPDIR=/is/htdocs/wp1090696_F7DLCX6X2Y/www/tmp/');

    It is doesn’t work in byethost

    I tried the fix outlined above (adding the line to wp-config) and suddenly WP couldn’t find my wp-content directory! EEP.

    I also added the line and successfully upgraded all in one seo pack. From that point on WP could not find the wp-content directory!!!

    There is a flaw in the WP code. Has anybody worked thru this???

    Help….

    Doesn’t work in Byethost. Anyone has a workaround? (manually upgrading all the plugins as well as the installation can get tiresome..)

    I dont know why but in file wp-admin/inclides/file.php
    On line aprox 144
    The function get_temp_dir totally ignores WP_TEMP_DIR
    So my correction passes by change

    return '/tmp/';
    }

    To

    return '/directory/to/tmp';
    }

    Hello everybody!

    I’m using WordPress 2.8.1 in ByetHost. I had the same problem with “Unable to locate WordPress Plugin directory.” but I solved it by adding the following code in my wp-config.php:

    if(is_admin()) {
    	add_filter('filesystem_method', create_function('$a', 'return "direct";' ));
    	define( 'FS_CHMOD_DIR', 0751 );
    }

    I’ve just write a post in one of my blogs (a very new blog), but it’s in spanish. May be you will can understand or, at least, be useful. You can see it here:
    Solución a los problemas FTP en WordPress 2.8
    .

    If you have any question, please leave it in my blog ??

    Sorry for my English :S . I’m copying and pasting this post in part on other threads, sorry again.

    In my case non of the above worked, but what did work was instead of typing in the url in the ftp field, I used the server’s local address: 127.0.0.1 and everything worked like a charm again.

    Hope this helps someone else too ??

    doc_root is like this /home/vol11/gofreeserve.com/gofre_number/domain.com/htdocs in gofreeserve.com
    ftp dir is /domain.com/htdocs/

    So I put define(‘FTP_BASE’, /domain.com/htdocs/’); into config file.
    still get Unable to locate WordPress Content directory (wp-content)

    class-wp-filesystem-base.php is a funny joke at all.

    I had the same problem ??

    This worked fine for me, it’s the simplest method to cure /tmp directory bug…

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘Auto-Update Failure in WordPress 2.7’ is closed to new replies.