ManageWP Disconnects Site Using Your Plugin

Hi @doctormicro,

Thanks for your question!

We are aware of a conflict with WooCommerce Payments and ManageWP, they are correct. An issue for that is here in GitHub: https://github.com/Automattic/woocommerce-payments/issues/2805

You can see a similar forum topic on the issue here as well:
https://www.ads-software.com/support/topic/problem-with-2-9-0/

Developers have already found a fix for that conflict. We expect that this fix will be included in the next release, but we do not have a date for that yet.

A workaround would be to revert to a previous version of WooCommerce Payments for now. You can get that from the bottom of the Advanced View page. Scroll down, select 2.8.4, then download.

Thanks for your patience while the fix is released, and let us know if you need anything else!

Thank you, for the quick reply.

I’m happy to hear that you have fixed this for the next update and appreciate the work-around.

Hi @doctormicro,

Glad to have helped. We will mark this issue resolved now.Thanks.

Not sure why this is marked as fixed. It is not — I had reached out to support via email on this topic and they stated that it should be fixed in the next update (2.9.1). Updated to 2.9.1 today and still getting the following error in ManageWP:

Argument 1 passed to WC_Payments_Fraud_Service::send_forter_token() must be of the type string or null, array given, called in /home2/texasem2/public_html/wp-includes/class-wp-hook.php on line 303 occurred in wp-content/plugins/woocommerce-payments/includes/class-wc-payments-fraud-service.php on line 202 please make sure that your website is accessible

Hi @urbancowboy1994,

Thanks for reaching out to us.

I have checked the issue that was reported in GitHub: https://github.com/Automattic/woocommerce-payments/pull/2808 and I can see that the fix is already done but it wasn’t released in 2.9.1 as it was a hotfix release.

I have checked with our developers and they confirmed that the fix will go into a future major release of WooCommerce Payments which in this case, it will be version 3.0.0.

Yet, I can’t tell from the records when this version will be released.

Hope that helps, and let us know if you have any other questions. We would be happy to assist further.

@nagdy,

That’s unfortunate — I see no reason that it shouldn’t have been immediately released if the issue was indeed fixed. Now you have all these sites running an outdated version (2.8.4) just so our developers have wp-admin access.

Please urge your devs to push this patch in the next minor release seeing as though there is no anticipated release date for 3.0.0.

Hi there!

The reason for that is because we had to create a new update before the scheduled date, but we weren’t able to test with all the other fixes/improvements (such as the merge that fixes this specific issue).

Anyway, version 3.0.0 is scheduled for September 15, so that should be 1 week from today. ??

The only option in the meantime is to create a custom patch from your end following the PR code changes, but that is not something that we would be able to do from our end.

Feel free to get back to us anytime if you need further help.

@felipea8c,

September 15th, got it — thank you for that update! I assume 1 more week on 2.8.4 is acceptable.

Thank you all for your time.

You are most welcome @urbancowboy1994 we will mark this thread as resolved for now.

Let us know if the issue persists after updating. We’d be happy to take a look.

UPDATE: ManageWP has released an updated version (4.9.10), which appears to have fixed the issue from their end. I guess they heard enough of our complaints and took the liberty to patch as promptly as possible, more or less what I was hoping y’all would do instead of waiting for 3.0.0.

Anyways, hope this helps!

*Resolved*