Forum Replies Created
-
Posts
-
this looks like a genuine tribe_events/The Events Calendar CPT protection compatibility edge case. The fact that anonymous users receive the SWPM protection message while an authorized logged-in member receives a 404 is actually a strong indication that the failure is occurring in the authenticated CPT request path, rather than in the membership-level comparison itself.
The official SWPM documentation acknowledges that CPT plugins which use non-standard hooks can require the enhanced CPT protection mechanism, and SWPM’s own support history specifically identifies The Events Calendar as having non-standard calendar pages that don’t behave like ordinary WordPress Pages/Posts.
I would not call this a normal or expected result for a correctly authorized member. I would treat it as something that needs either a reproducible compatibility fix or a different protection mechanism.
The developers will be informed.
So, after you made that selection did that resolve the issue? If you still need help with the Form Builder, please complete a Premium Addon Support ticket and a developer will contact you.
https://simple-membership-plugin.com/premium-addon-support/delete ALL users added BEFORE sync was turned on and re-add them.
When adding new users, the email addresses must not currently exist on the WordPress side. In other words, any new members added must have email addresses not already registered in SWPM and WordPress.
The behavior you’re seeing usually indicates that the Email Activation workflow is being used instead of the Manual Admin Approval workflow. These two workflows are mutually exclusive in the Simple Membership plugin—they cannot be used together.
Membership Level Settings
Go to WP Membership → Membership Levels.
Edit the membership level that new users are registering into.
Look for the Enable new user activation via email (Email Activation) option.
If your goal is manual admin approval, make sure this option is disabled. Email activation is configured on a per-membership-level basis.Default Account Status
Ensure the Default Account Status is set to Pending.
This can be configured globally or overridden per membership level. The per-level setting takes precedence if configured.Regarding the missing emails
Please turn on the debug logs. If the logs show the email being successfully sent, the problem is on the receiving end/Did you do what we have suggested?
1. Turn on WP and SWPM user account syncing. This will ensure any new SWPM registered users are properly synced.
2. Delete a user that was created before you turned on account syncing and manually recreate it using the procedure @admin described. Note: the affected user(s) will need to reset their passwords.
The message you’re seeing is generated directly by the content protection system rather than through a WordPress page, which is why it doesn’t inherit your site’s header, footer, or page template.
The add-on that lets you customize the message only changes the content of the notice—it doesn’t wrap it in your theme’s layout.
If you want the login prompt to appear within your site’s normal page template (including the header and footer), the Partial Pages add-on is the appropriate solution, as it displays protected content and login prompts within your site’s themed pages instead of as a standalone message.
What you describe usually points to the WordPress user session and the Simple Membership (SWPM) session not being synchronized.
Normally:
Logging in via the Simple Membership login form should also log the user into WordPress.
Logging in via the WordPress login page should also log the user into Simple Membership (if synchronization is enabled and the accounts are linked).Go to Simple Membership → Settings → Advanced Settings.
Make sure Force WP User Synchronization is enabled.This setting ensures that:
Logging into WordPress also logs the user into Simple Membership.
Logging out of one logs the user out of the other.
The login cookie duration is synchronized as well.Because you’re also using the SWPM Full Page Protection addon, temporarily disable that addon and repeat the payment test. This will help determine whether the 403 is being triggered by page protection or by something external.
If your host provides page caching or server-level security, ask whether any rules are returning a 403 on the registration URL after Stripe redirects back to your site.
The developer has been notified.
It depends on whether or not you are just collecting an additional fee for a specific number of additional family members or if you expect these additional family members to also have access to the site.
SWPM does not support the creation and maintenance of associate login accounts, because each member account must have its own unique email address, and the linking of one membership account to another is not supported.
However, if all you want to do is charge more for extra family members as in the case of a social organization, without creating additional SWPM accounts, you could create extra payment buttons corresponding to the number of memberships being purchased.
This is usually caused by the newer Stripe Checkout API not receiving the description parameter in the same way older Stripe APIs did. The payment may still work correctly, but the description field might not appear in the Stripe dashboard or payment details as expected.
A few things to check first:
Which exact button type are you using?
“Stripe Buy Now”
“Stripe Subscription”
“Stripe SCA Buy Now”
“Stripe SCA Subscription”
Or the newer “Stripe New” button
Where are you expecting the description to appear?
Stripe Dashboard payment entry
Checkout page
Receipt email
Metadata field
Bank/card statement descriptor
Can you share:
A screenshot of the payment button configuration
A screenshot from Stripe showing the missing description
The plugin version you are usingAlso, please ensure the SWPM debug logs are turned on.
Because you have the premium Form Builder addon, please complete a Premium Addon Support ticker and a developer will contact you:
https://simple-membership-plugin.com/premium-addon-support/@jennylens — this user posted the same question twice. The decision was to only answer the first posting. With that said, please state your specific question, as it applies to you.
What you’re describing is not normal behavior for the Simple Membership plugin. After a successful recurring payment, the member’s account should remain Active and keep the same membership level.
Please enable your debug logs.
https://simple-membership-plugin.com/enable-debug-logging/Also read this, and see if any of the issues apply to you.
https://simple-membership-plugin.com/understanding-the-impact-of-caching-on-membership-sites/Also, Can you tell us:
* Which payment gateway are you using? (Stripe, PayPal, other)
* Are you using a subscription button or manual recurring billing?
* Does this happen to all members or only some?
