Skip to content

EP Membership

EP Membership gives your PageMotor site a public-user authentication layer. Visitors register, log in, manage their profile, and you gate content behind a login or a membership level. Pairs naturally with EP Courses for members-only learning content and EP Ecommerce for paid membership tiers.

Published by ElmsPark Studio.

  • Registration form on a public page, with optional email verification. The emailed link opens a “Confirm my email address” button (0.8.1), so email security scanners cannot use it up before the member does.
  • Login form with lockout after repeated failed attempts.
  • Built-in password reset via email (secure one-hour tokens, no extra plugin needed).
  • Profile page for members to update their own details.
  • Member dashboard showing up to three of the member’s most recent course enrolments, with progress (with EP Courses).
  • Member levels (0.5.0): optional ordered tiers — Free, Pro, VIP or whatever fits your site.
  • Level-gated content (0.5.0): gate a span of content or a whole page by level.
  • Purchase grants (0.5.0): active EP Ecommerce membership purchases count towards a member’s level automatically.
  • Members Only documents (0.6.0): a protected content type that PageMotor itself refuses to non-members, so the document stays out of the sitemap, the content API, site search and search-engine pings.
  • Login gating on any shortcode-wrapped content. (EP Courses always asks members to sign in before they enrol or open a lesson.)
  • Integration with EP GDPR for consent capture and logging on registration.
  • Integration with EP Newsletter for an opt-in checkbox on the registration form.

Members are stored as PageMotor’s own User type, marked as members by this plugin, so they have no admin access. If a member does reach the admin, the plugin sends them to their profile page.

On PageMotor 0.10, members used a separate Learner type. On an upgraded site they are switched over the next time an administrator opens any admin page (see 0.6.9).

Version 0.9: registration, login, Sign in with Google, member levels, Members Only documents, member import (from the admin or an assistant) and the assistant actions (API and MCP) all work on PageMotor 0.11.5.

  • PageMotor 0.11.5 or later. (EP Membership 0.6.11 and earlier ran on PageMotor 0.7 and later, including 0.10.)
  • EP Suite base class
  • EP Email, or PageMotor 0.11’s built-in mail. Transactional email (verification, welcome, password reset) goes through EP Email when it is active. Without it, 0.6.1 and later fall back to PageMotor’s own mailer (0.11+), and those sends appear in core’s email log attributed to EP Membership. On 0.6.0 and earlier, or on a 0.10 core with no EP Email, those emails are not sent and the failure is silent: each attempt is written to the PHP error log only.

Optional:

  • EP Courses for the enrolment lists on the member dashboard and profile.
  • EP Ecommerce / EP Ecommerce Subscriptions for purchase-granted membership levels.
  • EP GDPR for a required consent checkbox on registration, with consent logging.
  • EP Newsletter for a newsletter opt-in checkbox on registration.
  1. Make sure the site can send email, through either EP Email or PageMotor’s own mail settings. Both deliver the verification, welcome and reset emails.
  2. ep-membership.zip comes with an EP Suite licence — ElmsPark supplies it directly (see EP Suite plugins); after install it updates through your site’s Updates screen.
  3. Upload via Plugins → Manage Plugins. Activate.
  4. Create pages for registration, login, and profile:
    • [ep-register-form] at /register/.
    • [ep-login-form] at /login/.
    • [ep-member-profile] at /profile/.
    • Optionally [ep-member-dashboard] at a members’ landing page.
  5. In settings, check the Login Page Slug, Registration Page Slug, and Profile Page Slug match the pages you created, and set the After Login Redirect.
  6. Optionally define Member Levels (see below).
ShortcodePurpose
[ep-register-form]Registration form: full name, email, preferred language, password with confirmation. Includes a honeypot spam trap, and GDPR consent / newsletter opt-in checkboxes when those plugins are active.
[ep-login-form]Login form: email and password, with a forgotten-password flow. A sign-in lasts PageMotor’s own seven days.
[ep-logout-link]Log out button. Optional text for the label and redirect for the page to land on afterwards. Shows nothing to a visitor who is not signed in.
[ep-member-profile]Profile editor for the signed-in member (display name, preferred language, password change). Shows the login form to visitors.
[ep-member-dashboard]Signed-in landing page. With EP Courses active it lists up to three of the member’s most recent active enrolments, with progress bars.
[ep-login-gate]...content...[/ep-login-gate]Gate the wrapped content to logged-in members. Visitors see a message and a login link instead. Optional message="..." argument overrides the default prompt.
[ep-level-gate level=pro]...content...[/ep-level-gate]Gate the wrapped content by membership level (0.5.0). Visitors see a login prompt; members below the level see an upgrade prompt; members at or above the level see the content. Optional message="...".

The bare, unprefixed forms of the original six ([register-form], [login-form], [logout-link], [member-profile], [member-dashboard], [login-gate]) still work as deprecated back-compat aliases for existing content. Use the ep- prefixed forms in new content.

Levels are optional. Define them in settings under Member Levels: one per line, lowest tier first, as slug | Label:

free | Free
pro | Pro
vip | VIP

Line order is rank order — a Vip member passes every Pro and Free gate. New members receive the Default Level at registration (blank means the first line). Leave the levels box empty and the plugin behaves exactly as it did before levels existed.

A member’s effective level is the higher of:

  • the level assigned to them (at registration, or by you in the Members panel), and
  • any active purchase grant (below).

Change a member’s level any time from the Members panel in settings. Every member is listed with a level selector.

With the Purchase Grants setting on and EP Ecommerce installed, an active membership purchase lifts the member’s effective level automatically. Set the product’s membership_level to one of your level slugs; EP Ecommerce Subscriptions records the grant on purchase and renewal. Grants are checked live, so an expired or cancelled subscription stops counting immediately — no sync job, no delay.

A product whose level is not in your list is ignored by the ladder. EP Ecommerce 0.1.40 and later warn you when you save such a product. The product still sells, and its buyers still pass EP Ecommerce’s own exact-match [ep-membership-content] gate; they just gain nothing on this plugin’s ladder.

There are two kinds of gate in this plugin, and the difference matters if you are selling access.

Presentation gates control what a visitor sees. The per-page Required membership level, the sitewide gate, and the [ep-login-gate] / [ep-level-gate] shortcodes all work by replacing the page body at render time. The prompt shows correctly in a browser, but the underlying document is still an ordinary public page as far as PageMotor is concerned: its text remains readable through the public content API, it stays listed in sitemap.xml and in site search, and saving it pings the search engines through IndexNow. Use these for soft gating, teasers, and members-only presentation of material you do not mind being readable.

Protection is the Members Only content type (0.6.0). PageMotor refuses the document itself to anyone below the level, before any of those read paths sees the row. Use this for anything you are actually charging for.

The two compose: put the document on the Members Only type for the hard gate, and keep a page’s own Required membership level for the finer one.

Wrap the span in [ep-level-gate]:

[ep-level-gate level=pro]
Here's the pro-and-above content.
[/ep-level-gate]
[ep-level-gate level=vip message="This one is for VIP members."]
VIP-only content with a custom prompt.
[/ep-level-gate]

A gate naming a level you haven’t defined fails open by default (the content shows, with a note in the PHP error log) — a typo degrades to visible, never to a page nobody can see. Since 0.6.3 a site that would rather hide a paid page than leak it can reverse that: Member Levels → When a Gate Names a Level That Does Not Exist, set to hide. The breadcrumb is logged either way.

With levels defined, every page’s content options gain a Membership box with a Required membership level select. Visitors and members below the level see a prompt in place of the page body; the page chrome renders normally. Admins always see the page.

This is a presentation gate, as described above. It changes what renders, not what the site will hand out. If the content must not be readable at all, put the document on the Members Only type as well.

To gate the whole site at once, set Sitewide Required Level in the Member Levels settings to a level slug. Every page then requires that level, except:

  • the paths you list under Public Paths (one per line, / for the homepage — say, a landing page and an application form), and
  • the login and registration pages, which are always public so members can never be locked out of signing in.

A page’s own Required membership level always overrides the sitewide gate. Blank the setting to switch the sitewide gate off; nothing else changes.

This is the only gate that withholds the data itself.

0.6.0 registers one content type, Members Only, which behaves exactly like a standalone HTML document (same renderer, same clean URL) except that PageMotor marks it protected. Core then refuses it to anyone who is not a signed-in member at or above the level you set, and the refusal happens at the content layer rather than at render time. The document is therefore absent from sitemap.xml, absent from list-public-content, returns not_found from get-public-content and from MCP, absent from site search and listings, never pushed to IndexNow, and any file attached to it is refused too.

To use it, open the document in the admin and change its type to Members Only. The document itself is untouched, and moving it back is the same change in reverse.

Set the minimum level under Members Only Document Level in the Member Levels settings. Blank means any signed-in member. This setting exists because a standalone document never renders through the per-page gate, so for these documents it is the gate.

What a visitor sees (0.8.7). Someone who is not signed in gets a sign-in page in your site’s own design: the header, footer, fonts and colours come from your home page, with a “Members only” panel and a sign-in form where the page content would be. After signing in they land back on the document. A signed-in member without the level sees the same design with the upgrade message and a Sign out button, so they can switch accounts. The design is borrowed when your home page is itself a standalone HTML document; otherwise a plain sign-in page is shown. Search engines are told not to index either page.

Admins always have access, as everywhere else in the plugin.

Why this exists. Before 0.6.0 the only gating on offer was the render-time kind, which hides a page body and nothing else. Reported from the field in August 2026 with a full reproduction: a page gated to a level showed the prompt correctly in a browser while its complete text was still being served to anonymous callers through the public content API, and the URL stayed in the sitemap. Credit to andre for the report and for independently identifying the protected-content-type seam as the fix.

Wrap content in [ep-login-gate]...[/ep-login-gate] — visitors get a login prompt, any logged-in member sees the content.

EP Courses always asks members to sign in before they can enrol or open a lesson. (The Lesson Access and Enrolment Access switches that earlier versions showed never had any effect, and were removed in 0.7.1.)

Since EP Courses 0.7.0, each course can name its own membership levels. In the course editor, fill in “Members with any of these levels can take this course” with one or more of your level slugs. Anyone holding one of them can take the course for as long as they hold it:

  • A course set this way is not open for free self-enrolment, and members are never asked to pay for a course their membership includes.
  • When a membership ends, the course closes for them. The lessons they finished are kept, and are there again if they rejoin.
  • Courses without the setting work exactly as before.

This needs EP Membership 0.8.0 and EP Courses 0.7.0. Prefer it to putting the whole course viewer page under a Required membership level, which gates every course on the page alike and does not stop anyone enrolling.

Plugin developers can call member_levels($user_id) and member_has_any_level($levels, $user_id) on the EP Membership instance (0.8.0), or member_has_level($user, $slug) as before.

You can bring members across from another site in one go, with their levels and end dates. Ask your connected AI assistant to import a spreadsheet export (CSV) or a list. It uses the import-grants action:

  • It always shows you what it would do first, and changes nothing until you say so.
  • New accounts are created without sending anyone an email, and running the same import twice changes nothing the second time.
  • Up to 1,000 rows per run. Staff accounts are never touched.
  • Members moving from WordPress can keep their passwords if the export includes the old password hashes. Anyone without one can be sent a “choose your password” email with send-set-password, only when you ask.

Settings, Import Members: choose a CSV file or paste it in, then Preview. The preview shows each row’s outcome and changes nothing. Import then does it, after asking once more. Tick the box to email new members a link to choose their password; otherwise nobody is emailed. The import screen also works on sites with no member levels.

  • General — the site name used in emails and notifications.
  • Registration — enable/disable registration, email verification on/off, default language, after-registration redirect, welcome email on/off, newsletter opt-in on/off.
  • Login: login and registration page slugs, after-login and after-logout redirects, max login attempts, and lockout duration in minutes.
  • Profile: the profile page slug.
  • Member Levels (0.5.0): the level definitions, default level, purchase grants switch, (0.5.1) the sitewide gate with its public-paths list, (0.6.0) the Members Only Document Level, and (0.6.3) what a gate does when it names a level that does not exist: show the content (default) or hide it.
  • Members (0.5.0): every member account, with email, registration date, verification state and a level selector.
  • Social Login (0.9.0): Google on/off, Client ID and Client Secret (stored encrypted), and the redirect address to give Google.
  • Import Members (0.9.0): import a CSV of members, with a preview first.

Built in, so no separate plugin is needed. The login form links to a reset-request form, and the member receives an emailed link with a single-use token that expires after one hour.

Each account can request at most three reset links an hour. Delivery goes through EP Email when it is active, otherwise through PageMotor’s own mailer.

Since 0.7.1, setting a new password signs out every other session on the account. Changing it from the profile page does the same. Each link works once, and after a reset any other reset links sent to that address stop working.

Staff accounts (administrators and producers) reset their password from PageMotor’s own admin log-in page. This form does not send them a link, and its reply is the same for every address.

Members can sign in, or join, with their Google account. The “Continue with Google” button appears on your log-in and registration forms once it is set up.

Setting it up. You need a Google Cloud account.

  1. In Google Cloud Console, open APIs & Services, then Credentials, and create an OAuth client ID of type Web application.
  2. Under Authorised redirect URIs, add the address shown in EP Membership’s Social Login settings. It is your log-in page’s address, for example https://example.com/login/. It must match exactly.
  3. Copy the Client ID and Client Secret into EP Membership’s Social Login settings, tick Google, and save. The secret is stored encrypted.

How accounts are matched.

  • Someone whose Google address matches a member signs straight in. From then on that account belongs to that Google account, and a different Google account using the same address is turned away.
  • Someone new gets a member account with your default level, already verified, as long as registration is open. With registration closed, only existing members can use the button.
  • Staff accounts (administrators and producers) never sign in this way. They use PageMotor’s own admin log-in.
  • If a member’s email address had never been confirmed on your site, the password on that account is removed the first time Google confirms it, their other devices are signed out, and they are emailed to say so. This stops someone who registered the address first from keeping a way in. They can pick a new password with Forgot your password?.
  • Google is the only outside sign-in. Apple, Microsoft and Facebook are not offered.
  • With EP GDPR active, joining with Google starts from the registration form and needs the privacy box ticked, and the consent is recorded as it is for the form.

A member who joined with Google has no password of their own until they set one with Forgot your password?.

When EP GDPR is active, the registration form adds a required consent checkbox, and each registration logs the consent text, email, and IP through EP GDPR’s consent log. Since 0.9.0 both the check and the logging happen on your server, so a registration without the box ticked is refused even if the browser skips the check.

Since 0.7.1, EP GDPR’s data requests include members. An export adds the member’s level, language, verification state and account activity, with an IP address only on activity the member did themselves. An erasure removes their activity log and any unused sign-in links.

Run the erasure before you delete the account in Manage Users. Deleting the account is still how the account itself goes.

With the Newsletter setting enabled and EP Newsletter active, the registration form adds an opt-in checkbox; ticked registrations are subscribed automatically.

“Registration form says email already exists but the user doesn’t remember registering”

Section titled ““Registration form says email already exists but the user doesn’t remember registering””

Look for the email in the Members panel (your browser’s Find works), or ask your connected assistant to search members by email. If the email is there, the person has an account they forgot about. Point them at the Forgot password link on the login form.

“Logins work but the session doesn’t persist”

Section titled ““Logins work but the session doesn’t persist””

Check cookies are being set correctly. Common cause: session cookie’s Secure flag is on but the site is being accessed via HTTP. Ensure HTTPS is the only way in.

“Verification, welcome, or password reset emails aren’t arriving”

Section titled ““Verification, welcome, or password reset emails aren’t arriving””

With EP Email active, check its delivery log for the specific send. Without EP Email, on 0.6.1+ on a 0.11 core, check PageMotor’s own email log (sends appear as source EP Membership); if core mail is not configured either, the attempt is written to the PHP error log, which now names what was missing. On 0.6.0 and earlier there is no fallback: EP Email is required, and a missing EP Email means the email was never sent.

“A member paid for a subscription but their level hasn’t changed”

Section titled ““A member paid for a subscription but their level hasn’t changed””

Check the Purchase Grants switch is on, and that the product’s membership_level matches one of your level slugs exactly. The grant’s level string and your defined slug must be the same word.

“A gated page is still readable through the API, or still in the sitemap”

Section titled ““A gated page is still readable through the API, or still in the sitemap””

Expected, if the page is gated only by its Required membership level, the sitewide gate, or a gate shortcode. Those are presentation gates: they change what renders, not what the site hands out, so the document stays public to the content API, site search and sitemap.xml.

Put the document on the Members Only content type (0.6.0). That is the gate that withholds the data.

“A level gate is showing its content to everyone”

Section titled ““A level gate is showing its content to everyone””

The gate names a level that isn’t defined in settings — undefined levels fail open by default. Check the slug in the shortcode against the Member Levels box, and check the PHP error log for the breadcrumb. If you would rather such a gate hide the content, set Member Levels → When a Gate Names a Level That Does Not Exist to hide (0.6.3).

  • Members can sign in with Google. A new Social Login section in the settings adds a “Continue with Google” button to your log-in and registration forms. Tick Google, paste in the Client ID and Client Secret from your Google Cloud account, and add the address shown on the screen to Google as an authorised redirect address. The secret is stored encrypted.
  • How it matches accounts. Someone whose Google address matches a member signs straight in, and from then on that member’s account belongs to that Google account: a different Google account using the same address is turned away. Someone new gets a member account with your default level, already verified, as long as registration is open. Staff accounts never sign in this way.
  • An address nobody had confirmed. If a member’s email address had never been confirmed on your site, the password on that account is removed the first time Google confirms it. Other devices are signed out and the member is emailed to say so. This stops someone who registered the address first from keeping a way in. The member carries on with Google, or picks a new password with “Forgot your password?”.
  • One address for Google. The address you give Google is your site’s recorded address. A visitor who arrives on another address for the same site (with or without www, say) is moved to the recorded one before the Google sign-in starts.
  • Joining with Google counts towards the limit of five new accounts an hour from one visitor.
  • Import members from the admin. A new Import Members section takes a spreadsheet (CSV), either chosen as a file or pasted in. Preview shows row by row what would happen and changes nothing. Import then creates the missing accounts and gives the levels, after asking once more. Nobody is emailed unless you tick the box, and importing the same file twice changes nothing the second time. It also works on sites with no member levels.
  • Fixed: the registration form now checks the privacy box on your server. With EP GDPR active, a registration without the box ticked was only stopped by the visitor’s browser, and the consent was not recorded in EP GDPR. Both now happen on the server.
  • When EP GDPR is active, joining with Google asks for the privacy box too: the button on the registration form only works once it is ticked.
  • Needs PageMotor 0.11.5.
  • Members Only documents now have a proper door. A visitor who is not signed in sees a sign-in page in your site’s own design, with its header, footer, fonts and colours, a “Members only” panel and a sign-in form. After signing in they land back on the document they asked for.
  • A signed-in member without access sees the same design with the upgrade message, and a Sign out button so they can switch to the right account.
  • The door is never indexed by search engines and carries none of your home page’s sharing or search details.
  • Fixed: a warning written to the server log on every admin page load.
  • Needs PageMotor 0.11.5.
  • Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.

Please install this one. It repairs the links in account emails.

  • Fixed: links in account emails stopped working on 0.8.3 and 0.8.4. On a site where an administrator had opened the admin since updating, the links in the verification, password reset and “choose your password” emails opened the page with nothing on it to confirm or reset. The member saw the plain registration or log-in page. Links sent by 0.8.5 work again.
  • What to tell members. A link from an email sent by 0.8.3 or 0.8.4 will not work, and waiting does not help. Ask the member to press “Forgot your password?” again, or to sign in so a new verification email is sent.
  • Needs PageMotor 0.11.5.

A security update. Please install it.

  • Sign-in lockouts count per account and per connection. Failed sign-ins are limited per account and per address, with a higher cap per address so one office cannot lock everyone out.
  • Registration is limited to five accounts an hour per visitor, and the member activity log keeps 180 days.
  • Sign-in takes the same time whether or not the username exists.

A security update. Please install it.

  • Members-only pages stay out of your feed and your chat assistant. EP Membership now tells your other EP plugins which pages are for members: pages with a sign-in or level gate, pages with a Required Level, and every page under the sitewide gate apart from sign-in, registration and the pages you list as public. EP RSS and EP Concierge leave those pages out, so their text no longer appears in your feed or in the assistant’s answers.
  • Account emails always link to your own site. Verification, password reset and set-password links now use the web address your site had when an administrator last opened the admin, not the address of whoever asked for the email.

A security update. Please install it.

  • Nobody can sign up as one of your customers. When someone registers with an email address that already has orders, downloads or memberships on your site, they must now confirm that address before they can sign in, even with Email Verification switched off. Before, they were signed straight in and could see that customer’s purchases.
  • What your existing members will notice. A member whose email address has purchases but was never confirmed is asked to confirm it once, at their next visit. A link is sent to them automatically when they sign in. Members who already confirmed see no change.
  • Verification links can no longer be used up by email security scanners. Many work email systems, Microsoft 365 and Outlook among them, open every link in an incoming email to check it is safe. Until now that check used up the member’s verification link, so when the member clicked it themselves they were told it had expired. Opening the link now shows a “Confirm my email address” button on your registration page, and only pressing it confirms the address and signs the member in.
  • Links are now stored more safely. Verification, password reset and set-password links are kept in your database in a scrambled form, so a copy of the database or a backup no longer holds links that work. Links already sitting in members’ inboxes keep working after the update.
  • Needs PageMotor 0.11.5.
  • Levels can now stand on their own. A new setting, How Levels Work, lets each level be separate, for example a course, a coaching group and a book club. A member can hold several at once, and each one can have its own end date. Your site keeps today’s ranked levels (Free, Pro, VIP and so on) until you change the setting; nothing changes until then.
  • A page can be opened by any of several levels. With independent levels, the page’s Membership box gains “Or any of these levels”: tick each level that may see the page. A level you chose before switching still applies.
  • New level gate options. [ep-level-gate levels="course,coaching"]...[/ep-level-gate] shows the content to members with any of those levels. Add show="not" to show it only to people who do NOT have them, visitors included, which suits an offer that members already have no need to see.
  • Give a level with an end date, or take it away. Your AI assistant can give one member a level until a date, take it away again, and list every level a member holds and why. A level whose end date has passed stops giving access straight away.
  • Bring your members across from another site. The assistant can import members and their levels from a spreadsheet export (CSV) or a list. It always shows you what it would do first and changes nothing until you say so. New accounts are created without sending anyone an email. Running the same import twice changes nothing the second time.
  • Members moving from WordPress keep their passwords. If your import includes the old site’s password hashes, members can sign in on your log-in page with the password they already know. The first time they do, PageMotor stores its own secure copy and the old one is deleted. Accounts without one can be sent a “choose your password” email, only when you ask.
  • Needs PageMotor 0.11.5.
  • Changing a password now signs out every other session. This applies both to a reset link and to the password change on the profile page, so anyone who knew the old password is logged out too.
  • Each link works once. A reset or verification link can only be used once, even if it is clicked twice at the same moment. After a reset, any other reset links sent to that address stop working.
  • Staff accounts are left to PageMotor’s own reset. The reset form on your log-in page no longer sends links to administrator or producer accounts, and a link sent before an account became staff no longer works. Staff reset their password from the admin log-in page as before. The form’s reply is the same for every address, so it gives nothing away.
  • Course links on the member dashboard and profile now open the course. They pointed at /courses/ followed by the course name, which nothing on the site serves. They now open your EP Courses viewer page. The profile also stops listing unfinished checkouts, refunded courses and draft courses.
  • Members are included in EP GDPR requests. A data export now includes the member’s level, language, verification state and account activity, including failed log-ins against their address. An IP address is included only on activity the member did themselves.
  • An erasure removes their activity log and any unused sign-in links. Run it before you delete the account in Manage Users, which still removes the account itself.
  • Settings that did nothing have gone. Lesson Access and Enrolment Access (EP Courses always asks members to sign in), the Profile Page on/off box, and Remember Me (days). The Remember me box on the log-in form has gone too: a sign-in lasts PageMotor’s own seven days either way.
  • Needs PageMotor 0.11.5.
  • Ask your AI assistant about your members. EP Membership now has its own actions in your site’s API and MCP. An assistant connected to your site can list and search your members, show what a member can see and why, list your levels, show recent account activity, change a member’s level and resend a verification email. Administrators only.
  • It tells you the level that really applies. A purchase can give a member a higher level than the one stored on their account. Your assistant sees both, and after changing a level it tells you which one is now in force.
  • Nothing reaches a member without your say-so. Resending a verification email refuses until the assistant confirms with you. Staff accounts are never touched.
  • Needs PageMotor 0.11.5.
  • Clearer help text for After Registration Redirect. The tooltip now says the setting takes a path on your site, such as /welcome/, and that it is also where members land after clicking their verification link. It used to ask for a URL, but the setting expects a path.
  • Fix for sites installed in a subfolder (for example example.com/site/): the sitewide gate no longer hides the log-in form. With a Sitewide Required Level set, the log-in and registration pages are meant to stay open to everyone, along with anything listed under Public Paths. On a subfolder site none of them were recognised, so the log-in page showed the “please log in” message instead of the form, and its link led straight back to the same page. Members could not sign in from your site. These pages are now recognised wherever the site is installed.
  • Sites installed at the top of their domain are unchanged.
  • Security fix: saving a member in PageMotor’s Manage Users can no longer make them an administrator. PageMotor 0.11 no longer lets plugins add user types, so members were stored as a type it does not list. Manage Users showed their type as blank, and the Edit User screen’s type menu fell back to Administrator, so clicking Save User on a member would have made them an administrator. On PageMotor 0.11, members are now stored as PageMotor’s own User type, which cannot use the admin. Edit User shows them as User, and saving keeps them a User. Reported by mikozoid.
  • Existing members are switched over automatically the next time an administrator opens any admin page, before Edit User can show them. Their level, language, verification status and display name are kept. Member accounts created by EP Ecommerce for buyers are switched over the same way.
  • Members still log in, verify and appear in the Members panel exactly as before. Ordinary User accounts that were not created as members are left alone.
  • Nothing changes on PageMotor 0.10, which still lists the member type.
  • The link in the verification email now verifies the account. Clicking it opened the registration page with an empty form and left the account unverified, so the member was then turned away at the log-in page with “Please verify your email address first”. The link now marks the address as verified, signs the member in and takes them to your Registration Redirect page. A link that has already been used, or has expired, now says so instead of showing an empty form. Reported by mikozoid.
  • The password-reset link had the same fault and now works. It opened the normal log-in form instead of the form for choosing a new password.
  • Password-reset links no longer arrive already expired on servers where the database clock is set to a different time zone from PHP. The one-hour link was checked against the database’s clock but written in PHP’s, so a database an hour ahead made every link expired on arrival.
  • Members left without a working link can get a new one. A member who registered while email verification was switched on was left unverified, holding a link that has since expired, and could not register again because their address was already taken. When they log in at your log-in page with the right password, they are now sent a fresh verification link and told to check their inbox. An account never holds more than three unused links at once, and each lasts 24 hours, so no inbox gets more than three a day.
  • Email verification now also applies to PageMotor’s own log-in at /admin/. A member who had not verified could sign in there and be taken to their profile page. They are now signed out on the next page they open, whichever page that is.
  • If email verification is switched off, the only change you will see is the working password-reset link.
  • Security fix: “Hide the content” now hides it. The setting “When a Gate Names a Level That Does Not Exist” is meant to keep a page hidden when its level has been renamed or mistyped. Until now it only applied to other plugins asking EP Membership; a page’s own Required Level, the Sitewide Required Level and [ep-level-gate] blocks still showed their content to everyone. With “Hide the content” chosen they now show the log-in or upgrade prompt instead, and site admins still see the content. With the default (“Show the content”) nothing changes.
  • Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
  • Section status. Each settings section shows whether that feature is switched on. On a site that also runs an older EP plugin, the section shows its plain title instead.
  • A password-reset, welcome or verification email that fails to send is now recorded in the PHP error log. Until now the result of the send was thrown away, so a site could show “check your email”, write the reset token and log the request while nothing had left the server. Nothing else changed in how the emails are sent.
  • Pair this with EP Email 1.10.57, which fixes the cause on sites using Mailgun, Brevo or the ElmsPark relay: depending on plugin activation order, emails sent while the page was loading could fall back to the server’s own mail program instead of the configured service.
  • Fixes a crash on the registration and login forms when an older EP plugin is installed on the same site. Submitting the form returned an internal error and the sign-up or sign-in failed. EP plugins share one common code library, and whichever copy loads first is the one every EP plugin on that site uses, so a single out-of-date plugin could leave this one calling a spam check its copy did not have. The check now carries its own fallback and no longer depends on another plugin being up to date.
  • No change on a site where this never happened: the same spam check runs, and nothing else changed.

9 September 2026. The Log out control is now a button, not a link, and you should update.

The Log out control is now a proper button.

The Log out control on your profile page, on your login page and anywhere you have used the [ep-logout-link] shortcode is now a form with a button, which nothing can trigger by accident. It is styled to look exactly as it did before, so your pages should not change visibly.

Nothing you have already written breaks. If you hand-wrote a Log out link in your own page content, it still works. It now opens a short “Are you sure you want to log out?” page with a single button, rather than signing the member out on the spot.

Two smaller fixes in the same release. The shortcode’s redirect option, for sending a member to a particular page after they sign out, now works, having been silently ignored until now; it and the After Logout Redirect setting both accept pages on your own site only. And [ep-logout-link] now shows nothing at all to a visitor who is not signed in, instead of a link that did nothing.

7 September 2026. A gate naming an undefined level can now fail closed. Fail-open remains the default; the new setting under Member Levels lets a site choose to hide the content instead. Logged either way.

27 August 2026. PageMotor 0.11.2 compatibility: update this plugin before or with the core update. Members Only documents now work with 0.11.2, and a refused visitor sees the login prompt while a below-level member sees an upgrade prompt naming the required level.

26 August 2026. Transactional email falls back to PageMotor’s own mailer (0.11+) when EP Email is absent, with sends attributed in core’s email log. Previously those sends failed silently to the PHP error log.

24 August 2026. The Members Only content type: standalone documents kept private to members across your whole site, not just on the page itself.

For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.

For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.