Forum Replies Created
-
AuthorPosts
-
admin
KeymasterHi David, thanks for the question. The plugin’s PayPal (PPCP) buttons currently show PayPal, Venmo (where available) and card payments, but they don’t include Apple Pay or Google Pay. PayPal handles those through a separate integration that needs Apple domain verification and extra setup in your PayPal account. PayPal also only supports them for one-time payments, not subscriptions. We will look into this as a new feature request.
admin
KeymasterYes, the latest version of our plugin is compatible with 2026-10-28.endive. We tested a full Stripe subscription checkout with the account set to Endive, and everything (payment, webhooks, member account creation) worked fine.
Our plugin sets its own API version on the requests it sends to Stripe, so changing your account default won’t affect those calls. The breaking changes in Endive are in areas our plugin doesn’t use.
You can go ahead and upgrade. We recommend doing one test transaction after switching, just to be safe.
November 4, 2026 at 4:57 am in reply to: SWPM Comment Protection Not Working with the Twenty Twenty-Five Block Theme #32458admin
KeymasterHi, Thank you for the detailed report. It made this easy to track down.
You’re right. Our comment protection wasn’t applying to the Comment Content block used by block themes such as Twenty Twenty-Five. Classic themes weren’t affected, which is why it worked with your previous theme. Comment posting uses a separate check, so that part kept working as expected.
We have fixed this in the plugin, and the fix will be in the next release. After you update, the comment protection will work with your block theme the same way it did before, with no changes needed on your end.
If you’d like the protection back before the update is out, you can add the following snippet to your site using a plugin like Code Snippets (or your child theme’s functions.php file):
add_filter( 'comment_text', function( $content, $comment = null ) { if ( is_admin() || ! is_a( $comment, 'WP_Comment' ) || ! class_exists( 'SwpmAccessControl' ) ) { return $content; } return SwpmAccessControl::get_instance()->filter_comment( $comment, $content ); }, 20, 2 );You can remove the snippet after you update the plugin.
November 4, 2026 at 4:53 am in reply to: SWPM Comment Protection Not Working with the Twenty Twenty-Five Block Theme #32457admin
KeymasterEdited
November 3, 2026 at 6:11 am in reply to: Login loop caused by POST grace period on expired auth cookie #32454admin
KeymasterWe have released Simple Membership version 4.8.7, which includes the fix.
admin
KeymasterHi, Thank you for the detailed report. This was a bug in the Zapier integration add-on itself, not in Simple Membership 4.8.6.
We have released version 1.2 of the add-on with this fixed. You can download it from the same page:
https://simple-membership-plugin.com/zapier-webhook-integration-for-simple-membership-plugin/Version 1.2 also makes setup easier: the Zapier webhook URL is now set in Simple Membership → Settings → Addon Settings instead of in the PHP file, so it’s kept when you update the add-on in the future.
To update:
1) Deactivate and delete the old version (1.0) from the Plugins menu.
2) Upload and activate version 1.2.
3) Go to Simple Membership → Settings → Addon Settings (or click the Settings link under the add-on in the Plugins menu), paste your Zapier Catch Hook URL into the Zapier Webhook URL field, and save.After that, registrations will complete normally and new members will be sent to Zapier again. If anything doesn’t work as expected, enable the debug log in Simple Membership, register a test member, and check the log. It now says clearly whether the data was sent or what went wrong.
October 29, 2026 at 5:04 am in reply to: Legacy PayPal Hosted Button subscriptions and missing item_number in SWPM 4.8.6 #32436admin
KeymasterHi, Your reading of the changelog is correct, and the log entry you are seeing is expected for subscriptions that were started from buttons created directly in your PayPal account.
1) Was this intentional in 4.7.7?
Yes. Version 4.7.7 tightened the PayPal Standard IPN validation as a security fix (so forged IPN data can’t be used to create or extend memberships), and the old code for PayPal hosted buttons was removed at the same time. Every IPN must now point back to a PayPal button that was created inside the Simple Membership plugin:
– The
item_numbermust be the ID of a payment button created in the plugin.
– Thesubsc_refvalue must match the membership level configured on that button.
– Thereceiver_emailmust match the PayPal email address configured on that button.Your legacy subscriptions don’t send an
item_number, so the plugin has no button to verify them against and rejects the IPN. That is the “Empty item number received” line in your log.2) Is there a supported way to record these renewals in 4.8.6?
Not automatically. PayPal keeps sending the same data for an existing subscription profile, so there is no setting that will make these renewal IPNs pass validation.
The payments are still collected in your PayPal account. Until those subscriptions are moved over, you can apply each renewal to the member’s profile manually: edit the member, set the access start date to the renewal payment date, and make sure the account status is active. This page explains how the expiry is calculated from the access start date:
https://simple-membership-plugin.com/manually-activating-expired-members-account/
3) Migrating without cancelling everything at once
You can move members over gradually, one renewal at a time:
1. Create a PayPal subscription button inside the plugin for each membership level (same PayPal account, same pricing and billing cycle):
https://simple-membership-plugin.com/simple-membership-documentation/#membership-payment-options2. Leave the existing PayPal subscriptions running and reconcile their renewals manually (as explained in point 2).
3. As each member approaches their next renewal date, ask them to log in to your site and subscribe using the new button, then cancel the old subscription from their PayPal account (or you can cancel it from your PayPal account once the new one has started). Because the member is logged in when they pay, the new subscription is applied to their existing member account, so their profile and history are kept.
4) Are cancellation and payment failure notifications affected too?
Yes. The same validation runs on every IPN before the transaction type is checked, so
subscr_cancel,subscr_eot,subscr_failedand refund notifications from these legacy subscriptions are also rejected. Until a member is migrated, their account won’t be updated automatically when they cancel or a payment fails. Please keep an eye on these events in your PayPal account and update the member’s account status manually when needed.Let me know if you have any questions.
admin
KeymasterHi, Glad to hear everything else is working well.
The easiest option is the mini login shortcode. It shows a “Login Here” link to guests and a “Logout” link (along with the username and a profile link) to logged-in members:
[swpm_mini_login]The following page explains how to use it in a sidebar, header or footer:
https://simple-membership-plugin.com/adding-mini-login-widget-sidebar-header-footer/If you’d rather code it yourself (for example, as a menu item), you can use the following function to check the session status. It returns true when a member is logged in:
SwpmMemberUtils::is_member_logged_in()Here is an example snippet that adds a Login/Logout item to the end of a menu. Add it to your child theme’s functions.php file (or use a code snippets plugin), and change “primary” to your menu’s theme location:
add_filter( 'wp_nav_menu_items', 'my_swpm_login_logout_menu_item', 10, 2 ); function my_swpm_login_logout_menu_item( $items, $args ) { if ( $args->theme_location !== 'primary' || ! class_exists( 'SwpmMemberUtils' ) ) { return $items; } if ( SwpmMemberUtils::is_member_logged_in() ) { $url = home_url( '/?swpm-logout=true' ); $label = 'Logout'; } else { $url = SwpmSettings::get_instance()->get_value( 'login-page-url' ); $label = 'Login'; } $items .= '<li class="menu-item"><a href="' . esc_url( $url ) . '">' . esc_html( $label ) . '</a></li>'; return $items; }Note: If you use any page caching on your site, make sure it is bypassed for logged-in members. Otherwise visitors may see the wrong link. The following page has more details:
https://simple-membership-plugin.com/understanding-the-impact-of-caching-on-membership-sites/Let me know if you have any questions.
admin
KeymasterHi, There isn’t an option to auto-assign a membership level based on the email domain. The whitelisting feature works site-wide: it controls who can register at all, not which level they get. If you whitelisted the organization’s domain, it would also block everyone else from registering on your site.
Here’s a setup that handles organizational access well:
1. Create a new membership level for the organization (for example, “Acme Org Members”) and give it access to the same content as your paid level.
2. Create a registration form for that specific level using the registration form shortcode generator:
https://simple-membership-plugin.com/simple-membership-registration-form-shortcode-generator/3. Protect that registration form with an invitation code, then give the code to the organization so only their people can sign up:
https://simple-membership-plugin.com/member-registration-via-an-invitation-code-or-password/4. Collect the bulk fee from the organization separately, using a one-time payment button or invoice.
This keeps your regular paid registration working as it does now. It also lets you control the organization’s access separately, for example by setting an expiry on that level to match their billing period.
If your entire site is meant only for that organization, the domain whitelisting feature can be used instead:
https://simple-membership-plugin.com/blacklisting-whitelisting-feature/admin
KeymasterHi, yes, you can do either of those.
Option 1: Redirect visitors straight to the Join Us page
The free Full Page Protection addon has an auto redirect feature for protected pages. Instead of showing the protection message, it sends the visitor to the URL you choose (your Join Us page, login page, or any other page).
– Install and activate the Full Page Protection addon: https://simple-membership-plugin.com/full-page-protection-addon-simple-membership/
– Go to the addon’s settings menu and tell it to handle protection for your posts and/or pages.
– Scroll to the “Redirection Settings” section and enable the auto redirect option.
– Enter your Join Us page URL as the redirect destination and save.Full details are in the “Enabling Auto Redirect on Protected Pages” section of the documentation linked above.
Option 2: Customize the protection message
If you’d rather keep visitors on the page and show your own message, use the free Custom Messages addon:
https://simple-membership-plugin.com/simple-membership-custom-messages-addon/
After activating it, go to the “Custom Message” menu and enter your text in the “Restricted Post (No Logged In)” field. HTML is supported, so you can add your own links, buttons, or a short sales pitch with a link to your Join Us page. You can also add a CSS class to the message and style it via Appearance → Customize → Additional CSS.
admin
KeymasterYes, you can do this with an action hook. The plugin fires a hook right after a member account is created, and it passes the submitted form data to your function.
Since you create accounts from the admin dashboard, use this one:
swpm_admin_end_registration_complete_user_dataFor members who register themselves using the front-end registration form, the equivalent hook is:
swpm_front_end_registration_complete_user_dataBoth pass an array of the member’s data (user_name, email, first_name, last_name, membership_level, account_state, etc.). Here is an example that sends a custom email when you add a member from the admin side:
add_action( 'swpm_admin_end_registration_complete_user_data', 'my_custom_new_member_email' ); function my_custom_new_member_email( $member_info ) { $to = $member_info['email']; $first_name = isset( $member_info['first_name'] ) ? $member_info['first_name'] : ''; $subject = 'Welcome to our site'; $body = "Hi " . $first_name . ",\n\n"; $body .= "Your account has been created. Your username is: " . $member_info['user_name'] . "\n\n"; $body .= "You can log in here: " . wp_login_url() . "\n"; wp_mail( $to, $subject, $body ); }If you need the member’s ID (for example, to look up more details), you can get the record by email:
$member = SwpmMemberUtils::get_user_by_email( $member_info['email'] ); $member_id = $member->member_id;You can add the code using a plugin like Code Snippets, or in your child theme’s functions.php file.
If you don’t want the plugin’s default email to go out as well, uncheck this option:
Simple Membership -> Settings -> Email Settings -> “Send Email to Member When Added via Admin Dashboard”
Then only your custom email will be sent.
October 17, 2026 at 6:54 am in reply to: PPCP renewals saved with empty member_id (4.7.2 fallback has no effect) #32389admin
KeymasterThank you. I will look into it and apply a fix.
October 17, 2026 at 6:49 am in reply to: PAYMENT.SALE.COMPLETED is lost permanently when the PayPal API call fails #32388admin
KeymasterThank you. I have applied a fix. It will go out with the next release.
October 17, 2026 at 6:48 am in reply to: BILLING.SUBSCRIPTION.PAYMENT.FAILED is subscribed but never handled #32387admin
KeymasterThank you. I will apply a fix for this. It will go out with the next release.
admin
KeymasterThanks for the details. When the reset link is clicked, the plugin reads the
action,keyandloginvalues from the link’s URL to decide whether to show the “set new password” form. Since you’re seeing the original reset request form again, those values aren’t reaching the plugin. This is usually caused by the hosting environment rather than the plugin itself.Please check the following:
Click the reset link from the email in a private/incognito window. Once the page loads, look at the address bar. Does the URL still contain
?action=swpm-reset-using-link&key=...&login=...?If the URL has changed, a redirect is stripping those values.
Go to WP Membership > Settings > General Settings and confirm the Password Reset Page URL exactly matches the live URL of the page containing the[swpm_reset_form]shortcode (same https/www format). It should be a clean URL such ashttps://example.com/password-reset/with no?in it.
WordPress.com applies its own page caching. If the URL is intact but you still see the request form, the cached version of the page is being served. Please ask WordPress.com support to exclude your password reset page from caching.As a workaround, you can disable Enable Password Reset Using Link in the settings. The plugin will then email the member a new temporary password instead of a link.
More info:
https://simple-membership-plugin.com/password-reset-notification-email-customization/Let us know what you find in step 1 and we can go from there.
-
AuthorPosts