Pro's WooCommerce Checkout Editor Incompatible w/WooCommerce 3.4

Support
#1

Hey guys -

Besides all the bugs I pointed out in my last ticket on this topic, we discovered that optional checkout fields are now suffixed with “(optional) (optional) (optional)”.

This plugin should have been properly tested with WooCommerce 3.4 well before Woo’s official release. The beta has been available for months. Why don’t you guys test your plugins BEFORE the update is released like everyone else on the planet? It’s very unusual.

Hope you guys can fix this plugin really soon. It’s a mess.

#2

Hi co50,

We tried but we couldn’t replicate the bug. We only get a single “(optional)” suffix.

Can you send us the page URL with this issue in a secure note so that we can have a closer look and suggest you a solution?

Thanks.

#3

See this video: https://youtu.be/ny80jrYAQ1g

I don’t want to provide my WP login for this client because ultimately there is a bug in the plugin that needs to be fixed - lots of bugs actually of which this is just one. We’ll find a workaround even if it means switching back to Woo’s own version. But you should really have someone fix all the issues with this plugin. Thx.

#4

Hi,

Please note that the latest supported version by the theme is woocommerce V3.3.5

It’s in our Version Compatibility page - https://theme.co/apex/forum/t/troubleshooting-version-compatibility/195

Kindly roll back to that version - https://github.com/woocommerce/woocommerce/archive/3.3.5.zip

Thanks

#5

You guys have to have your theme ready for major WooCommerce releases before they are released…with GDPR this was a gigantic oversight on your part. WooCommerce 3.4 brings the system into compliance with GDPR and thus is pretty much a required update. To ensure compliance with EU law, we had to upgrade applicable clients immediately. You should have been ready. Talk to Rubin about this, please.

#6

Hey @co50,

Matt from the leadership team here. Thanks for bringing this to our attention. I’ve taken on board your comments and we will of course, address any compatibility issues.

Appreciate your thoughts on this and, as well as your continued custom.

1 Like
#7

FYI WooCommerce 3.4.1 fixes the issue described in this ticket. Apologies for not knowing if this was your plugin or Woo’s bug.

#8

Hello @co50,

Thanks for updating the thread.

We have taken this into consideration and our developers are working to address the issues reported by our customers.

Thanks.

#9

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.