WooCommerce 8.6 Upcoming Fixes: Checkout Page, Product Page, and Compatibility with Woo Subscriptions

rodelgc Avatar
rodelgc

•

After the release of WooCommerce 8.6, we received reports from users who encountered the following issues:

  • [Fix in progress] Stores with Woo Subscriptions started getting fatal errors when adding or editing a subscription in WP Admin.
  • [Fix in progress] Some stores started having a broken Checkout block or checkout page after upgrading from WooCommerce 8.5.2 to 8.6.
  • [Under investigation] Product pages not showing up on certain stores, and we will include a fix for it as well after investigating and testing it.

We are preparing a fix for the following issues. You may monitor their progress via these two pull requests:

  • Don’t render attribution metabox for non-supported order types. (#44680)
  • Prevent script caching by using the WC Core version to hash WC blocks assets instead of old WC Blocks version (#44676)

We are currently investigating the following issue. You can monitor its progress here:

  • Upgrading to WP WooCommerce plugin 8.6.0 causes product page showing blank content for unauthenticated users (#44679)

How can I tell if this affects me?

If you are a store admin and your store is using Woo Subscriptions, you might encounter a fatal error when you log in to WP Admin and navigate to WooCommerce > Subscriptions, and then try to add a new subscription or edit an existing one. The error would be something similar to Uncaught Error: Call to undefined method WC_Subscription::get_report_customer_id() in /srv/htdocs/wp-content/plugins/woocommerce/src/Internal/Admin/Orders/MetaBoxes/CustomerHistory.php:28

You might also get the same fatal error when adding or editing other order types from plugins you are using.

If your store is using the Checkout block and had recently upgraded to WooCommerce 8.6 from 8.5.2, some of your customers might get an error message either on the checkout page or on other pages that have the checkout block. The error could be something similar to Oops! Unexpected error in: woocommerce/cart-order-summary-block. Error: Cannot read properties of undefined (reading 'call').

You may also receive reports from some of your customers that the product pages of your store are either rendered as empty pages, or not loading at all.

What action should I take?

If you are experiencing any of these issues, here’s what you can do.

If you are affected by the fatal error when adding or editing certain order types:

If your store has broken checkout page or checkout block:

  • Try installing this plugin Transients Manager or any Transient plugin, and deleting these transients:
    • woocommerce_blocks_asset_api_script_data 
    • woocommerce_blocks_asset_api_script_data_ssl

If your store does not load the product pages correctly:

  • It’s likely that you are using the product_page shortcode. Try removing the status attribute from it.

What happens next?

We are aiming to release WooCommerce 8.6.1 very soon to patch these issues. We will make the announcement here on the WooCommerce Developer Blog.

Thank you

Another big thanks to our community members for reporting these issues and helping us gather the data we need to resolve them. Special thanks to dshapovalov1971 for submitting #44679, and to thomasmb for doing an initial investigation to the possible cause of that issue.

Keep yourself in the loop!

This field is hidden when viewing the form
This field is hidden when viewing the form
This field is hidden when viewing the form

17 responses to “WooCommerce 8.6 Upcoming Fixes: Checkout Page, Product Page, and Compatibility with Woo Subscriptions”

  1. danielspain Avatar
    danielspain

    Hi, thanks for the fixes…when we could exxpect the 8.6.1 fixes…in the weekend or after monday perhaps? Just asking for proper planning…Thanks in advance

    Reply
    1. Beau Lebens Avatar
      Beau Lebens

      We’re aiming for early next week; either Monday or Tuesday.

      Reply
    2. Julia Amosova Avatar
      Julia Amosova

      We just published an update here https://developer.woocommerce.com/2024/02/16/woocommerce-8-6-updated-fix-release-details/ – please take a look for details.

      Reply
  2. tsukii Avatar
    tsukii

    Removing transients successfully fixed the broken cart.

    Reply
  3. Mark Avatar
    Mark

    Any chance there are downgrade options? Also, I know for a fact that I’m not using the product_page shortcode – I am just calling the normal “the_content” call on a single-product.php page.

    An odd thing is happening though: when I am logged in (to my Admin account), I can view the Shop, and all Product details normally. I can even add to cart and check out.

    However, as soon as I log out, when I try to view a single product, the details are gone.

    Reply
    1. MaFt Avatar
      MaFt

      I am seeing this as well.

      Logged in then the_content() for products is all fine. But if not logged in then no product details are shown.

      I downloaded the 8.5.2 from the WordPress site here: https://en-gb.wordpress.org/plugins/woocommerce/advanced/

      Reply
  4. Davon Avatar
    Davon

    I had a problem displaying orders, and I noticed several other sites seem to be reporting similar, will that be in the fix update?

    Reply
  5. Ian Dunn Avatar
    Ian Dunn

    It looks like by store is affected by this. My sales came to an abrupt halt last week! None of my items in my store will load. Sometimes they load after refreshing the browser. I’m glad I found this page, and I’m glad a solution is in the works. Thanks for your efforts! You can see my store at http://www.boltind.com
    Thanks!!!
    Ian

    Reply
  6. chris Avatar
    chris

    Same problem here fon NON logge-in user with the normal use of the_content(); single page display nothing!
    Only logged-in user can display products…. lol

    Reply
  7. Attilio Urciuolo Avatar
    Attilio Urciuolo

    Hello, i have problem with order details ( CUstomer History )

    2024-02-19T08:52:40+00:00 Critico Uncaught Error: Call to undefined method WC_Order::get_report_customer_id() in /home/admin/domains/emarketworld.it/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/Orders/MetaBoxes/CustomerHistory.php:28 CONTEXT: {“error”:{“type”:1,”file”:”\/home\/admin\/domains\/emarketworld.it\/public_html\/wp-content\/plugins\/woocommerce\/src\/Internal\/Admin\/Orders\/MetaBoxes\/CustomerHistory.php”,”line”:28},”backtrace”:[“”,”#0 \/home\/admin\/domains\/emarketworld.it\/public_html\/wp-content\/plugins\/woocommerce\/src\/Internal\/Admin\/Orders\/Edit.php(271): Automattic\\WooCommerce\\Internal\\Admin\\Orders\\MetaBoxes\\CustomerHistory->output()”,”#1 \/home\/admin\/domains\/emarketworld.it\/public_html\/wp-admin\/includes\/template.php(1456): Automattic\\WooCommerce\\Internal\\Admin\\Orders\\Edit::Automattic\\WooCommerce\\Internal\\Admin\\Orders\\{closure}()”,”#2 \/home\/admin\/domains\/emarketworld.it\/public_html\/wp-admin\/edit-form-advanced.php(707): do_meta_boxes()”,”#3 \/home\/admin\/domains\/emarketworld.it\/public_html\/wp-admin\/post.php(206): require(‘\/home\/admin\/dom…’)”,”#4 {main}”,”thrown”]}

    Reply
  8. Nigel Stevenson Avatar
    Nigel Stevenson

    Hi folks,

    WooCommerce 8.6.1 has been released and the related post is here:
    https://developer.woocommerce.com/2024/02/20/woocommerce-8-6-1-fixes-to-issues-introduced-in-8-6-0/

    Thanks!

    Reply
  9. Ian Dunn Avatar
    Ian Dunn

    My items are able to load again. Thank you for the resolution! Now I hope I can get back on track with my sales. I was just starting to gain some steam.

    Reply
  10. Helen Seyoum Avatar
    Helen Seyoum

    Hi, my order page is not showing anything except the delete button. I could not take orders. it has been 2 days and is so frustrating. Is the issue going to be resolved soon or is there anyting else I can do on my end? Please advise me.

    Reply
    1. pia8c Avatar
      pia8c

      Hi Helen, have you upgraded to 8.6.1 yet? The fixes were pushed recently: https://developer.woocommerce.com/2024/02/20/woocommerce-8-6-1-fixes-to-issues-introduced-in-8-6-0/

      Let us know if you are still experiencing issues after the update.

      Reply
  11. Sven Moller Solis Avatar
    Sven Moller Solis

    Hello,

    With 8.6.1 I dont have broken checkout but I can see in the logs:

    WordPress database error Commands out of sync; you can’t run this command now for query UPDATE `wp_options` SET `option_value` = ‘1713046242’ WHERE `option_name` = ‘_transient_timeout_woocommerce_blocks_asset_api_script_data_ssl’ made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Blocks\Assets\Api->update_script_data_cache, set_transient, update_option

    Reply
  12. Andrew Driver Avatar
    Andrew Driver

    Hi

    I’m still having issues with WooCommerce not working with Stripe. Payments are failing but there are no error logs in either WP or Stripe. My Stripe portal works for all other payments types.

    I am using WC 8.8.2, WooCommerce Stripe Gateway 8.2.0 and WP Theme Bridge – Qode which is up to date.

    Could anyone help?

    Reply
    1. Brent MacKinnon Avatar
      Brent MacKinnon

      Hi Andrew, if you’re unable to resolve the Stripe payment issues on your own, a great first step would be to reach out to the WooCommerce support team. We may be able to help you troubleshoot the integration between WooCommerce and the Stripe payment gateway, and identify any potential conflicts with your specific setup.

      Plugin conflicts can sometimes interfere with payment processing, so ruling out this potential issue may help narrow down the problem as well.

      If you’d like to troubleshoot further on your own, try testing for plugin and theme conflicts:
      https://woocommerce.com/document/how-to-test-for-conflicts/

      If the WooCommerce support team is unable to resolve the issue, and you’ve confirmed there are no plugin conflicts, feel free to give us a shout in the Woo Community Slack and I’ll see if I can help you find next steps.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *