KevinPlusPlus

6.5.6 has resolved the issue. Thank you!

For us this ended up being caused by the MultiCurrency Pro plugin, with some changes it functions correctly with WC 8.3.

Not sure if you use this plugin as well, dyamized, or if there may be other plugins with incompatible JavaScript.

Bug report submitted here: https://github.com/woocommerce/woocommerce/issues/41556

Hi, one more comment as I’ve tested further:

$in_footer = array( ‘strategy’ => ‘async’)

Also works. But defer does not.

I have found the problem.

In /includes/class-wc-frontend-scripts.php:

In static_function_register_script and static_function_enqueue_script, the last parameter $in_footer was changed from

$in_footer = true

to

$in_footer = array ( ‘strategy’ => ‘defer’)

Changing this back to true, checkout works again.

Here is the commit that broke this functionality: https://github.com/woocommerce/woocommerce/commit/fe6e43b438710ecd3b0a97bfbe74bc6559a3db69

Kevin

Sorry I didn’t include this in my previous post, but I confirm that using 8.2.2, POST /?wc-ajax=update_order_review is called when loading checkout.

Under 8.3, this same wc-ajax call is NOT MADE and thus the card fields fail to load.

To Woo Support: can you please try this on your test / staging environment with the Stripe payment plugin specifically?

Kevin

Hello,

I am also using the checkout shortcode and the display for Stripe and Braintree card fields both do not load after the update to 8.3. Using the Stripe and Braintree plugins from the official WooCommerce site.

Under 8.2.2, there is an AJAX call made in the background where the spinning circle comes up and loads the card fields.

Under 8.3, this does not happen, no AJAX call, no spinning circle, and the card fields are just AWOL.

I think something is broken.

Thanks,

Kevin

Bug report also submitted on Github #39006

Ryan,

Thanks for the update. In the meantime I have changed this method on our server just to set an empty array and return an empty array so the warning is removed.

Kevin

Hello,

Same issue here.

The cause is:

global $avia;
$avia->style->print_extra_output = false;

If the Enfold theme is not installed, $avia is null.

Kevin

Tobias,

Yes, it is a strange one. Thanks for your help!

Kevin

Tobias,

I have been reading about this and it seems that SCRIPT_FILENAME may not always be set. For example: https://www.php.net/manual/en/reserved.variables.server.php

Data: $_SERVER[‘SCRIPT_FILENAME’]
Data type: String
Purpose: The absolute pathname of the origin PHP file, including the filename
Caveat: Not set on all PHP environments, may need setting by copying from __FILE__ before other files are included.

I did some additional testing and this is unique to running from a cron job. If I run from the command line:

php [full path removed for security]/wp-cron.php

there is no warning. Run the same commandnd run from the cron job does generate the warning. It seems that this just a quirk of how the PHP job is spawned, perhaps because of running as root for the cron job?

I don’t see any harm in re-arranging the order, the checks accomplish exactly the same thing and prevents a warning on this border case. PHP 8 is very strict about accessing non-existing array elements. If you are reluctant to re-order them, how about checking if the array index exists before accessing it, which is a better programming practice especially under PHP 8.

( isset($_SERVER[‘SCRIPT_FILENAME’]) && ‘wp-login.php’ === basename( $_SERVER[‘SCRIPT_FILENAME’] ) )

Thanks,

Kevin

Jordan,

Unfortunately, with 2.5.4 we have a new one:

PHP Warning: Undefined array key “detail” in /mailchimp-for-woocommerce/includes/api/class-mailchimp-api.php on line 1898

It seems that the ‘detail’ array element is being referenced when it may not exist:

throw new MailChimp_WooCommerce_Error($data[‘detail’], (int) $data[‘status’]);

Thanks,

Kevin Hock

Jordan,

Thank you so much, appreciate it!

Kevin

Hi,

Yes, sorry, my bad. The other is line 698, function get_recipients.

Kevin