Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

MemberPress Rules Not Working: Causes and How to Fix It

MemberPress Rules Not Working: Causes and How to Fix It

Short answer

MemberPress rules usually look broken because admins see all content, page caching serves one copy to everyone, or the rule targets the wrong page, category or membership. Test in a private window while logged out, exclude protected pages from cache, then check the member's transaction status and any drip settings.

Key takeaways

  • Admins see all protected content, so always test logged out.
  • Page, server and CDN caches can leak protected pages to everyone.
  • Check that each rule targets the right content type and membership.
  • Pending, failed or expired transactions block members even with correct rules.
  • Drip and expiration settings can hide content from active members.
  • Custom URI rules depend on working rewrite rules on your server.

Why are MemberPress rules not working?

MemberPress rules usually seem broken because you are testing as an admin, caching serves the same page to everyone, the rule targets the wrong content, or the member's subscription is not active.

Rules are how MemberPress protects content. Each rule says what is protected, such as a page or category, and who can see it, such as members of a certain membership.

When a rule fails, one of two things happens. Either non-members can see protected content, or paying members get blocked.

The fixes differ for each case, so first work out which one you have. Then go through the checks below. MemberPress explains how rules are built in its rules overview documentation.

Are you testing while logged in as an admin?

Administrators can see all protected content in MemberPress, so testing while logged in as an admin will always make rules look like they are not working.

This is the most common false alarm. The rule is fine, but you are seeing the page as an admin.

How to test properly:

  • Open a private window. Visit the page while logged out to see what the public sees.
  • Create test users. Make one user with an active membership and one without. Log in as each in separate private windows.
  • Use a different browser. This avoids leftover cookies from your admin session.

A user switching plugin can help you view the site as a specific member. Just remember to switch back to your own account afterwards.

Is caching serving protected pages to everyone?

Page caching can save a copy of a protected page and serve it to every visitor, which makes content visible to non-members or blocks members.

MemberPress decides access for each visitor when the page loads. A page cache skips that step and serves a saved copy instead.

How to fix it:

  • Exclude protected pages from cache. Add the URLs of protected content, account pages and login pages to your caching plugin's exclusion list.
  • Do not cache logged-in users. Most caching plugins have this option. Make sure it is on.
  • Check server and CDN cache. Host-level caches and CDNs such as Cloudflare can cache pages too. Cloudflare explains what it caches in its cache documentation.
  • Clear every cache after changing rules.

MemberPress sets cookies for logged-in members. Some caching plugins can bypass cache when those cookies are present. Check your caching plugin's documentation for cookie exclusions.

Our guide on how to clear cache in WordPress shows where each common cache lives.

Does the rule target the right content?

A rule only protects what its content type covers, so choosing the wrong type, the wrong page or the wrong category leaves content open.

MemberPress offers several ways to choose content. Common rule types include:

  • All content. Protects everything of a post type, with exceptions you can set.
  • A single page or post. Protects one item.
  • Child pages of a page. Protects pages under a parent, but not always the parent itself.
  • Posts in a category or with a tag. Protects posts assigned to that category or tag.
  • Custom URI. Protects any address matching a text or pattern you enter.
  • Partial content. Protects sections inside a page using a shortcode or block.

Typical mistakes:

  1. Protecting a category but forgetting that some posts are not in it.
  2. Protecting child pages and expecting the parent page to be protected too.
  3. Using a Custom URI with a typo or an incorrect pattern.
  4. Protecting a page, then building a second copy of it that is not protected.

Open MemberPress > Rules and read each rule's content selection carefully. A quick fix is to add a rule for the exact page that leaks.

Is the access condition set correctly?

The access condition decides who can see protected content, and a rule with the wrong membership, role or user selected will block or allow the wrong people.

Each rule has one or more access conditions. They can be based on a membership, a specific member, a WordPress role, or a capability, depending on your version.

Check:

  • The right membership is selected. Easy to miss when you have similar membership names.
  • All needed memberships are listed. If a premium tier should also see basic content, add both memberships to the rule.
  • Conditions are combined as intended. When several conditions are listed, the logic decides whether a user needs one or all of them.

When two rules cover the same page, MemberPress checks them together. Overlapping rules with different memberships can produce surprising results, so keep rules simple and avoid overlaps.

Is the member's subscription actually active?

Members are blocked if their transaction is pending, failed, expired or refunded, even when the rule itself is correct.

Go to MemberPress > Members and open the member. Then check MemberPress > Transactions and Subscriptions for their status.

Common account problems:

  • Pending payment. Offline or bank payments stay pending until you mark them complete.
  • Expired access. A one-time membership may have ended.
  • Failed renewal. A card failed and the subscription lapsed.
  • Wrong membership. The user bought a different tier than the one the rule allows.

You can add or edit a transaction by hand to fix access for a single member. For payment gateway problems, check the gateway's own logs.

Are drip or expiration settings hiding content?

Drip and expiration options on a rule can hide content until a set time after signup, or remove access after a period, even for active members.

Drip releases content gradually, for example a week after a member joins. Expiration removes access after a set time.

If a new member cannot see a lesson, check the rule's drip settings. If an older member lost access to some content, check the expiration settings.

These options are useful for courses and paced programs. They are also easy to forget once set.

Is the unauthorized message or redirect working?

If non-members see a blank page or the wrong message, the unauthorized access settings may be misconfigured rather than the rule itself.

MemberPress has global unauthorized settings and per-rule overrides. They control whether non-members see an excerpt, a login form, a custom message, or get redirected to another page.

Check MemberPress > Settings for the unauthorized options, then check the rule's own unauthorized tab. A per-rule setting overrides the global one.

If you redirect unauthorized visitors, make sure the redirect page is not itself protected. That creates a loop.

Could the theme or a page builder bypass the rule?

Some themes, page builders and plugins load content in ways that skip the normal WordPress content filters MemberPress relies on, so protected text can leak through.

Examples include:

  • Custom templates that print post content directly.
  • Page builder templates used for archives or single posts.
  • Related posts, sliders and search results that show excerpts or full text.
  • Feeds and the REST API, which may expose content outside the normal page view.

Test by switching temporarily to a default WordPress theme on a staging site. If protection works there, the theme or builder template is the cause.

To find a conflicting plugin, disable plugins one at a time. Our guide on fixing plugin conflicts explains a safe way to do this.

Are protected files and Custom URI rules supported by your server?

Custom URI rules and file protection rely on server rewrite rules, so they may not work on some server setups, especially Nginx without extra configuration.

WordPress uses rewrite rules for pretty permalinks. MemberPress uses them for some protection features too.

If URI-based rules fail:

  1. Go to Settings > Permalinks and click Save Changes to flush rewrite rules.
  2. Make sure permalinks are not set to Plain. WordPress explains the options in its permalinks documentation.
  3. On Nginx, ask your host whether extra rules are needed.

Direct links to media files are a separate issue. Files in the uploads folder are served by the web server without WordPress, so a page rule alone does not protect them.

Which symptom points to which cause?

Use this table to jump to the most likely cause for what you are seeing.

SymptomLikely causeFirst check
You can see everythingLogged in as adminTest in a private window
Logged-out visitors see protected contentCaching or wrong rule targetExclude from cache, review rule
Paying member is blockedInactive or pending transactionCheck Transactions
New member cannot see some lessonsDrip settingsReview rule drip options
Some posts leak, others are fineCategory or tag not assignedCheck each post's terms
Redirect loopRedirect page is protectedUnprotect the target page
Custom URI rule ignoredRewrite rules or pattern errorResave permalinks, check pattern

When should you contact MemberPress support?

Contact MemberPress support when you have tested logged out, cleared all caches, confirmed the rule and member status, and ruled out theme and plugin conflicts.

Include the rule settings, the page address, a test account, and your MemberPress version. Turning on WordPress debugging first can reveal errors. Our guide on how to enable debug mode in WordPress shows how.

MemberPress also has a guide to protecting content worth reviewing before you contact them. For background on the costs of running a members site, see our guide on what a WordPress membership site costs.

Frequently asked questions

Why can I see protected content when I am logged in?

Administrators can view all content regardless of MemberPress rules. Test in a private browser window while logged out, or log in as a test user who has the membership you want to check.

Does caching break MemberPress?

It can. A page cache may store a protected page and show it to everyone, or store the locked version and show it to members. Exclude protected pages, account and login pages from cache and do not cache logged-in users.

Why is a paying member blocked from content?

Check their transaction and subscription status first. Pending, failed, refunded or expired transactions remove access. Also check that the rule includes the membership they bought and that drip settings are not delaying the content.

Do MemberPress rules protect uploaded files?

Not automatically. Files in the uploads folder are usually served directly by the web server without loading WordPress, so a page rule does not cover them. Use a file protection feature or a dedicated download manager for private files.

What happens when two rules cover the same page?

MemberPress evaluates the rules together, which can give unexpected access results if they list different memberships. Keep rules simple, avoid overlaps, and add all memberships that should have access to a single rule where possible.

Sources

  1. Rules Overview MemberPress Docs
  2. Protect content with MemberPress MemberPress Docs
  3. Customize permalinks WordPress.org
  4. Debugging in WordPress WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.