Forum Replies Created
-
Posts
-
The “Read More” tag block of Gutenberg editor works fine with the following feature:
https://simple-membership-plugin.com/creating-teaser-content-membership-site/Please make sure you are not using the more link which is different than the standard more tag block. The more tag block needs to be used for teaser content feature.
Hi, Debit card add action refreshing the page is a PayPal account related issue. It’s not coming from this plugin. Anything you see within the PayPal’s payment window is controlled by PayPal. From my experience I think it has something to with the PayPal cookie getting stuck in the browser. Empty the browser cache and cookies. Then try again with a fresh browser. If that doesn’t solve it, the account owner needs to contact PayPal support since it is a PayPal account related issue.
If you have used one set of API keys to do testing and now want to change it to a different account, make sure to delete all trace of the previous account first.
#1) First, go to the “Payment Settings” -> “PayPal Webhooks” tab and delete the webhooks.
#2) Then go to the “PayPal API” tab and click the “Delete PayPal Token Cache” button to delete the token cache.
#3) Now, you can configure the new API keys again:
https://simple-membership-plugin.com/getting-paypal-api-credentials/#4) Make sure empty your browser cache and cookies before testing a transaction:
https://simple-membership-plugin.com/payment-testing-checklist-for-simple-membership/Our plugin doesn’t create any dashboard page that you referenced. The following documentation explains what pages our plugin creates:
https://simple-membership-plugin.com/recreating-required-pages-simple-membership-plugin/Any other pages can be deleted. If you got a freelancer to work on your site in the past, he/she may have created that page.
It will be good to delete your copy of the plugin and then download a fresh new copy from the official download page:
https://wordpress.org/plugins/simple-membership/You don’t lose any data in the process so it is safe to delete your copy of the plugin and then re-download.
The best way to get back on track is to download a fresh copy of our plugin to make sure you are using the official version. Then configure things using our documentation here:
https://simple-membership-plugin.com/simple-membership-documentation/Can you give reference to the payment button that you are trying to customize? Some elements of the buttons are from the payment gateway (such as PayPal) which the gateway doesn’t let you customize using your own CSS. So I need a visualization of which button you are referring to.
Hi, When a member updates the profile from the ‘edit profile’ page, our plugin doesn’t do any auto redirection to any page. The user should stay on the page with a message that says the profile has been updated. If you are seeing a redirection to the login page, it is coming from a configuration or customization that you may have applied.
Sometimes a user can apply customization in the theme’s functions.php file so when checking where the customization might be coming from, check/test the theme also:
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/Make sure to deactivate all the addons of the Simple Membership plugin also to make sure it is not coming from an addon’s configuration.
There appears to be a conflict with the server environment or a caching issue on your site. This may result in abnormal behavior from your perspective, but the root cause is external to the plugin.
Unfortunately, when external factors like conflicts cause issues, there is limited action we can take on our end. You might consider trying an alternative plugin as a potential solution.
https://simple-membership-plugin.com/understanding-the-impact-of-caching-on-membership-sites/
I recommend trying the following registration method to ensure the user account is created before the subscription payment. This approach can help reduce the likelihood of user errors that you are seeing:
The following two items are completely separate and unconnected:
Webhook Event:
The Webhook event type: BILLING.SUBSCRIPTION.CREATED. Event summary: Subscription created is a webhook notification from PayPal. Webhooks are asynchronous background notifications that can be received by the plugin at any time for any subscription. The plugin uses these webhooks to perform specific operations, such as handling recurring charges or processing subscription cancellations. However, user accounts are not supposed to be created based on this event, so it can be ignored in that context.OnApprove Ajax Request:
The OnApprove ajax request received for createSubscription is a synchronous event triggered when a user interacts with the subscription button and completes the checkout process in their browser. This event must occur during a new subscription checkout. If it is missing, it typically indicates that the checkout process wasn’t completed properly. Possible reasons could include insufficient funds on the user’s card or the user closing the checkout window before PayPal finalized the process.To ensure the subscription checkout process functions correctly on your site, you can perform your own testing:
Payment Testing Checklist for Simple Membership:
https://simple-membership-plugin.com/payment-testing-checklist-for-simple-membership/Keep in mind that occasional user errors may occur depending on the demographic of your site. These issues can often be identified by asking the user for details about what they did during the checkout process.
If you receive a webhook event and want to investigate further, you can copy the subscription ID (e.g., I-K90123456789) and search for it in the Members menu. If no user profile is associated with that subscription ID, it likely means that the user profile was deleted, or the user completed another subscription checkout that overwrote the previous one. You can deactivate such subscriptions directly from your PayPal account if necessary.
This looks to be related to caching. The following page will be helpful:
https://simple-membership-plugin.com/understanding-the-impact-of-caching-on-membership-sites/Hi,
Thank you. The fields marked in the “Optional Additional Parameter” section are optional but for your use case, those should be sent in the request:
So definitely send the username and password field in the API call.
For your use case, you should send all the following parameters:
– first_name
– last_name
– email
– user_name
– password
– membership_levelLet me know if that works better.
Please provide the script that you are using for the “create” user API call so I can review it:
Are you sending a username and password with the “create” request?
At the time, the password reset is clicked, does the corresponding WP user entry have a value in the “first name” field? Do a test yourself by recreating the issue so you can check if the WP user entry has a value in the first name field.
Hi, You can submit a pull request on our following github repository:
https://github.com/wp-insider/simple-membership
