"Virtual" won't stay checked on product

Nothing special. In system status what is your max input vars set to?

PHP Max Input Vars is set to 1000

Can you install the plugin mentioned here and then save your product page: https://docs.woocommerce.com/document/problems-with-large-amounts-of-data-not-saving-variations-rates-etc/#section-4. It will let us know if the issue is with max_input_vars.

If you get an error alert from that plugin when saving the product, then you’ll need to increase the max_input_vars value: https://docs.woocommerce.com/document/problems-with-large-amounts-of-data-not-saving-variations-rates-etc/#section-2

Thanks for the suggestion. I installed the “WP Max Submit Protect” plugin and activated it. Nothing seems to have changed. I edit a product, click “virtual” then click “update” and the “virtual” field unchecks itself. Other product changes are saved correctly. The new plugin didn’t produce any obvious warnings about the max_input_vars settings.

Hmm, maybe something is conflicting with WooCommerce.

Try temporarily switching back to the WordPress Twenty Sixteen Theme, or Storefront, and disable all plugins except for WooCommerce. If that resolves the issue, then slowly re-enable features until you find the one that’s causing the conflict.

I will give that a try but it may be a couple of days. This is a live, production site we picked up maintenance for. I’m going to set up a duplicate of it on one of our dev servers where I can do more intrusive testing like you’re talking about without disturbing the live site.

Okay, no problem. Just let us know if you need more help after doing that debugging process.

Caleb – I am having the same issue with my website, except it’s the Membership checkbox that will not stay checkmarked. It only works on one of the 3 variations I’ve created (digital book only, digital package, paperback book only, paperback package – only the digital package retains the checkmark when I save the variations).

Did you all ever figure out why – and can you pls help me figure out this issue? I can start a new thread if need be, or we can continue here since it is pretty much the same problem.

Thanks,
Andrea

No, I was never able to determine the cause, nor was I able to reproduce the problem on another server. The client didn’t have the budget to investigate further, so we found an alternate way of doing what they wanted that didn’t involve using the faulty “virtual” field.

It does seem to me in general though that the plugin shouldn’t drop UI settings without at least displaying some kind of warning (e.g. “requested setting ignored because X”).

-Steve