Forum Replies Created
-
Posts
-
Check the following documentation page since you are using a Caching solution:
https://simple-membership-plugin.com/understanding-the-impact-of-caching-on-membership-sites/This issue can compound with a plugin or theme related conflict. Do the following test please:
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/If you want to protect downloads or media files, the closest option that we have is the following one. Check the following documentation to see if this can be helpful for you:
https://simple-membership-plugin.com/protecting-media-files-in-wordpress-static-file-security-and-access-control/It looks like you ran the test in Sandbox mode, which unfortunately won’t work for this particular scenario. In sandbox, PayPal does not provide the payer’s email address, so you’ll need to perform a live transaction to properly test the guest checkout option.
The plugin now makes a server-side request to retrieve the email from the PayPal subscription details. If the email is still not available after a live transaction, it likely means PayPal is not providing it due to privacy restrictions in that specific country.
To handle this, you can choose one of the following options:
#1) Require account creation before payment:
This avoids the issue altogether since the user creates an account first:
https://simple-membership-plugin.com/allowing-members-create-account-prior-completing-membership-payment/#2) Use the ‘Thank You’ page registration method
This method lets users complete their registration without relying on an email:
https://simple-membership-plugin.com/paid-registration-from-the-thank-you-page/#3) Use Stripe instead of PayPal
Stripe supports guest checkout and does not have this email limitation:
https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/Enable the debug logging option (if it was enabled already, reset it so there is a clean capture).
https://simple-membership-plugin.com/enable-debug-logging/Read the following page fully before doing payment testing:
https://simple-membership-plugin.com/payment-testing-checklist-for-simple-membership/Do a test transaction and share the log file’s content from that transaction.
We have released a new version of the plugin that should solve this. Please upgrade to the new version when you can.
It’s better to use the following new option. It works for both the Stripe subscriptions and the new PayPal subscriptions:
https://simple-membership-plugin.com/show-active-subscriptions-and-providing-a-cancellation-option/
Once you’ve set it up, run a test to ensure it’s working correctly on your site. If the users you’re referring to subscribed a long time ago, their subscriptions may not be compatible with this new cancel option. In such cases, you’ll need to cancel those subscriptions manually from your Stripe account.
The following documentation should be helpful:
https://simple-membership-plugin.com/giving-wordpress-admin-user-access-protected-content/The email text you’re seeing is likely coming from the settings configured under “Email Related Settings.” Please check the following areas to locate and review the source of that content:
#1) Go to the “Email Settings” menu of the main plugin.
#2) Review all the email-related fields to see if the text appears there.
#3) If you’re using the Form Builder addon, edit the associated registration form and check if a custom email message is configured for it.
#4) To rule out interference from other plugins, addons, or custom code, please follow this conflict test guide:
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/This behavior is not typical for our plugin or its addons, which suggests an external factor—such as a plugin, theme, or server configuration—is causing a conflict.
To help identify the source of the issue, please follow this conflict test guide:
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/If you’d prefer our help via paid support, you can open a ticket here:
https://simple-membership-plugin.com/paid-support-simple-membership-plugin/However, please understand that we cannot resolve issues caused by external conflicts, as we have no control over your server environment. To investigate further, we would require a staging site where only our plugin is active. That’s why it’s best if you first complete the plugin conflict test mentioned above. This step often reveals the root cause and may save you time.
The error here is for the ‘username’ field (Not the email address). When you see the following in the error message, it means you are trying to use an username already in the system:
username already existsThe username must also be unique. You can use the email address as the username to ensure uniqueness.
Before running a test, follow these steps to avoid conflicts or confusion:
1) Check the WP Users and Members menus to confirm that the username you plan to use is not already taken.
2) Do the same for the email address — make sure it’s not already in use in either the Users or Members menus.Check the WP Users menu also. It is very likely that you were using another membership plugin in the past and the emails are assigned to another WP User entry.
You can import your existing WP user entries into Simple Membership using the following option:
https://simple-membership-plugin.com/import-existing-wordpress-users-simple-membership-plugin/If the standard protection is not working for your setup, you can try our following free addon to see if that work for the protection:
https://simple-membership-plugin.com/full-page-protection-addon-simple-membership/Sure. If you need any new hooks, just let me know and we’ll add them to the plugin.
On a related note, we’ve recently added a feature for subscription buttons that lets you display a custom message or warning to members who already have an active subscription. There’s also an option to hide the subscription button entirely in that case. This can be a useful way to prevent duplicate subscription payments from existing members.
