• Hi,
    while updating the plugin from 1.66 to 1.67, I got this error in the admin panel:

    thrown in /SITE_BASE/wp-admin/includes/class-wp-filesystem-ftpext.php on line 420
    [27-Apr-2022 07:21:25 UTC] PHP Fatal error:  Uncaught TypeError: ftp_nlist(): Argument #1 ($ftp) must be of type resource, null given in /SITE_BASE/wp-admin/includes/class-wp-filesystem-ftpext.php:420
    Stack trace:
    #0 /SITE_BASE/wp-admin/includes/class-wp-filesystem-ftpext.php(420): ftp_nlist()
    #1 /SITE_BASE/wp-content/plugins/google-captcha/bws_menu/bws_functions.php(748): WP_Filesystem_FTPext->exists()
    #2 /SITE_BASE/wp-includes/class-wp-hook.php(307): bws_admin_enqueue_scripts()
    #3 /SITE_BASE/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
    #4 /SITE_BASE/wp-includes/plugin.php(474): WP_Hook->do_action()
    #5 /SITE_BASE/wp-admin/admin-header.php(118): do_action()
    #6 /SITE_BASE/wp-admin/index.php(137): require_once('...')
    #7 {main}
      thrown in /SITE_BASE/wp-admin/includes/class-wp-filesystem-ftpext.php on line 420

    Is there a way to fix it?
    Thanks`

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support andrewsupport

    (@andrewsupport)

    Hi,

    Could you please complete the following steps in order to detect the problem and find its solution:

    1) Activate a default WordPress theme for a while (Twenty Nineteen or Twenty-Twenty) and check if the problem remains.
    2) Deactivate all of your plugins except the reCaptcha plugin, and also check if the problem is still present. If it is not, activate the plugins one by one, meanwhile checking, after which plugin activation the problem appears again.
    3) Contact us back with information about the results.

    Thread Starter tety94

    (@tety94)

    Hi,
    as per your indication I tried to use 2022 default theme and deactivate all plugins but it did not work

    Plugin Support andrewsupport

    (@andrewsupport)

    Hi,

    Please, try to reinstall the plugin. Delete the current version, download, install and activate a new one.

    I also want to report the same problem today after updating the plugin to version 1.67. The site works, but it is impossible to enter the admin panel – A critical error occurred on the site updating plugins. I returned to version 1.66 – no manipulation with version 1.67 (which you suggested) helped.

    2022-05-04 16:39:18: (mod_fastcgi.c.451) FastCGI-stderr:Stack trace:
    2022-05-04 16:39:18: (mod_fastcgi.c.451) FastCGI-stderr:#0 /www/free/wp-admin/includes/class-wp-filesystem-ftpext.php(420): ftp_nlist()
    2022-05-04 16:39:18: (mod_fastcgi.c.451) FastCGI-stderr:#1 /www/free/wp-content/plugins/google-captcha/bws_menu/bws_functions.php(748): WP_Filesystem_FTPext->exists()
    2022-05-04 16:39:18: (mod_fastcgi.c.451) FastCGI-stderr:#2 /www/free/wp-includes/class-wp-hook.php(307): bws_admin_enqueue_scripts()
    2022-05-04 16:39:18: (mod_fastcgi.c.451) FastCGI-stderr:#3 /www/free/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
    2022-05-04 16:39:18: (mod_fastcgi.c.451) FastCGI-stderr:#4 /www/free/wp-includes/plugin.php(474): WP_Hook->do_action()
    2022-05-04 16:39:18: (mod_fastcgi.c.451) FastCGI-stderr:#5 /www/free/wp-admin/admin-header.php(118): do_action()
    2022-05-04 16:39:18: (mod_fastcgi.c.451) FastCGI-stderr:#6 /www/free/wp-admin/plugins.php(605): require_once(‘…’)
    2022-05-04 16:39:18: (mod_fastcgi.c.451) FastCGI-stderr:#7 {main}
    2022-05-04 16:39:18: (mod_fastcgi.c.451) FastCGI-stderr: thrown in /www/free/wp-admin/includes/class-wp-filesystem-ftpext.php on line 420

    Plugin Support andrewsupport

    (@andrewsupport)

    Hi,

    To solve your problem, please contact us via our Help Center (https://support.bestwebsoft.com/)

    Thread Starter tety94

    (@tety94)

    Hi,
    we tried to reinstall the plugin and install a new one but it did not working.

    Plugin Support andrewsupport

    (@andrewsupport)

    Hi,

    None of our customers have come forward with a problem like this. Unfortunately, we cannot offer you a ready-made solution to your problem. To solve your problem, please contact us via our Help Center (https://support.bestwebsoft.com/)

    @andrewsupport Actually I came here today looking to see if anyone else reported something similar to this issue. I am performing regular software upgrades and when going from 1.66 to 1.67, I also see three warnings coming from this plugin.

    Warning	ftp_nlist() expects parameter 1 to be resource, null given	1	
    
        wp-admin/includes/class-wp-filesystem-ftpext.php:420
        ftp_nlist()
        wp-admin/includes/class-wp-filesystem-ftpext.php:420
        WP_Filesystem_FTPext->exists()
        wp-content/plugins/google-captcha/bws_menu/bws_functions.php:748
        bws_admin_enqueue_scripts()
        wp-includes/class-wp-hook.php:307
        do_action('admin_enqueue_scripts')
        wp-admin/admin-header.php:118
    
    	Plugin: google-captcha
    Warning	ftp_pwd() expects parameter 1 to be resource, null given	2	
    
        wp-admin/includes/class-wp-filesystem-ftpext.php:230
        ftp_pwd()
        wp-admin/includes/class-wp-filesystem-ftpext.php:230
        WP_Filesystem_FTPext->cwd()
        wp-admin/includes/class-wp-filesystem-ftpext.php:450
        WP_Filesystem_FTPext->is_dir()
        wp-admin/includes/class-wp-filesystem-ftpext.php:422
        WP_Filesystem_FTPext->exists()
        wp-content/plugins/google-captcha/bws_menu/bws_functions.php:748
        bws_admin_enqueue_scripts()
        wp-includes/class-wp-hook.php:307
        do_action('admin_enqueue_scripts')
        wp-admin/admin-header.php:118
    
    	Plugin: google-captcha
    Warning (Suppressed)	ftp_chdir() expects parameter 1 to be resource, null given	1	
    
        wp-admin/includes/class-wp-filesystem-ftpext.php:451
        ftp_chdir()
        wp-admin/includes/class-wp-filesystem-ftpext.php:451
        WP_Filesystem_FTPext->is_dir()
        wp-admin/includes/class-wp-filesystem-ftpext.php:422
        WP_Filesystem_FTPext->exists()
        wp-content/plugins/google-captcha/bws_menu/bws_functions.php:748
        bws_admin_enqueue_scripts()
        wp-includes/class-wp-hook.php:307
        do_action('admin_enqueue_scripts')
        wp-admin/admin-header.php:118
    
    	Plugin: google-captcha

    Warning level messages make it to our logging system so we won’t be able to upgrade until this is rectified somehow.

    If it helps, we don’t use any FTP facilities at all to manage our sites, they are run in Docker containers and deployed to AWS Fargate. We also have local file modification disabled in WP since we don’t actually modify the filesystem of deployed containers via the UI. I don’t believe the current usage of WP_Filesystem() is safe in all use cases, such as ours.

    Edit: These warnings occurred for me just loading the WP Admin home page after upgrading.

    • This reply was modified 2 years, 6 months ago by chief1983.

    After update 1.68 – the problem remains. I have to stay on version 1.66

    I gave this a shot and tried the upgrade on our stage environment anyway. Lots of these coming in from Sentry as people click around. We’ll be stuck on 1.66 until the following code is adjusted to be safe in more environments:

    		WP_Filesystem();
    		if ( ! $wp_filesystem->exists( dirname( __FILE__ ) . '/css/jquery-ui-styles/' . $jquery_ui_version . '/' ) ) {
    			$jquery_ui_version = '1.12.1';
    		}

    As multiple users are running into this issue, it might be helpful to find out what configuration we have in common.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Errors updating version 1.66 to 1.67’ is closed to new replies.