Forum Replies Created
-
AuthorPosts
-
July 19, 2026 at 5:32 am in reply to: dissonance between membership login and wordpress login #32211
admin
KeymasterThat error is actually the clue here. It means the member account exists in SWPM but has no matching WP User record, so the forced WP login fails.
Please try what the message suggests: take the username value from the error (ariolodin@gmail.com) and search for it in the WP Users menu (Users → All Users). Do you see a WP User entry for that username? If not, that missing WP user is the cause, let us know and we’ll advise on restoring it.
admin
KeymasterTo add to the above, if your goal is just to visually style that message (colors, spacing, font size, etc.) rather than wrap it in your full page template, CSS will handle it.
You can inspect the message with your browser’s developer tools to find its wrapper class, then target that class in your theme’s Custom CSS (or a custom CSS plugin so the tweak survives updates). Our CSS tweaks page has examples of this approach:
https://simple-membership-plugin.com/miscellaneous-css-tweaks-simple-membership-plugin/For more precise control, use the free Simple Membership Custom Messages addon. It lets you replace the default notice with your own text and HTML markup — so you can wrap the message in a div with your own class or id, then target that with CSS to style it exactly how you like:
https://simple-membership-plugin.com/simple-membership-custom-messages-addon/admin
KeymasterThanks for the update, and thanks for reporting back that it was the firewall’s bad query string / XSS rules causing the 403. That’s a useful detail, because it’s very likely relevant to the PayPal issue too.
Your PayPal log shows exactly where the flow stops
A complete PayPal subscription checkout produces this sequence in the debug log:
1. swpm_pp_create_subscription ajax request received for createSubscription… ✔ you have this
2. PayPal Subscription ID: I-XXXXXXXX ✔ you have this
3. Webhook event type: BILLING.SUBSCRIPTION.CREATED ✔ you have this
4. Webhook event type: BILLING.SUBSCRIPTION.ACTIVATED ✔ you have this
5. OnApprove ajax request received for createSubscription… ✘ missingStep 5 is the one that matters. The onApprove step is a browser-side callback: once PayPal approves the subscription, the button’s JavaScript sends one final AJAX request from the customer’s browser back to your site’s admin-ajax.php. That request is what creates the payment/member record, sends the registration email, and returns the URL the customer should be redirected to.
Your log has no OnApprove entry at all, which matches your symptoms precisely: PayPal takes the payment (hence the PayPal emails and the ACTIVATED webhook), but the popup never hands control back to your page — so no registration email and no redirect. The webhooks alone do not create the member account; the onApprove request does.
Most likely cause
Since your firewall was already returning 403s on this site, the first thing to rule out is whether it’s still blocking that second AJAX request. The onApprove request POSTs a JSON payload (subscription details, PayPal URLs, etc.) to admin-ajax.php — exactly the kind of thing that “bad query string” and XSS filter rules tend to trip on. The first AJAX call (create subscription) is a much smaller payload, which would explain why that one gets through and this one doesn’t.
To confirm, please do this:– Open your Join page in a browser where you are not logged in as admin.
– Open Developer Tools → Network tab (tick “Preserve log”), and also open the Console tab.
– Complete a test payment.
– Look for a POST to admin-ajax.php with action=swpm_onapprove_process_subscription. Tell us whether it appears at all — and if it does, what status code and response body it returns.
– Note any red errors in the Console.That one check tells us whether the request is being blocked (firewall/WAF), is failing (server error), or is never sent, which would point to a JavaScript conflict instead.
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/admin
KeymasterThanks for the detailed log.
Your webhooks are working correctly
Looking at the log, the Stripe webhooks are being received, validated, and processed successfully (invoice.payment_succeeded). The line “Ignoring unused stripe webhook event. Webhook type: customer.subscription.created” is normal, expected behavior — our plugin only acts on the events it needs and ignores the rest with a 200 response. It never returns a 403 for any webhook. So the 403 you’re seeing is not coming from our plugin’s webhook handling.
The 403 is a server-level block
“The server sent back an error: 403 Forbidden” is a response from your server (or a security/firewall layer in front of it), not from our plugin. Since you’ve already ruled out the SWPM Full Page Protection addon and ModSecurity, the next step is to identify exactly which request is being blocked:
Open your browser’s Developer Tools → Network tab, then run the payment test again. Find the request returning 403 and note its URL. That tells us what’s being blocked (e.g. admin-ajax.php, a REST API endpoint, or the return/registration page).
Check for any other security layer: Cloudflare or another CDN/WAF, Wordfence or a similar security plugin, or host-level firewall rules beyond ModSecurity. Any of these can return a 403 on a specific URL or query string.Regarding XML-RPC
No, our plugin does not require XML-RPC to create registration pages or to process Stripe payments. You can leave it disabled; it’s unrelated to this issue.
Worth double-checking your setup
While you investigate the 403, it’s also worth confirming your Stripe button and webhooks were configured per our documentation:
Stripe subscription button: https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/
Creating the webhook: https://simple-membership-plugin.com/create-a-webhook-in-your-stripe-account/
Webhook signing secret (recommended): https://simple-membership-plugin.com/configuring-the-stripe-webhook-signing-secret/Once you’ve identified the blocked request from the Network tab, reset the log file, run another test, and share both the 403 request URL and the new log data. That will pinpoint the source.
admin
KeymasterGood to hear that you got it sorted out. Thank you for sharing your solution.
admin
KeymasterHi hapo, Since switching the export format didn’t fix it, the issue is most likely one of these:
Hidden BOM character in the file — Excel/Numbers on Mac often adds an invisible “byte order mark” at the very start of the file even when you export as plain CSV. This gets prepended to your first column header, so it’s technically not user_name anymore even though it looks correct. Fix: Open the CSV in a plain text editor (TextEdit in “Plain Text” mode, or VS Code/Sublime) instead of Excel/Numbers, and check the very first characters of the file.
Wrong delimiter, depending on your Mac’s regional settings, “Comma Separated” exports can still use a semicolon (;) instead of a comma. Open the file in a text editor and confirm the header row actually uses commas: user_name,email,password,…
Extra/renamed header cell — double-check there’s no trailing space, hidden character, or renamed cell (e.g., Username instead of user_name) in that first column header. The column name must match exactly, case-sensitive.Quickest way to isolate it: Download the plugin’s official sample CSV template from Simple Membership > Import Members, and only replace the data rows — don’t retype or rebuild the header row. If that imports fine, the header row in your original file is the problem.
admin
KeymasterSince you already have a dedicated thread for this question, I’ll continue the discussion and provide my response there:
https://simple-membership-plugin.com/forums/topic/how-to-enable-search-of-country/admin
KeymasterUpdate: We have added the option to search by country for the directory listing addon.
——
I’ll take another look at this over the next few days and get back to you with an update.Since this issue relates to a premium add-on, please submit a support request via the following page so I can follow up with you by email:
https://simple-membership-plugin.com/premium-addon-support/-
This reply was modified 4 months, 1 week ago by
admin.
admin
KeymasterLet me add some more context.
This thread is referring to the Member Directory Listing Addon:
https://simple-membership-plugin.com/simple-membership-member-directory-listing-addon/The search feature in the Directory Listing Addon can search the following fields:
Username
First Name
Last Name
Email
Company Name
Custom Fields (text-based fields work best)Is your question related to the Directory Listing Addon?
admin
KeymasterHi, No you don’t need form builder addon for that.
Translation strings missing mean it hasn’t been translated in that specific language yet. The following translation documentation should be helpful:
https://simple-membership-plugin.com/translate-simple-membership-plugin/admin
KeymasterWe don’t have a built-in feature for post allowance.
May 20, 2026 at 2:22 am in reply to: Security check: captcha validation failed. Simple Membership Plugin #32116admin
KeymasterThank you for submitting the ticket. We have responded to your inquiry.
May 16, 2026 at 3:32 am in reply to: Confirm if Stripe Webhook Signing Secret process I followed is correct #32112admin
KeymasterThank you for reporting this. Looks like Stripe has updated their UI. I have just updated the documentation to so it matches closely with the current Stripe UI:
Here is the documentation for creating a Stripe webhook:
https://simple-membership-plugin.com/create-a-webhook-in-your-stripe-account/Here is the documentation for configuring webhook signing secret:
https://simple-membership-plugin.com/configuring-the-stripe-webhook-signing-secret/Let me know if this is helpful.
admin
Keymaster@Naovaczid, It will be an issue with the site’s setup. Do you have debug log data similar to what the previous poster shared?
admin
KeymasterIf you only created this button a couple of months ago, there’s no need to create a new one. Just update the Stripe webhook API version to the latest from the Developers menu in your Stripe account. After that, reset the debug log file and monitor new transactions for a few days to see if any issues come up.
-
This reply was modified 4 months, 1 week ago by
-
AuthorPosts