Опис
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)
- Configurable access capability gating protected content — defaults to
read, which every logged-in WordPress user already has, so it works out of the box on any site - Editable, autocompleting protected page paths and protected post types lists — click either field to see every page/post type already on the site
- Editable member capabilities granted to the Portal Member role (and Administrator), for other plugins/theme code to check against
- A
Portal Memberrole, created automatically on activation [lapdi_member_account]shortcode for the account page- WordPress-native password recovery and nonce-protected logout
noindex,nofollowon account and protected front-end requests
Required framework
LAPDI Member Portal requires TSP Easy Dev to be installed and active. WordPress blocks activation until that dependency is available and active.
Works with LAPDI Events
If LAPDI Events is also active, its “Members only” event visibility automatically defers to this plugin’s configured access capability — no extra setup required.
Встановлення
- Install and activate TSP Easy Dev.
- Upload the plugin under Plugins Add New Upload Plugin and activate it.
- Activation creates the
Portal Memberrole and creates (or fills, if empty) an Account page containing[lapdi_member_account]. - Open LAPDI Plugins Member Portal to review or change the access capability, protected page paths, protected post types, and member capabilities — all editable from that screen.
- Confirm the protected paths/post types match your site’s actual structure; the settings screen lists everything currently on the site to choose from.
Часті питання
-
Do I need to create a custom role or capability myself?
-
No. The plugin creates a
Portal Memberrole automatically and grants it a safe default (read) for protected-content access. Only change the access capability if your site already has its own membership capability you’d rather gate on instead. -
How do I protect an additional page or post type?
-
Open LAPDI Plugins Member Portal, 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. WordPress includes those core account fields in its personal-data export and erasure tools. Member Portal stores site-wide access settings, an account page ID, and role capabilities, but it does not create a separate profile-data table or send profile data to an external service.
-
What happens when I delete the plugin?
-
Permanent deletion removes the Portal Member role, Member Portal settings, and plugin-owned capabilities. Users whose only role was Portal Member 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.
Відгуки
Для цього плагіна немає відгуків.
Учасники та розробники
“LAPDI Member Portal” — проект з відкритим вихідним кодом. В розвиток плагіну внесли свій вклад наступні учасники:
Учасники
Перекладіть “LAPDI Member Portal” на вашу мову.
Цікавитесь розробкою?
Перегляньте код, перегляньте сховище SVN або підпишіться на журнал розробки за допомогою RSS.
Журнал змін
1.0.0
- Add the WordPress.org View details link to the Plugins screen.
- Initial general release. Configurable access capability (defaults to universal
readinstead of a site-specific capability name), generic role/capability naming, editable settings screen with autocomplete for protected paths/post types/capabilities. - Require TSP Easy Dev 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.