PP Verified Users

Verification requests, review workflow, and verified badges for PeoplePress communities.

This area is still changing. Steps and screenshots may lag behind the current release.

PP Verified Users adds a verification workflow to a PeoplePress community: a member requests verification, a moderator reviews the request, and an approved member displays a badge on their profile.

It is an addon, so it requires PeoplePress core. It registers itself as a module against the core lifecycle, which is why its screens behave like core screens rather than a bolted-on settings page.

Vocabulary

These terms are used consistently across every page in this section:

  • Verification request — what a member submits.
  • Review — what a moderator does to a request: approve or reject.
  • Verified badge — what an approved member displays.

TODO(verify): whether the plugin supports multiple named verification types, and what the admin UI calls them. Confirm against the data layer in src/ before promoting this page.

Requirements

FieldValue
Version1.0.0
Requires PHP7.4
RequiresPeoplePress core
Text domainpp-verified-users

How it loads

The plugin boots on the pp_register_modules action, which core fires on plugins_loaded at priority 10100. That is the supported hook for third-party module registration: by the time it runs, core has booted and the module registry exists.

The practical consequence is ordering. If PeoplePress core is not active, the addon registers nothing at all rather than failing loudly — so a site with the addon active and core deactivated will simply have no verification features.

Source: pp-verified-users.php

Uninstalling

Deleting the plugin from the WordPress admin runs uninstall.php, which drops the plugin's tables and removes its options. Deactivation does not. Verification data does not survive deletion, so export anything you need first.

Source: uninstall.php

Pages planned for this section

Installation, configuration, managing verification types, reviewing requests, requesting verification as a member, and the developer reference. See data/topics.yml for the source files each one must be written from.

On this page