Related: Clean Talk is Blocking ThriveCart
-
We ran across a similar/related issue (compared to this old post) where CleanTalk was catching ThriveCart API calls to our MemberPress installation and marking new user emails as spam (due to the ThriveCart IP addresses). As a result, new members were not getting added to WordPress/Memberpress after a successful ThriveCart purchase.
Solution
For some background, we have ThriveCart (which leverages AWS and dynamic IPs) setup to leverage the MemberPress integration.After doing some research, we decided to adjust the CleanTalk config within our WordPress setup by adding a RegExp URL Exclusion within Settings for Anti-Spam by CleanTalk (under advanced settings):
(\/wp-json\/mp\/v1\/)
- Make sure to check the box by “Use Regular Expression in URL Exclusions”
That RegExp should work for all MemberPress REST endpoints that ThriveCart needs to hit. As for peace of mind, we know that ThriveCart is the ONLY integration using MemberPress REST endpoints. Nonetheless, we will monitor the WordPress users emails against the CleanTealk Blacklist to make sure nothing slips through.
How we determined what RegExp to write
Below are some MemberPress Developer Tools REST URLs examples:/wp-json/mp/v1/transactions/:id
/wp-json/mp/v1/members
/wp-json/mp/v1/subscriptions/:id
After making those configuration/setting adjustments. We have done a few tests and no longer see CleanTalk blocking the addition of a user to MemberPress after a successful ThriveCart purchase (leveraging a fulfillment to a MemberPress integration).
Note, the other (old) post doesn’t use Memberpress for they use Thrive apprentice instead. This exclusion solution should work for any integration that has a common URL pattern for REST API calls into WordPress from ThriveCart.
I hope this helps the next person that comes across a similar ThriveCart and CleanTalk issue.
- The topic ‘Related: Clean Talk is Blocking ThriveCart’ is closed to new replies.