WooCommerce Mini-Cart checkout and view cart buttons not displaying when Page Optimize is active

[rw-ye]

Quick summary

The Mini-Cart checkout and view cart buttons do not show when the Page Optimize plugin is active along with some WooCommerce plugins such as WooCommerce Product Bundles.

Error message:

Oops!

Unexpected error in: woocommerce/mini-cart-footer-block

Error: Cannot read properties of undefined (reading '__experimentalUseColorProps')

Video

Screen.Recording.2023-05-25.at.4.39.50.pm.mov

Steps to reproduce

1. Open an AT site.
2. Install WooCommerce
3. Install WooCommerce Product Bundles
4. Activate Page Optimize
5. Activate Product Bundles
6. Add the Mini-Cart block to your site.
7. Select the Mini-Cart on the front end and you'll see the error displaying instead of the checkout and cart buttons.

What you expected to happen

For the View my cart and Go to checkout buttons to display

What actually happened

Error:

Oops!

Unexpected error in: woocommerce/mini-cart-footer-block

Error: Cannot read properties of undefined (reading '__experimentalUseColorProps')

Impact

Some (< 50%)

Available workarounds?

Yes, easy to implement

Platform (Simple and/or Atomic)

Atomic

Logs or notes

Reproduced on Storefront and Tsubaki

Workaround

• Deactivate Page Optimize plugin or disable Concatenate scripts in Page Optimize settings: /wp-admin/options-general.php?page=page-optimize

[rw-ye]

User report: 6326939-zd-woothemes

[github-actions]

Support References

This comment is automatically generated. Please do not edit it.

• 6326939-zen
• 6323366-zen
• 6330326-zen
• 6330454-zen
• 6328048-zen

[rw-ye]

6323366-zd-woothemes

[carinapilar]

Another report on 6330326-zd-woothemes

[shevene]

6330454-zen

[cuemarie]

📌 SCRUBBING : RESULT - Replicated / Could Not Replicate / Uncertain

• Tested on Atomic – Could Not Replicate

📌 FINDINGS/SCREENSHOTS/VIDEO

• So far I'm unable to replicate this problem; tested with Storefront and Tsubaki. Test specifics:
  • WordPress 6.2.2
  • WooCommerce Version 7.7.0
  • WooCommerce Payments Version 5.9.0
  • WooCommerce Product Bundles Version 6.18.6
  • Page Optimize Version 0.5.3
  • PHP Versions 7.4, 8.0
  • Themes: Storefront, Tsubaki

Screenshots/Recordings

uE4OE3.mov

Went back and added WooCommerce Product Bundles Version 6.18.6 after this recording - still no issues with the mini-cart block.

📌 ACTIONS

• Requested author feedback

📌 Message to Author

• @rw-ye @carinapilar @meetshevene - are your users still seeing this issue? Can you spot anything I'm missing in my recording that may explain why this isn't replicating at the moment?

[carinapilar]

@cuemarie, the user I got had Woo’s Product Bundles active too, only worked after deactivating Page Optimize. I also had all other plugins deactivated.

[rw-ye]

@cuemarie I tried with WooCommerce Payments and can't replicate it now. However, I can still consistently replicate this issue with WooCommerce Product Bundles active. Updated the original post.

The plugins I have active are:

• WooCommerce Version 7.7.0
• Page Optimize Version 0.5.3
• WooCommerce Product Bundles Version 6.18.6

On WordPress 6.2.2 and both PHP 7.4 and 8.0

[zdenys]

6328048-zd-woothemes

[cuemarie]

Ok, looks like this was also reported here:

• Conflicts between Mini-Cart block, Page Optimize and Product Bundles woocommerce/woocommerce-blocks#9584

And was resolved by this fix: woocommerce/woocommerce-blocks#9586

Having WooCommerce Blocks (which supports Mini-Cart) active and up to date (v10.3.0 released 2 days ago) on my site resolves the issue.

📌 ACTIONS

• Closing as fixed

📌 Message to Author/HEs

• please make sure your customers have WooCommerce Blocks installed and up to date to resolve this error!

[cuemarie]

Since Woo folks have had very busy queues, I've gone ahead and replied to all the users whose interactions were shared above and asked them to install and activate the latest version of WooCommerce Blocks to resolve the issue. 👍

[mdtanjid0]

I encountered a similar problem where the user was still experiencing difficulties. Upon investigation, I discovered that the user had not installed the WooCommerce Blocks plugin. Installing the plugin resolved the issue. This is just a heads-up.