Forum Replies Created
-
Posts
-
The time of the day does not play a factor.
The plugin uses WordPress’s built-in cron system for account expiry checks.
https://developer.wordpress.org/plugins/cron/It schedules a daily cron job that runs once per day, but the exact time it fires depends on site traffic and other factors — so you can’t predict the precise time it will execute on any given day.
You also have the option to override the default login template and create a fully customized version. Please note that this involves modifying PHP files, so it is considered an advanced option and may not be suitable for all users.
You can find a step-by-step guide here:
https://simple-membership-plugin.com/how-to-override-simple-membership-plugin-templates-in-your-theme/If you’re only looking to adjust the appearance (for example, styling or layout), some CSS tweaks may be sufficient. The following page includes helpful examples:
https://simple-membership-plugin.com/miscellaneous-css-tweaks-simple-membership-plugin/Please check the following active login limit feature. Is that something that will work for you?
https://simple-membership-plugin.com/configuring-active-login-limit/
Our plugin uses WordPress’s
wp_redirect()function to handle post-login redirects. Unfortunately, this function cannot preserve URL anchors (fragments). This is a browser limitation — the #fragment portion of a URL is client-side only and is stripped by the browser before the HTTP request is sent to the server, so the server never receives it.For your use case, we recommend bypassing the standard After Login Redirection add-on and using the following action hook to implement your own custom redirect logic:
https://simple-membership-plugin.com/simple-membership-action-hook-reference/#swpmafterlogin
This gives you full control over post-login redirects, including the ability to redirect users to a specific anchor position on a page.
The
invoice.payment_succeededwebhook is needed for sure. That’s the one our plugin uses. So if that hook is not getting triggered by Stripe, it needs an investigation.Check the
Developers → API versionssection to see which version of the API is being used by your Stripe account.Are you using the latest version of the Simple Membership plugin?
Our Form Builder add-on includes options to customize the registration form. You can hide the username field and configure the system to use the email address as the username instead.
Thank you. Looks like you are using the Form Builder addon with bbPress. I think the Form Builder needs a small update for this. I will investigate this more and get back to you with an update.
One more question, are you using any other addon besides the bbPress Integration addon on this site?
okay so the WordPress user role is working as intended. The issue is that the user’s “Forum Role” (for bbPress) gets updated/changed which causes the issue right?
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/
