Description
LAPDI Member Portal gates protected pages, post types and other plugins’ member-only content to logged-in users, and gives members a self-service front-end account page. It ships with sensible, universal defaults and is fully configurable from its own settings screen — nothing is hardcoded to any one site’s setup.
Features
- A front-end account/login page with a nonce-protected profile form (first name, last name, display name, email)
- Any number of member roles, each with independent access settings
- Renameable
Portal Memberand full-accessPortal Board Memberstarter roles - Users → Assign Roles: select any number of members and add or remove a member role in one action
- Users → Member Roles: create, rename, delete, and configure roles — access capability, protected page paths, protected post types, member capabilities, and the welcome-email template
[lapdi_portal_role]conditional content, including nested third-party shortcodes[lapdi_member_account]shortcode for the account page- WordPress-native password recovery and nonce-protected logout
noindex,nofollowon account and protected front-end requests- Protected content excluded from unauthorized REST API requests, search, feeds, and public XML sitemaps
- An account-page extension action for independently maintained membership and billing integrations
- Optional site-owned presentation for WordPress account and password emails
- No required framework — Member Portal registers its own screens directly, nothing else to install first
Works with LAPDI Events
If LAPDI Events is also active, its “Members only” event visibility automatically recognizes users assigned to any configured portal role — no extra setup required.
Installation
- Upload the plugin under Plugins → Add New → Upload Plugin and activate it.
- Activation creates the
Portal MemberandPortal Board Memberstarter roles and creates (or fills, if empty) an Account page containing[lapdi_member_account]. - Open Users → Member Roles to add, rename, or delete roles and configure each one.
- Open Users → Assign Roles to select members and assign them a role.
- Confirm the protected paths/post types match your site’s actual structure; the Member Roles screen lists everything currently on the site to choose from.
FAQ
Do I need to create a custom role or capability myself?
No. The plugin creates Portal Member and Portal Board Member starter roles automatically. You can rename either role or create more roles from Users → Member Roles.
How do I protect an additional page or post type?
Open Users → Member Roles, select the role, and add the page slug or post type in the relevant field — start typing or click into the field to see suggestions drawn from your site’s actual pages/post types.
What personal data does the plugin store?
The account form updates the current user’s standard WordPress first name, last name, display name and email fields. Member Portal does not own registration, payment, learning tiers, or application review. Independent integrations may add account sections through the documented action without moving their durable records into Member Portal.
What happens when I delete the plugin?
Permanent deletion removes all plugin-created portal roles, Member Portal settings, and plugin-managed capabilities. Users whose only role was a portal role receive the site’s default role so they are not left roleless. The Account page and standard WordPress user profile fields are preserved because they may contain administrator-authored content or user-owned data. Ordinary deactivation does not remove anything.
Changelog
1.2.0
- Expand Assign Roles from this plugin’s own member roles to every role registered on the site, grouped by the plugin that governs it: WordPress core, LAPDI Member Portal, or Other when that can’t be determined.
- Add the
lapdi_portal_role_group_mapfilter so another plugin can claim its own roles on the Assign Roles screen instead of falling under “Other”. - Allow a member to hold more than one role at a time, matching how WordPress itself works: adding a role no longer clears any other role the member already has, and removing a role only removes that one role.
- Protect the Administrator role from being removed from user ID 1 or from the site’s last remaining administrator, including across a bulk removal of several administrators at once.
- Member Roles is unchanged in scope: it still only configures the roles this plugin created.
1.1.0
- Drop the LAPDI Easy Dev Framework dependency entirely — Member Portal now registers its own admin screens and no longer requires another plugin to be installed first.
- Move the admin interface from its own “LAPDI Plugins” menu to Users → Assign Roles and Users → Member Roles.
- Add bulk role assignment: select any number of members and add or remove a role in one action, instead of one member at a time.
- Rename “portal role” to “member role” throughout the admin interface for clarity; internal role IDs and data are unchanged.
- Add an optional transactional email wrapper selected by WordPress content ID, with native plain-text account emails preserved when none is configured.
- Add the
lapdi_member_portal_account_sectionsaction for independently owned account integrations. - Prevent unauthorized discovery of protected pages and post types through the REST API, REST search, public search, feeds, and XML sitemaps, while preserving role-specific access for authorized members and administrators.
- Allow deleting a role from the admin interface and fix the role-conditional shortcode name.
1.0.0
- Add the WordPress.org View details link to the Plugins screen.
- Initial general release with unlimited, renameable portal roles and independent access settings.
- Add full-access roles, portal role assignment for users, and role-conditional page content with
[lapdi_portal_role]. - Preserve word boundaries in custom role IDs and migrate role IDs created by the earlier 1.0.0 builder.
- Add configurable capabilities and editable settings with autocomplete for allowed paths, post types, and capabilities.
- Require LAPDI Easy Dev Framework through WordPress’s native dependency header and path-independent runtime detection.
- Keep the account interface theme-independent and document use of WordPress core profile data.
- Internationalize and contextually escape the Member Portal administration interface.
- Clean up the Portal Member role, plugin-owned capabilities, and settings safely when the plugin is deleted.
