WordPress.org

31. mayooresan
    Member
    Posted 4 years ago #

    @marcoart
    some plugins have their own folders inside plugin directory!!! :(

32. Xandaline
    Member
    Posted 4 years ago #

    Otto42, solution to modifying the file.php worked for me. I was able to upgrade the plug-ins with out changing permissions.

    The downside to using this method is that when you upgrade WordPress this file gets overwritten and you have to modify the file again. It would be really nice if we could have a check-box option that would force FTP.

33. Brent Rasmussen
    Member
    Posted 4 years ago #

    Solved here:

    [Solved] WordPress 2.5 One-Click Plug-in Upgrades - Could not create directory

34. meegwell
    Member
    Posted 4 years ago #

    I clicked Activate and the screen went blank (WPAU 1.1) WP 2.1

    Now my whole blog is blank and the php error is:

    [Wed May 7 13:38:33 2008] [error] PHP Parse error: syntax error, unexpected $end in .../public_html/nashville95/wp-content/plugins/wordpress-automatic-upgrade/lib/pclzip.lib.php on line 1762

35. eselesel
    Member
    Posted 4 years ago #

    i had the same "could not remove the old plugin"-problem..

    without changing any permissions it rathers seems to be relevant that the appropriate user (in my case: www-data) owns the plugin directory.

    i.e.
    sudo chown -R www-data:www-data plugins/

36. npeden
    Member
    Posted 4 years ago #

    On my install the plugin auto update needed a wp-content/upgrade directory with the right permissions too. Like others, of course, the plugin directory had to be set too.

37. CarltonBale
    Member
    Posted 4 years ago #

    If you ever tried FTP SSL and it didn't work, this may be your problem. A bug in 2.5.1 will prevent you from switching back standard FTP.

    There is a bug with WordPress 2.5.0 and 2.5.1 where the setting to use FTP over SSL can not be deactivated once activated. So no matter what changes you make to the config page in the GUI, it will not work. The only way to override that setting is to set FTP_SSL to False in the wp-config.php file. Add the following line to your wp-config.php to override the setting:

    define('FTP_SSL', false);

    Here is the bug report:
    http://trac.wordpress.org/ticket/6986

38. jerrybell
    Member
    Posted 3 years ago #

    There is one more possible cause of this problem, as I found out. See this for details: http://www.jerry-bell.com/fix-for-wordpress-could-not-remove-the-old-plugin-error/

39. rivermaya
    Member
    Posted 3 years ago #

    Jerry Bell's tips didn't work out, no nested wp-content directories on my blogs .. Jerry's case is rare, I think ..

40. rivermaya
    Member
    Posted 3 years ago #

    I found out, in this "could not remove the old plugin"-problem, just chmod folder upgrade inside wp-content directory, if it can't change to 777, just delete the files inside upgrade folder or delete entire folder, and create a new folder named "upgrade" and do the chmod again.

41. reverbstudios
    Member
    Posted 3 years ago #

    Otto42's solution re the code change seems to work but the plugin still shows as being out of date once the process is finished. Maybe this doesn't work right for WP 2.7?

42. emikey
    Member
    Posted 3 years ago #

    The fix to force WordPress to use FTP worked great in version 2.6 but now I have version 2.7 and the file.php code does not contain function get_filesystem_method() { does anyone know how to force ftp update with WP 2.7 ?

43. guvnrDOTcom
    Member
    Posted 3 years ago #

    Problem: WordPress upgrade throws this error:-

    "Fatal error: Cannot redeclare pclziputilpathreduction()"

    Answer: Do this!

    Hope that helps.

Topic Closed

This topic has been closed to new replies.