Conflict with WordPress 6.0 / Woocommerce

  • Resolved mmwdesign

    (@mmwdesign)


    2 years, 9 months ago

    Sold Out Badge plugin Causing conflict with WP 6.0 / Woocommerce:
    There has been a critical error on this website. message appears in Woo Home tab, Customers tab and Status tab, on activation.
    Still works on front end.

    Error log:

    WordPress version 6.0
Active theme: Beaver Builder Child Theme (version 1.0)
Current plugin: Sold Out Badge for WooCommerce (version 4.3.1)
PHP version 8.0.20
Error Details
=============
An error of type E_ERROR was caused in line 301 of the file /var/web/site/public_html/wp-content/plugins/sold-out-badge-for-woocommerce/vendor/htmlburger/carbon-fields/core/Loader/Loader.php. Error message: Uncaught TypeError: array_merge(): Argument #1 must be of type array, null given in /var/web/site/public_html/wp-content/plugins/sold-out-badge-for-woocommerce/vendor/htmlburger/carbon-fields/core/Loader/Loader.php:301
Stack trace:
#0 /var/web/site/public_html/wp-content/plugins/sold-out-badge-for-woocommerce/vendor/htmlburger/carbon-fields/core/Loader/Loader.php(301): array_merge(NULL, Array, NULL, NULL, NULL, NULL, Array)
#1 /var/web/site/public_html/wp-includes/class-wp-hook.php(307): Carbon_Fields\Loader\Loader->initialize_widgets(Object(WP_REST_Server))
#2 /var/web/site/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
#3 /var/web/site/public_html/wp-includes/plugin.php(476): WP_Hook->do_action(Array)
#4 /var/web/site/public_html/wp-includes/rest-api.php(561): do_action('rest_api_init', Object(WP_REST_Server))
#5 /var/web/site/public_html/wp-includes/rest-api.php(519): rest_get_server()
#6 /var/web/site/public_html/wp-includes/rest-api.php(2868): rest_do_request(Object(WP_REST_Request))
#7 [internal function]: rest_preload_api_request(Array, '/wc-analytics/r...')
#8 /var/web/site/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/Settings.php(144): array_reduce(Array, 'rest_preload_ap...')
#9 /var/web/site/public_html/wp-includes/class-wp-hook.php(307): Automattic\WooCommerce\Internal\Admin\Settings->add_component_settings(Array)
#10 /var/web/site/public_html/wp-includes/plugin.php(191): WP_Hook->apply_filters(Array, Array)
#11 /var/web/site/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/WCAdminSharedSettings.php(61): apply_filters('woocommerce_adm...', Array)
#12 /var/web/site/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/Assets/AssetDataRegistry.php(258): Automattic\WooCommerce\Internal\Admin\WCAdminSharedSettings->Automattic\WooCommerce\Internal\Admin\{closure}()
#13 /var/web/site/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/Assets/AssetDataRegistry.php(359): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->execute_lazy_data()
#14 /var/web/site/public_html/wp-includes/class-wp-hook.php(307): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->enqueue_asset_data('')
#15 /var/web/site/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
#16 /var/web/site/public_html/wp-includes/plugin.php(476): WP_Hook->do_action(Array)
#17 /var/web/site/public_html/wp-admin/admin-footer.php(95): do_action('admin_print_foo...')
#18 /var/web/site/public_html/wp-admin/admin.php(297): require_once('/var/web/site/p...')
#19 {main}
  thrown
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Charlie Etienne

    (@charlieetienne)

    Hi, I think the problem is php8 here. Since WordPress and plugins/themes ecosystem is not really ready for php8, I didn’t try to make it work. But I will.

    Charlie

    Thread Starter mmwdesign

    (@mmwdesign)

    Cheers Charlie, Yes, seemed to be related?to php8 (was fine when reverted to 7.2).? Debugging this end led to an older child theme issue—once I updated that the issues have not reappeared.

    Plugin Author Charlie Etienne

    (@charlieetienne)

    Glad to hear that. On my side, I checked with php8 and didn’t find any issue.

    Cheers,

    Charlie

    Hi Charlie

    I got this message at 15:27 BST 27-06-22:

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Sold Out Badge for WooCommerce.

First, visit your website (******) and check for any visible issues. Next, visit the page where the error was caught (https:******wp-login.php) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.

https://****/wp-login.php?action=enter_recovery_m*******a&rm_key=DyMbFAhBQflW2525guqOVW

To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.0
Active theme: AHTC Theme (version 4.9.0.1613239828) Current plugin: Sold Out Badge for WooCommerce (version 4.3.2) PHP version 7.2.34

    I have version 4.3.2 installed and have had to deactivate it via recovery mode.

    I see that you last updated the plugin 2 hours ago, but I had issues since then.

    Plugin Author Charlie Etienne

    (@charlieetienne)

    Whoops, sorry. I just published a 4.3.3 which reverts buggy 4.3.2.

    Charlie

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Conflict with WordPress 6.0 / Woocommerce’ is closed to new replies.