Fenton Digital Badges
| 开发者 | Steve_Fenton |
|---|---|
| 更新时间 | 2026年7月20日 20:42 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Configure an issuing organization
- Create badges
- Issue badges, with email notifications to the recipient
- Public attestation pages show the badge and links to share it
- Admin views over the list of badges, assertions, and basic statistics
/wp-admin/site-editor.php?p=%2Ftemplate on your site.
- Click "Add Template"
- Select "Single item: Badge" or "Archive: Badge"
/badges/assertion/{uid}/, create a Page, optionally add [fendigibadge_attestation], then choose that page under Badges → Settings. Edit the page’s template in the Site Editor. Themes can also override the markup with fendigibadge/attestation.php.
Shortcodes
[fendigibadge_attestation]— certificate markup on/badges/assertion/{uid}/when using a page template
- Issuer JSON:
/ob/issuer.json - Badge class JSON:
/ob/badges/{id}.json - Assertion JSON:
/ob/assertions/{uid}.json - Attestation page:
/badges/assertion/{uid}/ - Claim name:
/badges/claim-name/{token}/ - Unsubscribe:
/badges/unsubscribe/{token}/
安装:
- Upload the plugin files to
/wp-content/plugins/fenton-digital-badges, or install the ZIP via Plugins → Add New → Upload Plugin. - Activate Fenton Digital Badges through the Plugins screen.
- Go to Badges → Settings and configure your issuing organization (name and website URL are required).
- Create a badge under Badges → Add New (featured image and criteria URL required).
- Use Badges → Issue Badges to award badges from a CSV.
屏幕截图:
常见问题:
What CSV format is required?
Columns: email (required), name, evidence, expires (YYYY-MM-DD). A header row is optional — a single line like you@example.com,Your Name works.
Are recipient emails stored?
No, not on assertions. Emails are salted and hashed for the assertion identity and looked up via a separate HMAC. The only plaintext emails kept are addresses that opted out of badge notifications via the unsubscribe link.
How does an earner add their name to a badge?
If a badge is issued without a name, the issue email includes a one-time link to add it. The link asks the earner to confirm the name before saving, then stops working. The attestation page still verifies the badge even if no name is ever added, showing a generic completion message instead.
How do I stop badge notification emails?
Each issue email ends with a “Stop all future notifications” link. Using it adds that address to an unsubscribe list (only when the address still matches at least one badge). Later issue notifications for that address are ignored.
Does this support Open Badges 2.0 / 3.0?
This release implements Open Badges 1.0 JSON endpoints and assertions.
更新日志:
- Added assertion filters to Badges → Assertions — filter by badge type, search by recipient email (hashed lookup; no email is sent or stored), and choose items per page.
- Added Badges → Stats with issued, claimed, and claimed % summary boxes and a per–badge-type breakdown table.
- Removed the public "find my badges" email lookup form and its
/badges/find/endpoint,[fendigibadge_find]shortcode, and Find badges page setting. This was the only public, unauthenticated endpoint that could trigger an email; badge notification emails are now only sent when a WordPress user issues a badge. The one-time name-claim link and unsubscribe link are unaffected. - Added an Earn URL field to badges (the page where someone can go to earn the badge). It's shown as a link wherever
[fendigibadge]renders the badge, and as a button on the public attestation page.
- Tightened find-badges rate limits: 8 submissions per IP per 10 minutes, and one lookup per email every 30 minutes.
- Find-badges emails include a secure “Stop all future notifications” unsubscribe link.
- Unsubscribed addresses are ignored before email lookup hashing.
- Find-badges emails include a one-time link to add a missing recipient name, with confirm-before-save.
- Renamed internal prefixes to
fendigibadgefor WordPress.org plugin review compliance.
- Initial public release candidate for the WordPress.org plugin directory.