Forums

[resolved] Can't install new plugins using "Add New" feature (6 posts)

  1. watson
    Member
    Posted 3 years ago #

    I'm trying out the new WordPress 2.7 and want to use the build in function to install a new plugin directly from admin interface.

    After searching for the plugin and selecting "install", I'm prompted the FTP host, username and password. After entering the correct info I get the following error message:

    Installing Plugin: NextGEN Gallery 1.0.0

    Warning: ftp_rawlist() [function.ftp-rawlist]: php_connect_nonb() failed: Operation now in progress (36) in /usr/home/johndoe/domains/example.com/httpdocs/wp-admin/includes/class-wp-filesystem-ftpext.php on line 203

    Unable to locate WordPress Plugin directory.

    Installation Failed

    Before you ask if I've entered the correct u/p, then I can say that I've tried logging in with FTP via my console with these credentials and navigating to the plugins directory - no problem.

  2. watson
    Member
    Posted 3 years ago #

    I just tried via the zip file upload feature - same issue

  3. MichaelRpdx
    Member
    Posted 3 years ago #

    I also have the same problem. Though it took awhile for me to realize the hostname/UID/PW it was looking for was the WP system the plugin was to be installed to...

  4. barrydt
    Member
    Posted 3 years ago #

    I'm getting a similar result using both functions (install directly or upload the .zip file), but a different error message:

    Unpacking the plugin package

    Fatal error: Cannot redeclare pclziputilpathreduction() (previously declared in /home/domainyyy/directoryxxx/wp-content/plugins/wordpress-automatic-upgrade/lib/pclzip.lib.php:5421) in /home/domainyyy/directoryxxx/includes/class-pclzip.php on line 5498

    I have no idea what this means - any thoughts?

  5. babyrain
    Member
    Posted 3 years ago #

    No Resolution yet?

  6. watson
    Member
    Posted 3 years ago #

    I've found a solution, but it involves hacking WordPress it self.

    In my case it worked to change the way WordPress connects to the FTP server. So instead of using passive mode (which is the hardcoded default in WordPress), I now use active mode.

    To do this you have to edit wp-admin/includes/class-wp-filesystem-ftpext.php and change line 84 to this:

    @ftp_pasv( $this->link, false );

    In the future it would be nice to have an FTP WordPress constant called FTP_PASV that you could set to either true or false. This way the hack would survive WordPress upgrades :)

Topic Closed

This topic has been closed to new replies.

About this Topic