Network Pending Users Manager
| 开发者 | enricomarogna |
|---|---|
| 更新时间 | 2026年9月9日 19:01 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Network Pending Users Manager helps super admins manage pending signups (
wp_signups) in WordPress Multisite from a dedicated interface in Network Admin.
It is designed for multisite operators who need a practical workflow to inspect signups, resend activation emails, regenerate activation links, activate accounts manually, delete signup entries, and keep traceability with logs.
Key features
- List and filter pending users from signup records (
wp_signups). - Resend activation email.
- Regenerate activation link.
- Activate signup directly from Network Admin.
- Delete signup entries.
- Copy/Open activation links from row actions.
- Logs and retention settings for operational history.
- Diagnostics tab with basic status information.
- This plugin works only on WordPress Multisite.
- If your mail stack is misconfigured, the “Resend” action can complete without actual message delivery.
- The plugin does not send data to external services. Optional logs are stored locally and may include the performing administrator and IP address.
安装:
- Upload the plugin folder to
/wp-content/plugins/. - Go to My Sites → Network Admin → Plugins.
- Activate Network Pending Users Manager with Network Activate.
- Open Network Admin → Users → Pending Users.
常见问题:
Where can I find pending users?
Go to Network Admin → Users → Pending Users.
Why are activation emails not received?
The plugin triggers WordPress email functions, but delivery depends on server mail configuration (or SMTP plugin/service). Check SMTP setup, sender reputation, and mail provider/server logs.
Does this plugin work on single-site WordPress?
No. It is intended for Multisite only.
Does this plugin send data to external services?
No. All processing stays on your WordPress Multisite. If logs are enabled, action history is stored in a local database table.
更新日志:
1.0.5
- Plugin Check: prepared SQL identifiers, prefixed uninstall variables, and admin notices without query-string messages.
- Diagnostics no longer invoke core mail filters; list/export queries use table placeholders.
- WordPress.org compliance: unique NPUM prefix, local-only assets, English source strings, and at most five readme tags.
- Security: escape on output, sanitize individual request fields, and migrate legacy npu_* options/table.
- Compatibility: requires WordPress 6.2+ (table identifier placeholders) and tested up to WordPress 7.1.
- Security hardening: improved output escaping in Network Admin pages.
- i18n: added translators comments for strings with placeholders and improved handling of translatable strings containing HTML.
- Maintenance tweaks for WordPress.org Plugin Check/PHPCS compliance.
- Documentation and packaging metadata improvements for WordPress.org readiness.