Last update conflict with custom fields plugin ACF

Hi @ratamatcat

It appears certain custom fields (select, and taxonomy field types) are having trouble rendering or similar. Before and after below

This is a third-party plugin, and we don’t provide help & support for 3rd-party plugins or themes as they’re outside our support scope. It would be best to reach out to the plugin developer for further assistance.

Also a side issue was I couldn’t deactivate Woo initially, I had to deactivate my other plugins first, why would this be?

To deactivate WooCommerce, you’ll first need to deactivate any WooCommerce extensions you’re using. WooCommerce is necessary for these extensions to operate, so you can’t deactivate it while they’re still active.

I hope this clarifies your concern. If you have any other questions, feel free to ask.

Hi Shameem,

Thanks for your thoughts.

I sent the same info to ACF and am waiting their response.

I wouldn’t know if the Woocommerce or ACF have something problematic in the code, but the update of Woocommerce is what brought the issue, so thought it proper to report it here.

Thanks

@ratamatcat can you please link your post on ACF’s support forum? I’m having the exact same issue (I confirm it does the same, some “Select2” fields of ACF simply don’t render correctly) and would like to follow that thread. Thanks!

Hi @ratamatcat,

I sent the same info to ACF and am waiting their response.

Please keep us updated on their response.

but the update of Woocommerce is what brought the issue, so thought it proper to report it here.

On a staging site, please try rolling back WooCommerce to the previous version and check if the issue persists. You can use a plugin like WP Rollback to rollback the version of WooCommerce.

Be sure to have a full site backup in place.

Let us know how this goes.

Hey @ckadenge,

I also noticed the issue on a live website after updating WC to 9.2.1, I checked an offline copy of the same site and it worked correctly, once I ran the WC update it also started to display those (apparently random) broken dropdown fields. I’m not 100% sure the issue stems from the 9.2.1 update since I wasn’t smart enough to note down the version I had on the offline site before, so it might be another fairly recent release. The issue is only with the ACF fields, though, so it’s probably something on their part. Staying tuned.

Hello lupusyon,

Thank you for your message here.
We appreciate you for sharing information.

Let’s wait for a reply from @ratamatcat and see what ACF support has to say.
I will be happy to help resolve this problem if the issue originates from WooCommerce.

Have a great day!

I have the same problem and i did several rollbacks of both plugins until i came down to version 9.1.0 of Woocommerce and now it works fine… I hope this gets solved. I can confirm this is a problem with WooCommerce as i did rollbacks for ACF too, and they didn’t work until i rolled back Woocommerce to 9.1.0

• This reply was modified 3 months ago by EmirJulian.

Hi @emirjulian,

Just curious, were you able to try using the latest version 9.2.1 of WooCommerce with ACF and check if the same issue persists?

Hi @ckadenge … yes… I did several rollbacks until 9.1.0 worked.

9.2.1 was the version i got when the problem appeared.

• This reply was modified 3 months ago by EmirJulian.

Hi @ratamatcat, @lupusyon, @emirjulian (and anyone else who may be reading this!).

This is a known conflict issue with the latest version of WooCommerce, which you can learn more about here: https://github.com/woocommerce/woocommerce/issues/50847.

The good news is I see there’s work already done to revert this change:?https://github.com/woocommerce/woocommerce/pull/50854, so this should be fixed soon!

I’ll mark this thread as resolved for now, as the bug is confirmed, and a release is coming soon. Feel free to start a new thread or reply if you have any more questions.

Thanks!
Omar

Thank you, @omarfpg! i guess we all be waiting for a permanent fix now!

Thank you all!