My organization is looking to create a membership website and has chosen to use Memberpress along with Uncanny Automator. However, we have been experiencing difficulty obtaining helpful support from both plugin teams. We have received vague responses directing us to their knowledge base, which does not address the issue, or redirecting us to each other’s support team.
Our primary issue is that when a user signs up for our Full Membership, WordPress sets their role as Subscriber, while Memberpress assigns them a secondary role of Full Membership. We are attempting to use Uncanny Automator to detect when a Memberpress membership expires, and then have WordPress change the user’s primary role to “Expired Member.” You can view the Uncanny Automator recipe settings we have used in this [screenshot])
To test the workflow, we created a few test accounts by signing up for Full Membership in Memberpress. However, we are uncertain if the workflow is functioning correctly and are seeking guidance on how to proceed.
We have gone into the Memberpress settings under transactions and manually expired the test accounts. We have verified that their subscriptions are no longer showing as active and are now expired according to the “Expires On” date displayed.
However, despite the subscriptions being expired, Uncanny Automator is still failing to detect that the membership has expired, and as a result, the Uncanny Automator recipe is not triggered. This, in turn, means that WordPress is not automatically changing the user’s primary role to “Expired Membership” as per our workflow.
We are not sure what is causing this issue, as we have followed the recommended settings for the Uncanny Automator recipe, as well as Memberpress. We would appreciate any advice you can offer on how to resolve this issue, just hoping someone else uses Memberpress alongside Uncanny Automator, and might have attempted to do something similar.
[ad_2]
Are any of the Uncanny triggers working for you? Or is Uncanny not working at all on your install.
Is your WordPress cron setup and running correctly?
Does Uncanny have tasks created in its database table that have been queued but haven’t started (stuck in a non-started state)?
Maybe Memberpress changes the role back after Uncanny runs and does its changes. Could be a conflict between the two.
Or there’s no event being triggered when the account expires, so Uncanny is never informed.