Forum Replies Created

Viewing 15 replies - 1 through 15 (of 41 total)
  • Thread Starter forgetme

    (@forgetme)

    Version 2.1.0 did not resolve this issue. I’m still seeing it running PHP 8.0.3 now, here is the log error with stack trace.

    
    PHP Deprecated: Required parameter $ids follows optional parameter $table in wp-content/plugins/user-login-history/inc/common/helpers/class-db.php on line 113.
    
    {closure}()
    wp-content/plugins/user-login-history/inc/common/class-login-tracker.php:333
    User_Login_History\I\C\Login_Tracker->update_time_last_seen()
    wp-content/plugins/user-login-history/inc/common/class-login-tracker.php:136
    User_Login_History\I\C\Login_Tracker->init()
    wp-includes/class-wp-hook.php:292
    do_action('init')
    wp-settings.php:560
    
    Thread Starter forgetme

    (@forgetme)

    Just wanted to let you know whatever you fixed in 2021.2.1 around object caching appears to have resolved this issue as well. I’m no longer seeing the error when I clear my WP Rocket cache.

    Thanks.

    Thread Starter forgetme

    (@forgetme)

    Version info:
    WordPress: 5.6.2
    WooCommerce: 5.0.0
    PHP-FPM: 8.0.2
    Still getting the error, so I disabled all other plugins so it was only WooCommerce and Booster for WooCommerce and the deprecation notice went away, so it relates to Booster and another plugin in someway. I’ll have to investigate further.

    You can close this bug and I’ll open a new one once I determine if it is on your side or theirs.

    Thread Starter forgetme

    (@forgetme)

    Verified 2.4.0 fixed the PHP 7.4 and PHP 8.0 issues.

    Thanks for the quick update and the best plugin for identifying and debugging all my site’s issues.

    Thread Starter forgetme

    (@forgetme)

    Main version info:
    WordPress 5.6.2
    WooCommerce 5.0.0

    Thread Starter forgetme

    (@forgetme)

    I also get this same error on PHP 7.4, but it is only a Warning there and not a fatal error.

    Here are the PHP 7.4 errors I get when enabling Decalog

    
    Error (E_WARNING): "count(): Parameter must be an array or an object that implements Countable" at ./wp-admin/includes/class-wp-list-table.php:546
    
    ./wp-admin/includes/class-wp-list-table.php:546:546
    Decalog\L\PhpListener->handle_error()
    wp-admin/includes/class-wp-list-table.php:546
    WP_List_Table->row_actions()
    wp-content/plugins/decalog/includes/features/class-loggers.php:186
    Decalog\P\F\Loggers->column_name()
    wp-admin/includes/class-wp-list-table.php:1434
    WP_List_Table->single_row_columns()
    wp-admin/includes/class-wp-list-table.php:1379
    WP_List_Table->single_row()
    wp-admin/includes/class-wp-list-table.php:1366
    WP_List_Table->display_rows()
    wp-admin/includes/class-wp-list-table.php:1351
    WP_List_Table->display_rows_or_placeholder()
    wp-admin/includes/class-wp-list-table.php:1278
    WP_List_Table->display()
    wp-content/plugins/decalog/admin/partials/decalog-admin-settings-loggers.php:32
    Decalog\P\Decalog_Admin->get_settings_page()
    wp-includes/class-wp-hook.php:287
    do_action('perfops-settings_page_decalog-settings')
    wp-admin/admin.php:259
    
    
    Error (E_NOTICE): "Undefined variable: actions" at ./wp-content/plugins/decalog/includes/features/class-loggers.php:186
    
    ./wp-content/plugins/decalog/includes/features/class-loggers.php:186:186
    Decalog\L\PhpListener->handle_error()
    wp-content/plugins/decalog/includes/features/class-loggers.php:186
    Decalog\P\F\Loggers->column_name()
    wp-admin/includes/class-wp-list-table.php:1434
    WP_List_Table->single_row_columns()
    wp-admin/includes/class-wp-list-table.php:1379
    WP_List_Table->single_row()
    wp-admin/includes/class-wp-list-table.php:1366
    WP_List_Table->display_rows()
    wp-admin/includes/class-wp-list-table.php:1351
    WP_List_Table->display_rows_or_placeholder()
    wp-admin/includes/class-wp-list-table.php:1278
    WP_List_Table->display()
    wp-content/plugins/decalog/admin/partials/decalog-admin-settings-loggers.php:32
    Decalog\P\Decalog_Admin->get_settings_page()
    wp-includes/class-wp-hook.php:287
    do_action('perfops-settings_page_decalog-settings')
    wp-admin/admin.php:259
    
    Thread Starter forgetme

    (@forgetme)

    Here is some additional info around the hooks that may help in tracking these issues down to fix them.

    
    Required parameter $atts follows optional parameter $return_value
    wp-content/plugins/booster-plus-for-woocommerce/includes/shortcodes/class-wcj-shortcodes-products-crowdfunding.php:90
    WC_Jetpack->__construct()
    wp-content/plugins/booster-plus-for-woocommerce/booster-plus-for-woocommerce.php:88
    WC_Jetpack::instance()
    wp-content/plugins/booster-plus-for-woocommerce/booster-plus-for-woocommerce.php:117
    WCJ()
    wp-content/plugins/booster-plus-for-woocommerce/booster-plus-for-woocommerce.php:121
    
    
    Required parameter $templates follows optional parameter $section
    wp-content/plugins/booster-plus-for-woocommerce/includes/class-wcj-checkout-custom-fields.php:278
    WC_Jetpack->__construct()
    wp-content/plugins/booster-plus-for-woocommerce/booster-plus-for-woocommerce.php:88
    WC_Jetpack::instance()
    wp-content/plugins/booster-plus-for-woocommerce/booster-plus-for-woocommerce.php:117
    WCJ()
    wp-content/plugins/booster-plus-for-woocommerce/booster-plus-for-woocommerce.php:121
    
    Thread Starter forgetme

    (@forgetme)

    Hi @gravid7,
    Today I updated to version 5.3.8 which according to the changelog sounds like it should be compatible with PHP 8.0.2 now.

    = 5.3.8 – 24/02/2021 =

    * PHP 8.0.2 tested
    * WooCommerce 5.0 tested

    This is not the case as I still get the 2 errors above related to this plugin and PHP 8. Just wanted to pass along that there are still issue that need to be fixed for this plugin to fully support PHP 8.

    Thread Starter forgetme

    (@forgetme)

    I can follow up with WP Rocket about this, but here is the exact calls being made to clear caches and preload all caches.

    
    // Clear WP Rocket cache.
    if ( function_exists( 'rocket_clean_domain' ) ) {
    	rocket_clean_domain();
    	echo ( "Cache Flushed <br><br>" );
    	error_log( "Cache Flushed \n" );
    }
    
    // Clear WP & Redis cache.
    if ( function_exists( 'wp_cache_flush' ) ) {
    	wp_cache_flush();
    	echo ( "Redis Flushed <br><br>" );
    	error_log( "Redis Flushed \n" );
    }
    
    // Preload WP Rocket cache.
    if ( function_exists( 'run_rocket_sitemap_preload' ) ) {
    	run_rocket_sitemap_preload();
    	echo ( "Starting Sitemap Pre-load" );
    	error_log( "Starting Sitemap Pre-load \n" );
    }

    Not sure if an update fixed this or not, but I’m able to activate/deactivate on v3.2.7

    Thread Starter forgetme

    (@forgetme)

    The Advanced noCaptcha & invisible Captcha (v2 & v3) plug-in owner just needs to pull in the latest version of Freemius that they have a dependency on to fix this. It looks like it has already been addressed in the Freemius WordPress-SDK master branch on GitHub and is included in the 2.4.2 release.

    Here’s their 2 commits for PHP 8 issues in this class-fs-logger.php file:

    https://github.com/Freemius/wordpress-sdk/commit/f7b5b3c28455d1b161ca1e47dd6d32f371ccaa2a#diff-1fd96b73d06e9d77b0f53ee83dd468deb1efb073cc816c89f38d08ba2afa8102

    https://github.com/Freemius/wordpress-sdk/commit/b826574cf889710f6fa9a032f2a71b7ad2309ea0#diff-1fd96b73d06e9d77b0f53ee83dd468deb1efb073cc816c89f38d08ba2afa8102

    Thread Starter forgetme

    (@forgetme)

    Note that WP Rocket is cleared with a custom script that is called with webhook anytime I commit to my github repo.

    Thread Starter forgetme

    (@forgetme)

    Since Easyship has been no help on this issue, I took it upon myself to learn how to fix it myself here are the instructions for anyone that wants to getting these 3 Undefined Index errors in their debug log.

    Open and edit plugin code: /wp-content/plugins/easyship-woocommerce-shipping-rates/includes/easyship-api.php

    Find line 29: public static function init($token = null)

    Replace lines 29-59 with the following:

    
        public static function init($token = null) {
            $Easyship_Shipping_Method = new Easyship_Shipping_Method();
            if(isset($Easyship_Shipping_Method->settings['es_api_key'])) {
                self::$apikey = trim( esc_attr( $Easyship_Shipping_Method->settings['es_api_key'] ), " " );
            }
            if(isset($Easyship_Shipping_Method->settings['es_api_key'])) {
                self::$apiSecret = str_replace( '\n', "\n", $Easyship_Shipping_Method->settings['es_api_secret'] );
            }
            // if incoterms/insurance already exist on WC, send it with API
            self::$is_insured = 0;
            if(isset($Easyship_Shipping_Method->settings['es_api_key'])) {
                self::$taxes_duties_paid_by = $Easyship_Shipping_Method->settings['es_taxes_duties'];
            }
            self::$_currency = get_woocommerce_currency();
            // feature/access_token
            if (!is_null($token)) {
                self::$accessToken = trim(esc_attr($token), " ");
            } else {
                $token_option_name = 'es_access_token_' . get_current_network_id();
                self::$accessToken = trim(esc_attr(get_option($token_option_name)), " ");
            }
    
            // sandbox mode
            // if ( $Easyship_Shipping_Method->settings['es_sandbox_mode'] == 'yes' ) {
            //     self::$oauth_url = "https://auth-sandbox.easyship.com/oauth2/token";
            //     self::$api_url = "https://api-sandbox.easyship.com/rate/v1/woocommerce";
            // }
            if ((self::$apikey == '' || self::$apiSecret == '') && self::$accessToken == '') {
                throw new Exception('Missing API Key and API Secret OR Access Token!');
            }
        }
    

    Your done no more undefined index errors. Note that since this is an edit to the code, you will have to redo it every time Easyship updates their plugin unless they see this and actually fix in their distribution of the plugin.

    Thread Starter forgetme

    (@forgetme)

    Thanks for the information. I can confirm that clicking “Add to Primary Feed” has resolved the error showing up in my logs, but I think what may be the actual issue is that why clicking this was required after the update and everything was fine before the update.

    Thanks.

    Thread Starter forgetme

    (@forgetme)

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 5.5.1
    Current theme: Storefront Child (version 1.0.0)
    Current plugin: WebP Express (version 0.18.2)
    PHP version 7.4.11

    Error Details
    =============
    An error of type E_ERROR was caused in line 162 of the file /public_html/wp-content/plugins/webp-express/vendor/rosell-dk/webp-convert/src/Convert/Converters/Ewww.php. Error message: Maximum execution time of 30 seconds exceeded

    • This reply was modified 4 years, 1 month ago by forgetme.
Viewing 15 replies - 1 through 15 (of 41 total)