Woocommerce error after 1.11.0 update

What kind of product add-ons cause the trouble? Can you explain how I could reproduce this bug?

Have a site that uses WooCommerce and Woocommerce Product Add-on plugin. When a user adds a simple product to the cart it works, when they add a variable product it works, but when they add a product that has an add-on, nothing happens (when on the latest version of WP Super Cache). When I roll back to 1.10.0 all works fine again.

OK, I’ll try that but if you enable the debugging in this plugin, try to replicate the problem with both versions of the plugin. Maybe the logs will show that a cache file was deleted, or caching was disabled, in the old version.

I tested Woocommerce with the custom product addon but it worked ok from what I saw.

I created a product, and added a custom field. I saw the custom field in the product on my site. Adding it to the cart used a POST so the next page wasn’t cached and I saw a “X has been added to your cart.” message.

Due to how complex Woocommerce is, I can’t replicate your site, but hopefully the debug log will reveal why it doesn’t work for you.

Hi, I’m using this plugin: https://woo.com/products/product-add-ons/

OK, can you test that plugin with the old and current versions of WP Super Cache with debugging enabled? Hopefully, the debug log will reveal why it doesn’t work correctly.

Hi, so I tested the 1.11.0 with DEBUG on and this is an error I get:
Warning: Cannot modify header information – headers already sent by (output started at /***/***/*****/********/wp-content/plugins/gravityforms/includes/fields/class-gf-field-list.php:167) in /usr/www/users/lovelycqdv/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 1544

Sorry for the late reply. Did you try debugging in the WP Super Cache plugin? Not WP_DEBUG, Go to the debug tab and enable logging there.

That warning is a problem with Gravity Forms sending information to the browser too early in the process. Not something that WP Super Cache can fix.

I have not tried that. Will give that a try and report back.

Sounds like a plan! When you have news, please let us know.

Hi @maginem,

Do you have updates about that? While we don’t want to rush you, we usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!