| 开发者 | jtayler |
|---|---|
| 更新时间 | 2026年7月19日 19:53 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[truanon] shortcode, the [truanon_card] profile card, or the Badge block[truanon_settings] places the member panel on any front-end page for membership sites--truanon-*) a theme can override.
UsersWP works out of the box — the badge appears on member profiles and in the members directory, and the member's Verify / Manage control appears on their own profile, no snippet. BuddyPress and others take a one-line snippet to place the badge, plus the [truanon_settings] panel for member controls. See "Using it with a membership plugin" above. On a standard WordPress site nothing is needed; badges appear on their own.
Anchor once. They tap Verify on their profile, complete the connection in a TruAnon window, and they're done — the badge maintains itself from then on. Every visibility choice afterward is a switch they flip themselves.
Display is always theirs to revoke — one switch returns them to Unknown everywhere, immediately. The anchor itself is permanent; that permanence is what makes the badge worth reading.
Yes. The badge and card are bare, classed markup with CSS-variable colors and even CSS-generated separators — override --truanon-* variables or restyle any .truanon-* class from your theme. No templates to edit.
[truanon_verification] profile snippet, remove it after updating to avoid a duplicate badge.truanon_inline_manage; the module's badge placement is filterable via truanon_userswp_render_badge.[truanon_verification] alias now recognizes UsersWP members directories as well as BuddyPress, so member lists render the light inline check with no per-member API call; single profiles still get the full card.[truanon_settings] member panel, in the readme.[truanon_verification userid=".." username=".."] shortcode as an alias so existing 1.x/2.x placement snippets keep rendering after upgrade instead of printing the raw tag.size="inline|large|card" forces a specific piece.