[admin]

@lindak, Apologies for the earlier confusion. To clarify, the Simple Membership plugin does create a corresponding WordPress user account for each member. This design decision was made to ensure compatibility with other major plugins like bbPress, WooCommerce, and others, which rely on the standard WordPress user system.

At this time, there isn’t an option within the plugin to disable WordPress user creation. Changing this behavior would require custom development and direct code modifications. Unfortunately, this is not something we can support officially, as it introduces complexity and potential conflicts that go beyond our standard plugin support scope.

We understand this may not suit every use case, and we’re truly sorry we can’t offer a built-in setting for this scenario right now.

[admin]

At this time, our standard subscription integration does not support a donation-based model, and this feature is not currently advertised or included. However, I’ve noted your request and added it to our internal feature wishlist for future consideration.

[admin]

Just as a test, could you create a new Stripe Buy Now button using the instructions in our documentation below and see if you get the same result?
https://simple-membership-plugin.com/sca-compliant-stripe-buy-now-button/

This will help confirm whether the issue is related to using old/legacy buttons or an outdated configuration. Running this test will allow us to better isolate the cause.

[admin]

Have you tried version 4.6.7? When you test, please make sure to clear all caches on your site and also your browser cache. This cache clearing part will be important for this test.

[admin]

Good to hear that.

[admin]

Unless I can check the actual URL of the page containing the button, I can’t confirm 100% whether there’s a JavaScript error. Based on what you’ve described, it does sound like there may be an error.

You can safely downgrade the plugin if you wish—doing so won’t cause any data loss:
https://downloads.wordpress.org/plugin/simple-membership.4.6.5.zip

That said, we generally don’t recommend downgrading because the JavaScript issue isn’t originating from our plugin. It’s better to resolve the root cause of the error so that you can continue using the latest versions.

As an alternative (if you can’t address the theme’s JavaScript errors right now), you could use the following Stripe Payments plugin for membership payments:
https://wordpress.org/plugins/stripe-payments/

We also have integration documentation here:
https://simple-membership-plugin.com/stripe-payments-plugin-integration-for-membership-payment/

[admin]

Hi, I’m not familiar with the Nextend Social Login plugin, so I can’t confirm how it integrates with Simple Membership at the moment.

Previously, we tested the Super Socializer plugin and it worked with our integration. However, over time external plugins often change their code, which can break the integration pathway. Because of this recurring issue, we’ve decided to stop supporting third-party social login plugins — they tend to break too often and create ongoing maintenance challenges.

Instead, we’re planning to build our own dedicated social login feature for Simple Membership. This way, we’ll have full control over the login flow and can provide a solution that’s reliable and works as expected. Our goal is to release this in the coming weeks.

In the meantime, we unfortunately don’t have a working solution to offer to you. For your current project, you may want to try another plugin that better fits your needs until our built-in option becomes available.

[admin]

Also, please share the URL where the subscription button is so we can inspect it using our browser and check if there are any JavaScript errors on that page:
https://simple-membership-plugin.com/javascript-errors-on-your-site/

[admin]

Giving an update to this. We have made some changes to the plugin that should solve this issue.

We intend to release this version in the next few days or so. However, in the meantime, I am going to give you an updated copy of the plugin so you can use it and see if this works better on your site.

You can download an updated copy of the plugin from our site using the following link. Let me know if this makes any difference:
https://simple-membership-plugin.com/wp-content/uploads/simple-membership.zip

If you want to try this update, first delete the currently active copy of the plugin then upload and activate the above mentioned one. You won’t lose any data (members, payments, buttons, settings etc.) in the process so it is safe to do this.

[admin]

Thanks for the detailed post — this kind of clarity helps us investigate effectively.

Just a general reminder for others following along or experiencing similar issues:

Stripe frequently updates its platform, including how webhook events are structured and what data is included. A webhook payload from an earlier version may look different or behave differently than one in a newer version. These kinds of changes can impact how our plugin interacts with Stripe over time.

Additionally, how your membership level is configured matters a lot. For example, the “No Expiry or Until Cancelled” option (which was the originally supported method for subscriptions in our plugin) works reliably with Stripe’s subscription deletion webhook — when the subscription is cancelled, the membership is cancelled too. However, the “Access for X days/months” setup was added later, and some edge cases may still need refinement. It’s likely that this newer scenario requires more checks or adjustments.

So when you’re posting about issues, please include:

• Clear steps to reproduce the behavior
• How your membership level is configured
• Whether you’re using live or test mode
• Any relevant debug log entries or screenshots

We’re a small team maintaining a free plugin, so we rely on detailed and constructive reports to fix things quickly and reliably.

Your post includes clear steps — thank you for that. I’ll replicate your setup on a test site over the next few days using the latest Stripe API version and see if I can reproduce it. If I do, I’ll be sure to follow up here with an update.

[admin]

No, we don’t have a built-in option for Braintree subscription payments.
As a workaround, you could use WooCommerce along with its Braintree subscription checkout feature.

The Simple Membership plugin integrates with WooCommerce, so any payment processed through WooCommerce — including via Braintree — can be used for membership purchases.
https://simple-membership-plugin.com/woocommerce-simple-membership-plugin-integration/

[admin]

You can disable these two emails by leaving their email body fields empty.

Alternatively, you can use the following filter hooks to programmatically override their email body content and effectively disable the emails:

Prompt to Complete Registration
swpm_email_complete_registration_body

Registration Completed Successfully
swpm_email_registration_complete_body

[admin]

In our main plugin there is no concept or feature of uploading docs/files using any form. Can you share a screenshot maybe so we have a visual reference of the form you are referring to?

Are you using the Form Builder addon maybe? If this is a question about the form builder addon, please use the following paid addon support page:
https://simple-membership-plugin.com/premium-addon-support/

[admin]

The following are two recommended solutions that can help address this issue:

#1) Use the “Thank You” page for registration
This method allows users to register immediately after making a payment, directly from the thank you page—removing the dependency on the email being received:
https://simple-membership-plugin.com/paid-registration-from-the-thank-you-page/

#2) Allow account creation before payment
If you’re concerned about email delivery issues, this method lets users create an account before completing payment, ensuring a smoother and more reliable flow:
https://simple-membership-plugin.com/allowing-members-create-account-prior-completing-membership-payment/

If you require a different custom registration flow, you could explore custom code modifications. However, these may encounter limitations or compatibility issues with the plugin’s current architecture. In such cases, you might consider exploring alternative plugins that better suit your needs.

[admin]

The plugin doesn’t have a built-in option to automatically limit the maximum number of members. If you want to enforce a limit, you would need to manually disable user registration or sign-up once that limit is reached.

Another option is to use the plugin’s invitation code feature, which lets users sign up only if they have a valid code. For example, if you share the code with just 10 people, only those 10 will be able to register:
https://simple-membership-plugin.com/member-registration-via-an-invitation-code-or-password/

[Author]

Posts