Dustin L.

By the way, I haven’t tested it. When I am on the WordPress Dashboard and go to WooCommerce > Settings > Advanced > Features… I see a warning that Password Strength Settings for WooCommerce isn’t compatible.

View post on imgur.com

That’s great to hear! If the plugin is compatible, it would be helpful if you declared that.

Currently, Password Strength Settings for WooCommerce is listed as an incompatible plugin. I’m guessing this is because you haven’t added the code to declare compatibility.

You can learn more here:

High Performance Order Storage Upgrade Recipe Book

Supporting High-Performance Order Storage

Declaring extension (in)compatibility

Hi @anastas10s,

Thank you for getting back to me.

Yes, your understanding is correct. It appears that the order status didn’t get changed from failed to completed in the normal way (although it did somehow get changed). This caused other plugins that rely on the standard “signal” of the order status change never to get it and not function as expected.

I don’t know how to reproduce this. Do you? I would need to force Stripe to use SCA in a test environment only and force it to fail SCA. I checked the WC Stripe documentation, but this wasn’t covered.

I’m using WP 6.2.2, WC 7.7.2, and WC Stripe 7.4.1. All other plugins are up-to-date.

I noticed the “Error during status transition” order note I saw was left by some error handling built-in to WooCommerce’s status_transition() function.

By the way, I also have a ticket opened with your chat/email support – #6360186.

• This reply was modified 1 year, 9 months ago by Dustin L..

@dcsupport I do not have the extended version

@dcsupport ,

Thank you for working on this. I took the staging site down for now. I can recreate it later and test your fixes if needed.

I decided to go with a different product addons plugin that doesn’t conflict with WP Armour.

https://www.ads-software.com/plugins/woo-custom-product-addons/

@dcsupport By the way, I reached out to the developer of WooCommerce Gravity Forms Product Add-ons. He mentioned “the user isn’t the one submitting the information, WooCommerce is.” Maybe this is a hint as to how this might be resolved.

@dcsupport Thanks for the reply. I enabled registration. I also disabled the requirement for users to be registered and logged in to comment.

Upon further testing, 1.8.7 seems to fix the problem.

• This reply was modified 2 years, 2 months ago by Dustin L..

No. The workaround is to keep the Application Passwords v0.1.2 plugin activated.

Just wanted to report that this problem still exists with Application Password 0.1.3 and WordPress 5.7.2.

Everything is working with WP 5.7.2 and Application Password 0.1.2. I can remotely send commands to this WP installation and authenticate via Application Passwords.

If I remove Application Passwords OR upgrade to 0.1.3, I can no longer authenticate.

I have tried adding a new password but still can’t authenticate.

Thanks! I reported the issue to WooCommerce. The support rep was able to reproduce the issue and will open a bug ticket in their system.

Yes, it’s definitely due to a change in AutomateWoo. I know it was introduced sometime after version 4.9.6 – changelog – . I contacted WooCommerce, who provides support for AutomateWoo, and they weren’t helpful.

I found your email on your website. I’ll email you the plugin in case you’d be willing to look into it.

Thank you

• This reply was modified 4 years, 7 months ago by Dustin L..

I switched to Category and Taxonomy Image. It seems to work alright.

Seems related to this open issue.

https://github.com/Automattic/jetpack/issues/8161