If you are using aMember to manage subscriptions to a Wordpress site, please skim through and let me know if you have experienced this (and know of a solution!). Summary: On occasion, aMember successfully bills and creates a subscription account for a user in FMB, but does not create a corresponding user role in Wordpress. As a result, the user pays (and is even scheduled to be billed on a recurring basis), but cannot log in to view protected content. The only workaround is to manually "add a user" via Wordpress' admin panel, but this is far from ideal because that Wordpress user is now disconnected from the aMember-managed subscription cycle. So, even if the user cancels their subscription, or has problems with payment, the Wordpress account remains intact and active. With our sites, this is the current process: 1. User initiates signup process from aMember signup.php page 2. Via PayPal, recurring payments profile is created 3. Via PayPal, payment is processed / transaction is completed 4. PayPal tells aMember that steps 2 and 3 were successfully completed 5. aMember creates a user account and 'adds' the appropriate membership (monthly, quarterly, etc) to their account 6. aMember tells Wordpress to create a user 'role' in Wordpress. The role ('subscriber', 'editor', 'administrator') tells Wordpress what content to show that user. If the user does NOT have a role, then they see no content at all, even if their aMember account is active and payment is current. The error occurs at step 6. Challenges to debugging: There is NO record of this in the aMember error/debug log. We only find out about the problem if the user writes in to us. Additionally, this is impossible to reproduce (we don't understand the conditions under which the error occurs), making it very hard for the aMember support desk to help with troubleshooting. If you are using aMember and have any insights on this, please let me know. Your help is greatly appreciated! Sincerely, Susan
If you aren't using it- the amprotect plugin makes this whole process much easier. When the user logs in, the info is passed into wordpress and they get access set by amprotect that corresponds to the amember product. David