Forum Replies Created
-
Posts
-
The WordPress role that SWPM assigns is configured at the membership level. You can edit the relevant membership level and check the “Default WordPress Role” field to see which role is set for that level. When a member belongs to that membership level and their profile is saved, the specified role is applied to that member.
To clarify, are you saying that you’ve set a WordPress role in the membership level configuration, but it is not being applied when the member’s profile is saved?
I just want to understand whether the plugin isn’t behaving as expected, or if something else might be interfering with the process.
For manual approval (where an admin must review and explicitly approve each new member before they can log in), the key setting is the account status, which must be set to “Pending”.
#1) The global “Default Account Status” option (in the plugin’s main Settings) can be set to “Pending” to apply this site-wide.
#2) Alternatively (and often more flexibly), you can override this per membership level: Edit the specific membership level → set its “Default Account Status” to “Pending”.
This is useful if you want manual approval only for certain levels (e.g., paid or restricted ones) while keeping others automatic.As we continue to add new features to the plugin, some workflows evolve over time, which can occasionally change how certain options behave.
If you intend to use the manual approval feature, it’s important to follow the setup exactly as outlined in the documentation below. If the configuration differs, the expected behavior will not occur:
https://simple-membership-plugin.com/manually-approve-members-membership-site/Users sometimes confuse manual activation with manual approval. These two options are mutually exclusive and cannot be used together.
Please review the following documentation carefully to make sure you’re not mixing these two features or trying to enable both at the same time:
https://simple-membership-plugin.com/email-activation-for-members/
https://simple-membership-plugin.com/manually-approve-members-membership-site/
Just adding the reply from @dugganvideo in this thread in case it helps someone else who encounters a similar issue.
Found my problem. Member login was taking them to the staging version of my website. I have gotten it corrected. Thank you for responding.
Couple of issues:
#1) We don’t officially support any forminator integration. So I am not sure which documentation was followed to create the integration that you are using. In any case, this is not a supported model for our plugin’s registration process. The only supported registration process is explained on our following documentation:
https://simple-membership-plugin.com/membership-registration-process-overview/#2) The second issue is the payment button.
How was this payment button created? Was it created using our following documentation?
https://simple-membership-plugin.com/create-paypal-buy-now-buttons-paypal-api/or the following for PayPal Subscription type buttons:
https://simple-membership-plugin.com/create-paypal-subscription-buttons-paypal-api/Is your payment button (for the paid membership) assigned the correct membership level?
Do a test yourself by going through your registration process to ensure that the process works as per your expectation:
https://simple-membership-plugin.com/membership-registration-process-overview/Enable the debug logging feature then do a paid membership test:
https://simple-membership-plugin.com/enable-debug-logging/Can you go to the special registration link after payment to register for a new account for the membership level that you paid for? Share the debug log content from your test so we can check it.
According to the debug log file you shared, the plugin is successfully executing the email sending code. If you didn’t receive those emails in your inbox, it indicates that your server is either failing to send them out or the emails are being blocked somewhere along the way (e.g., by spam filters, your hosting provider’s policies, or the recipient’s email service). Your hosting provider can help trace the specific email delivery attempt and identify exactly where it’s getting blocked—ask them to check their mail logs for the sender address, timestamp, and recipient from your debug output.
For a deeper dive into this common issue (including how email flow works post-plugin execution and additional troubleshooting tips):
https://simple-membership-plugin.com/forums/topic/email-sending-issue-on-your-site/We don’t have an out of the box feature for this.
You can use the action hooks of our plugin to create a customization yourself:
https://simple-membership-plugin.com/simple-membership-action-hook-reference/
If you want us to create a customization for you, we can do a custom job to create a small custom addon for you that will allow you to configure sending of an additional notification email when member’s edit their account profile from the “Edit Profile” page. Reach out to us using the contact form if interested.
The expiry date is not a fixed data point but is dynamically calculated based on various account parameters.
For more details on the logic, this documentation may be helpful:
https://simple-membership-plugin.com/manually-activating-expired-members-account/We will look into it and see if we can create an email merge tag for it in the next release.
@bobgarrett, The 14-day “remember me” period is fixed from the time of the initial login and does not automatically extend based on ongoing usage of the website. This means that even if the user accesses the site daily, they will need to log in again once the original 14-day period expires.
There is no auto-refresh/extension of the login cookie just for logging in daily. This is a standard behavior of login cookies across all websites.
You can customize the duration and make your “remember me” login cookie stay valid much longer than 14 days (for example, you can use a value of 30 days or even longer).
What you are describing sounds like a custom setup that relies on a third-party plugin (which we are not familiar with) to automate the process. It’s quite possible that this external system or plugin is not setting all the necessary parameters for the post correctly.
Here’s how you can test this:
1) First, follow the steps outlined below to ensure that any external variables that could affect functionality are removed:
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/2) Next, manually edit the post in question and apply the protection settings correctly. Then save the post.
3) Check if the post protection now works correctly. If it does, that confirms the plugin itself is functioning as intended.
In that case, the issue lies outside of our plugin. Integration with third-party systems is beyond the scope of this free support forum, so we won’t be able to troubleshoot problems caused by external variables.
