BLOG
BlogGuides

Test a membership site: members in, everyone else out

Caching can show members' content to the public, or lock members out. One test signs in as a member and checks a visitor in a separate browser sees only the teaser.

Two ways to break a paywall#

Membership sites (courses, paid newsletters, member directories, client portals) promise two things at once: members see the content, and nobody else does. Both break, and usually for the same reason: a page cached for one kind of visitor is served to the other.

From the WordPress support forums:

MemberPress publishes setup instructions for popular caching plugins for exactly this reason: pages like the account, login and thank-you pages must never be cached, and logged-in users should not be served cached pages.

The trap for the agency is that the site owner, signed in as an admin, sees everything either way.

The test: a member and a visitor#

Store a sign-in account for a test member on the right membership level. Then write one test with two people, each in their own browser:

Two people take part: a member, using the stored account "member",
and a visitor who is not signed in and uses a separate browser.

As the member: open the lesson "Module 3: Pricing" and check the
lesson video and the text "Worksheet: pricing your first offer"
are shown.
As the visitor: open the same address and check the page asks to
sign in or join, and the text "Worksheet: pricing your first offer"
is not shown.

Two separate browsers matter: in one browser the member's cookies would decide what the visitor sees. And keep each person's steps together; when we alternated the two people's steps in one test, the run came back Inconclusive because they were done out of order.

What a two-person run looks like#

On our practice site, an editor who sees drafts and a visitor who must not were tested in one run, each in a separate browser.

The same page in the two browsers of one run: the editor sees the draft and a banner, the visitor sees only what is published.
The same page in the two browsers of one run: the editor sees the draft and a banner, the visitor sees only what is published.

Open the run (live until 18 February 2027) or read the write-up.

Also worth a test#

  • The other levels. A Bronze member opening a Gold lesson sees the upgrade page, not the lesson (roles).
  • After cancelling. A test account with an expired membership sees the teaser again.
  • Sign-up to first lesson. A new member joins with the run's mailbox, confirms, and reaches lesson 1.

Run the member-and-visitor test nightly and after every change to caching, the theme or the membership plugin: it is the one that would have caught each forum thread above.

This post is part of Find the bug before your client does.

Filed underWebSign-in and codesClient sites