Membership Plugin

WordPress Membership Plugin

  • Home
  • Documentation
  • Addons
  • Support
    • Quick Setup
    • Documentation
    • Premium Addon Support
    • Paid Support
    • Support Forum
    • Support Forum Search
    • Forum Login
    • Forum Registration
  • Contact
You are here: Home

admin

  • Profile
  • Topics Started
  • Replies Created
  • Engagements
  • Favorites

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 1,561 total)
← 1 2 3 4 … 103 104 105 →
  • Author
    Posts
  • September 14, 2026 at 5:26 am in reply to: Issues after re-signing in #32323
    admin
    Keymaster

    Good progress. The wp_set_current_user(0) line explains the logout problem, so that part is sorted.

    The remaining -1 is a nonce failure, not a plugin bug. A -1 with a 403 from admin-ajax.php is WordPress’s response when nonce verification fails. If the action itself were missing you would get 0 instead.

    WordPress nonces are tied to the current user ID and the current session token, not just the action name. So a nonce created while logged out (user ID 0) will fail once it is verified as a logged-in user, and a nonce created before a logout will fail after logging back in, because logout destroys the WordPress session token and the new login creates a different one.

    Most likely cause: the nonce is going out inside a JS file or markup that is being cached in a different login state. Even without a caching plugin, JS minify/combine/optimise features (Autoptimize, LiteSpeed, SiteGround Optimizer, Jetpack Boost, Perfmatters, theme optimisers, CDN asset combining) will bake a stale nonce into a cached file. Turn all JS optimisation off and retest.

    To confirm, log get_current_user_id() and wp_get_session_token() both where you create the nonce and at the start of your AJAX handler, then compare. Also check that your AJAX URL is built with admin_url(‘admin-ajax.php’) so the host and scheme match the page, otherwise the auth cookie is not sent and the request is evaluated as logged out.

    Finally, a nonce is CSRF protection, not authentication. Keep the SwpmMemberUtils::is_member_logged_in() check for deciding what data to return, and register both wp_ajax_ and wp_ajax_nopriv_ handlers for your action.

    The custom archive code is outside what we can support here, but this should be enough to track it down.

    September 12, 2026 at 5:18 am in reply to: swpm_session cookie slows my site to a crawl #32305
    admin
    Keymaster

    First, some context on that cookie. swpm_session is not the login cookie. The plugin assigns every visitor a random session ID, and that ID is used only as a key for short-lived front-end status messages (registration errors, profile update confirmations, password reset notices). It expires when the browser closes and holds no member data.

    It is also only issued once per visit, not on every page. The Set-Cookie header goes out on the first request, and after that the cookie is simply present in each request. So what is slowing you down is the CDN treating any request that carries a cookie as uncacheable, rather than the plugin re-issuing it each time.

    The cookie you actually want the cache to react to is swpm_in_use (and wp_swpm_in_use). We set that one only when a member logs in, specifically so caching layers can bypass the cache for logged-in members while still serving cached pages to everyone else. Full cookie list here:
    https://simple-membership-plugin.com/cookies-used-by-simple-membership-plugin/

    What I would recommend:

    1. Ask their support to ignore swpm_session in the StackCDN caching decision, and to bypass cache only when swpm_in_use, wp_swpm_in_use or wordpress_logged_in_* is present. This is the proper fix and it applies site-wide. StackCache itself has no cookie exclusion field, so this has to be done at the CDN/edge level.
    2. In StackCache > Cache Exclusion, exclude your membership pages: the login page, the join/registration page, the thank you page, and any member-only pages. Those should never be served from cache.
    3. Leave everything else cached as normal.

    On “Remove All Cookies From My Homepage”: it only affects the homepage, so it will not solve the problem across the rest of your site. It is safe if your homepage is plain public content with no membership elements. Do not enable it if your homepage contains the login form or login widget, the registration form, or protected content, because stripping cookies from that response also strips the login cookies and the login will silently fail.

    I would also leave “Remove PHP Session Cookies From All Pages” alone. That targets PHPSESSID, not our cookie, and it can break other plugins.

    More background on caching and membership sites:
    https://simple-membership-plugin.com/understanding-the-impact-of-caching-on-membership-sites/

    September 11, 2026 at 7:35 am in reply to: Customizing the login limit message #32302
    admin
    Keymaster

    That message is shown on a browser or device that was logged out after the same account logged in elsewhere. The text is translatable, so you can change it using this technique:
    https://simple-membership-plugin.com/customize-text-and-messages-using-the-translation-file/

    September 11, 2026 at 7:34 am in reply to: Issues after re-signing in #32301
    admin
    Keymaster

    No, this isn’t normal. The logout link is designed to log the user out of both the member session and the WordPress session. There is one exception: if the plugin doesn’t see an active member session when the link is clicked, it exits early and the WordPress session is left untouched. That matches what you’re seeing, so the two sessions are getting out of step somewhere.

    Could you tell me:

    How members log in. Is it only through the Simple Membership login form, or also wp-login.php, another plugin, or custom code?
    Whether any custom code calls wp_signon() or wp_set_auth_cookie().
    Whether Redis or Memcached object caching is active on your host.

    Please also enable Simple Membership -> Settings -> Enable Debug. Reproduce the login, logout, login, logout cycle once and share the log-auth file’s content from those interactions.

    Keep the SwpmMemberUtils::is_member_logged_in() change. It’s the right check for member content.

    September 6, 2026 at 6:49 am in reply to: Issues after re-signing in #32296
    admin
    Keymaster

    A couple of corrections first, because they are pointing you the wrong way.

    1) Having a Simple Membership member record and a corresponding WordPress user record is normal. Their IDs do not need to match. The connection relies on matching usernames and email addresses, so different IDs alone do not indicate a synchronization problem.

    The following documentation explains this:
    https://simple-membership-plugin.com/understanding-the-connection-between-simple-membership-members-and-wordpress-users/

    2) Also, onclick="<?php wp_logout() ?>" runs on the server at render time, not on click, so it was logging you out on every page load. That explains the second symptom you saw. Please remove it.

    The real cause is almost certainly a cached response. /?swpm-logout=true is a plain GET that returns a redirect, and if the browser or a CDN/host cache replays it, the request never reaches PHP, so you land on the homepage still logged in. The -1 is WordPress’s nonce failure output, and nonces are bound to the current WP user and session token, so a cached page carrying a stale nonce will fail the same way. One root cause, two symptoms.

    To confirm:

    1. Run the full login/logout/login/logout cycle in an incognito window.
    2. Check for caching outside WordPress (Cloudflare, LiteSpeed, host-level page cache), which stays active after deactivating a caching plugin.
    3. Add a cache buster to the logout link as a test: home_url(‘?swpm-logout=true&nc=’ . time()). Extra parameters are ignored by the handler.
    4. Exclude the page containing the nonce from caching, or fetch the nonce via AJAX.
    5. Enable Simple Membership > Settings > Advanced Settings > Enable Debug, reproduce once, and send me log-auth-*.txt.
    August 21, 2026 at 9:40 am in reply to: Registration form problem #32260
    admin
    Keymaster

    We have responded through our paid add-on email support channel, and I believe the issue has now been resolved. If you are still experiencing any problems, please reply to that email.

    August 16, 2026 at 7:10 am in reply to: Bug: Member-level users get 404 on protected Events pages #32259
    admin
    Keymaster

    Thanks for the detailed testing.

    Worth clearing up first: our plugin never returns a 404. Core protection replaces the post content with the protection message, and the Full Page Protection addon replaces the page output or redirects. Neither sets a 404 status anywhere. So the “page doesn’t seem to exist” result means WordPress is resolving that request as not-found before our access check runs, which is why switching addons changed nothing.

    The quickest way to confirm this: deactivate Simple Membership and both addons entirely, log in as that member’s WordPress user, and visit /events/ and one event. If you still get the 404, our plugin is not involved.

    Two other things to check while you are there:

    1) The anonymous test may have been served from LiteSpeed’s cache rather than PHP. Retest anonymously with ?nocache=1 on the end of the URL, or with LiteSpeed Cache deactivated. If it 404s then too, the behavior is the same for all non-admin visitors.

    2) Confirm the event’s Visibility is Public, not Private. Private posts show fine for admins but 404 for subscriber level users, which matches what you are seeing.

    Let me know how the deactivation test goes and we will take it from there.

    August 14, 2026 at 3:53 am in reply to: Bug: Member-level users get 404 on protected Events pages #32257
    admin
    Keymaster

    Hi, Instead of the Custom Post Protection addon, please try the following full page protection one. Does it work better with this tribe events post type?
    https://simple-membership-plugin.com/full-page-protection-addon-simple-membership/

    August 12, 2026 at 5:34 am in reply to: Users unable to complete registration #32252
    admin
    Keymaster

    Private browsing on cellular rules out browser caching, but not server side or CDN caching, so let’s narrow it down properly.

    First, what that message actually means. The registration form only outputs “Free membership is disabled on this site” when PHP receives no member_id and code values in the request (and no level is specified in the shortcode). If PHP had received those two values but they did not match a member record, you would instead see “This unique registration link is invalid. Could not find a match for the given member ID and the security code.” If the account had already been completed, you would see “This unique registration link has already been used.”

    So the fact that the parameters are visible in the address bar while you get the free membership message tells us the HTML being returned was not generated for that specific request.

    Two quick tests:

    Test 1: use a deliberately wrong code.
    https://yoursite.com/membership-join/membership-registration/?member_id=36&code=wrongcode123

    If you get the “This unique registration link is invalid” message, PHP is receiving the parameters. The problem is then with the member record or the reg code, not caching.
    If you still get “Free membership is disabled”, PHP is not seeing the parameters at all, which means a cached or proxied copy of the page is being served.

    Test 2: add a random parameter to a valid link.
    …?member_id=36&code=REAL_CODE&nocache=987654

    If it suddenly works, a cache layer is keying on the base URL and ignoring the query string.

    If the tests point to caching: caching is not only caching plugins. Please check for:

    Host level page caching (SiteGround, WP Engine, Kinsta, Cloudways/Varnish, LiteSpeed server cache, NGINX FastCGI cache). This is enabled by default on many hosts and is independent of any plugin.
    CDN or proxy caching, particularly Cloudflare with “Cache Everything” or APO enabled.
    Open the registration page in your browser’s dev tools, Network tab, and look at the response headers for the document request. Values like cf-cache-status: HIT, x-cache: HIT, age: or x-litespeed-cache: hit confirm a cached copy is being served.

    Note that “my page edits show up instantly” does not rule this out, because saving a page automatically purges that one page in most host level caches, while the registration page keeps serving its cached copy to visitors.

    If the parameters are reaching PHP (Test 1 shows the “invalid link” message): go to Simple Membership > Members, confirm the record for member ID 36 still exists and has an empty username (an incomplete profile), and confirm the code in the email matches the reg code on that record. You can resend the registration completion email from that same menu.

    One more thing worth verifying. In your log the generated signup link is on /membership-registration, but the link you pasted is /membership-join/membership-registration/. Go to Simple Membership > Settings > Pages tab and make sure Registration Page URL is the exact permalink of the page that contains the [swpm_registration_form] shortcode. If it does not match, the request goes through a redirect first, and some redirect rules or plugins drop the query string. You can view the currently configured URLs under Simple Membership > Tools > System Info.

    August 11, 2026 at 3:52 am in reply to: Users unable to complete registration #32246
    admin
    Keymaster

    Hi, this looks like the same caching issue you ran into before. See the previous thread here:

    https://simple-membership-plugin.com/forums/topic/user-registration-after-payment/

    With caching enabled, the page isn’t rendered dynamically. Instead of showing the registration form for that member, you’re seeing a static cached version of the page, which is why it displays “Free membership is disabled.”

    This is a known caching-related issue and is explained in more detail here:
    https://simple-membership-plugin.com/understanding-the-impact-of-caching-on-membership-sites/

    To fix it, you’ll need to exclude caching on pages that require dynamic content (such as the registration page). Otherwise, this will keep happening.

    August 7, 2026 at 6:38 am in reply to: dissonance between membership login and wordpress login #32241
    admin
    Keymaster

    Please check this documentation to see if this is helpful:
    https://simple-membership-plugin.com/creating-member-logout-link/

    August 5, 2026 at 5:06 am in reply to: 403 Error – Redirect to Paid Registration Link #32235
    admin
    Keymaster

    It has been a couple of weeks, so I’ll mark this topic as resolved. If you still need assistance, please reply here.

    August 3, 2026 at 3:25 pm in reply to: User registration after payment #32232
    admin
    Keymaster

    Thanks for the log, it’s helpful. Everything on the plugin side worked: member record 18 was created, the unique link was generated, and the return URL was set to the paid registration link.

    The “Free membership is disabled” message only appears when the registration page loads without the member_id and code values in the URL. So the link is correct, but those parameters aren’t reaching the page. That’s a site-level issue, not a plugin setting, and no addon is required.

    First, edit your registration page and confirm the content is just [swpm_registration_form] with no extra attributes such as a hardcoded level value, and that Settings > General Settings > “Registration Page URL” points to that page. This documentation covers how the required pages should be set up and how to recreate them if needed:
    https://simple-membership-plugin.com/recreating-required-pages-simple-membership-plugin/

    Then test this: open the exact link from the log in a private browsing window and check the address bar after it loads. If the parameters have disappeared, something is stripping them. Common causes are page caching or a CDN, a server redirect that drops the query string (http→https, www, trailing slash), or a security plugin filtering query args. Exclude the registration page from caching and review your redirect rules.

    https://simple-membership-plugin.com/membership-registration-process-overview/
    https://simple-membership-plugin.com/understanding-the-impact-of-caching-on-membership-sites/

    You can regenerate the link from the plugin’s Tools menu to retest without paying again:
    https://simple-membership-plugin.com/regenerate-and-resend-the-unique-registration-completion-link/

    Also note your log records the user IP as a private address (10.0.0.1). The auto-redirect feature matches the pending member record by IP address, so if your site is behind a proxy or CDN and the plugin isn’t seeing the real visitor IP, it will fall back to the Thank You page. That likely explains the behaviour on your other buttons.

    For the third button, edit and re-save it so the PayPal plan is recreated, then retest. If it still errors, post the browser console output and the log entries from that attempt.

    July 27, 2026 at 6:26 am in reply to: I am not receiving registration emails for pending accounts #32220
    admin
    Keymaster

    You can create as many free membership levels as needed. Each level simply needs to be configured according to your site’s requirements.

    The following documentation explains the available options for offering free memberships:

    https://simple-membership-plugin.com/offering-multiple-free-memberships-site/

    https://simple-membership-plugin.com/offer-customers-free-membership/

    July 20, 2026 at 5:42 am in reply to: dissonance between membership login and wordpress login #32213
    admin
    Keymaster

    Did you import any users into this site, or were they created directly through the Simple Membership plugin? During an import, invisible whitespace or other hidden characters in a field value can sometimes cause this type of mismatch.

    As a test, delete the affected user (from WP users interface) and also from the SWPM interface. Then manually add the member through the Simple Membership admin interface:
    https://simple-membership-plugin.com/manually-adding-members-site/

  • Author
    Posts
Viewing 15 posts - 31 through 45 (of 1,561 total)
← 1 2 3 4 … 103 104 105 →
« Previous Page

Please read this message before using our plugin.

Search

Featured Addons and Extensions

  • Membership Form Builder Addon
  • Member Directory Listing Addon
  • WooCommerce Payment Integration
  • Member Data Exporter Addon

Documentation

  • Documentation Index Page

Copyright © 2026 | Simple Membership Plugin | Privacy Policy