Forum Replies Created
-
AuthorPosts
-
admin
KeymasterThat looks fine to me. Everything executed as expected, and the recurring payment was processed correctly (membership level retained, account remained active).
One thing worth noting: the Stripe webhook events in your log are coming through with api version: 2018-05-21, which is quite old. This indicates the subscription button was likely created some time ago. You can upgrade the API version from the Developers menu in your Stripe account.
Since the button has been around for a while, it’s a good idea to review the current Stripe subscription button documentation and make sure all the steps are still valid for your setup:
https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/You can also follow the documentation to create a new Stripe subscription button and replace the old one on your site. Existing subscriptions will continue running without interruption. Only new subscribers will use the new button. This is a good way to ensure that going forward, all new subscriptions are using the latest API version and the most up-to-date setup.
admin
KeymasterEvery site is different, and the original poster’s situation may include background details that don’t apply to yours.
The feature being discussed in this thread is documented here:
https://simple-membership-plugin.com/giving-wordpress-admin-user-access-protected-content/There is no known bug with this feature. If it’s not working on your site, it’s most likely due to a conflict with another plugin/theme or a configuration issue.
If you’d like help troubleshooting, please describe your specific setup — what you’ve configured so far, what you expected to happen, and what’s actually happening. With that context, we can provide useful guidance.
admin
KeymasterThank you for sharing the log data. Unfortunately, this particular log doesn’t contain any recurring payment-related entries, so I’m unable to identify the issue from it. For us to troubleshoot effectively, the log file needs to cover the exact time when the issue occurs. I’d recommend resetting the debug log just before a recurring payment is due, so it captures only the relevant data from that event without unrelated noise.
A couple of clarifying questions to help us narrow this down:
1) When you mention “first invoice”, do you mean the very first checkout (when the user clicks the subscription button to create the subscription agreement), or the first recurring payment that occurs after the initial checkout?
2) From the timeframe covered by the current log, can you confirm whether the account was created correctly with the right membership level during the user’s registration/checkout attempt?
Also, since you’re using the WooCommerce addon as well, please go to that addon’s settings and make sure a value is set in the “Default Membership Level” field under the auto-create member account option. Missing this configuration can sometimes cause unexpected level assignments.
Once you’re able to share a fresh log covering a recurring payment event, we’ll take another look.
admin
KeymasterThe
swpm_account_status_for_subscription_start_date_updatefilter hook is only used if some custom code on your site explicitly hooks into it. It is not something that runs by default. So unless you (or a developer) have added custom code for it, your site is most likely not using this filter.You can check by doing a quick search for the filter name in the following places:
– Your active theme’s functions.php file.
– Any custom snippets added via a code snippets plugin (e.g., Code Snippets, WPCode).
– Any custom plugins you may have installed on the site.In the meantime, please go ahead and capture the debug log when the next recurring payment comes in for one of the affected members, then share the relevant portion of the log file with us. The log will show exactly what status value is being applied to the account when the recurring payment is processed, which will help us pinpoint the cause.
admin
KeymasterPlease enable the debug logging feature and capture the event so you can share the log file with us:
https://simple-membership-plugin.com/enable-debug-logging/This will let us see what account status value is being used when the payment is received.
Usually, this issue can be caused by one of the two things outlined below, so please check them as well:
1) “Default Account Status After Payment” setting
The value of this settings field may be set incorrectly. Our plugin sets it to “active” by default, so it’s a good idea to make sure it is set to active and then save the settings.
2) swpm_account_status_for_subscription_start_date_update filter hook
The plugin has this filter hook, which can be used to customize the account status after a recurring payment. If your site is using this filter to apply custom logic that returns an incorrect account status value, it can cause this issue.
admin
KeymasterThis one is a duplicate of this other post on WordPress.org forum so I will close this one here:
https://wordpress.org/support/topic/passkey-support-3/April 16, 2026 at 12:21 am in reply to: {expiry_date} – Member’s account expiry date – Time of Day #32028admin
KeymasterThe 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.
admin
KeymasterYou 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/admin
KeymasterPlease check the following active login limit feature. Is that something that will work for you?
https://simple-membership-plugin.com/configuring-active-login-limit/
admin
KeymasterOur 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.
admin
KeymasterThe
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?
admin
KeymasterWe have released an update that should solve this.
admin
KeymasterOur 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.
admin
KeymasterThank 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.
admin
KeymasterOne more question, are you using any other addon besides the bbPress Integration addon on this site?
-
AuthorPosts