Member accounts
Registration, sign-in and profiles as a first-class collection that relates to your content.
Add a members layer to any project, accounts, comments, profiles and moderation, without standing up a second system to keep in sync. Scoped, rate-limited and API-first.
Every capability integrates with permissions, validation, migrations and the headless API. Nothing bolted on the side.
Registration, sign-in and profiles as a first-class collection that relates to your content.
Attach discussions to any entry. Submissions run through validation and an optional queue.
A moderation queue with spam scoring. Approve, reject or ban from the admin or the API.
Member tokens are sandboxed, they can never reach your editorial collections.
Likes, public profiles and activity feeds, all related to your existing content.
Every community feature is reachable over the module's AJAX endpoints, authenticated with a member token.
Members authenticate with their own scoped tokens. The module adds its features as actions on the core hook system, so every submission runs validation before it touches the database, with moderation built in.
Member tokens reach community actions only, never your editorial content.
Validation and length limits on every submission, with optional review.
Actions hook into the same permission and validation layer as everything else.
// the module registers an action on the core hook system
add_action('community_post_comment', function () {
$member = get_current_user(); // the signed-in member
$entry = (int) ($_POST['entry_id'] ?? 0);
$body = trim((string) ($_POST['body'] ?? ''));
// validate, store, then return JSON
echo json_encode(['success' => true, 'data' => ['id' => 9]]);
});{
"success": true,
"data": {
"id": 9,
"author": "Sam R.",
"body": "Great write-up.",
"status": "approved"
}
}Self-service registration, profiles and account management.
Nested comments on any collection, with validation.
Spam scoring, approval flows and ban controls.
Scoped REST endpoints for every feature.
Full documentation. Installation, configuration, every option and the API reference live in the Community module docs. Building your own instead? Read building a module.
Drop it in public/modules, activate it in the admin Modules screen, and its migrations run on activation. Reviewed, supported, and free to self-host.