You do not need the block editor to use the plugin. Every block has a shortcode twin, and the access rules are enforced on the server, far below whatever built the page.
Shortcodes anywhere
Wherever WordPress runs shortcodes, the memberarea ones work: the classic
editor, a shortcode widget in Elementor, a Code or Text module in Divi, an HTML
module in Beaver Builder, and template files through do_shortcode().
| Shortcode | Attributes |
|---|---|
[memberarea_checkout] |
product, label, class |
[memberarea_product] |
product, layout (compact or full), class |
[memberarea_cart] |
class |
[memberarea_form] |
form, class |
[memberarea_badge] |
badge, class |
[memberarea_login] |
sign_in, sign_out, avatar, name, logout, align, class |
[memberarea_my_courses] |
empty, signedout, link, linklabel, class |
[memberarea_progress] |
course, empty, signedout, link, linklabel, class |
[memberarea_course_catalogue] |
button, owned, empty, link, linklabel, class |
product, form, badge and course take the UUID of that item, which you
copy from your memberarea. The class attribute puts your own class on the
wrapper, which is how you make a block match a builder's styling.
Locking a page you built with a builder
The panel that sets a rule lives in the block editor, but the rule itself is stored on the page and checked on every request. So you can set it once in the block editor and keep editing the page in your builder afterwards: the lock stays.
For a page whose builder takes over the whole template, choose the denial with care:
- Are sent to the sign-in and Are sent to another page happen before the page is rendered at all, so they work whatever draws the page.
- See a short message instead swaps the message into the page content. A builder that renders its own template without the standard content filter can bypass it, and the visitor then sees the page.
Test every locked builder page once in a private window. If the content still shows, switch that page's rule to the sign-in or the redirect answer, which cannot be bypassed that way.
What is always covered
Whatever built the page, the plugin also guards the places content leaks out of:
excerpts, archive and search listings, query loops, the WordPress sitemap and
the REST API. A locked page cannot be read through /wp-json either.
What needs blocks
Two things have no shortcode, because they are properties of a block rather than something you place:
- Block-level visibility, which shows a single block only to members, only to guests or only to holders of a course.
- Setting up a page rule, as described above.
If you work in a builder most of the time, the practical route is to switch a page to the block editor for a minute, set the rule, and go back.
Caching
Nothing changes for builders: pages stay cacheable for anonymous visitors, and
responses for signed-in members are marked not to be cached. If your builder
ships its own cache, check that it honours DONOTCACHEPAGE before you rely on a
locked page.