AmbassadorHub
| 开发者 | trybes |
|---|---|
| 更新时间 | 2026年11月4日 22:04 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
AmbassadorHub is a peer-to-peer fundraising platform plugin for WordPress. It provides everything you need to run ambassador-led fundraising campaigns:
- Accounts — Ambassador role, email verification, custom profile fields, frontend portal
- Campaigns — Campaign custom post type with lifecycle management
- Fundraisers — Individual and nested (team) fundraiser pages, with a shared team total
- Donations — Donation tracking, donor deduplication, and GDPR anonymization
- Payment Connectors — Built-in Stripe and PayPal PSP connectors
- Consent — Privacy-policy and marketing-consent checkboxes, WP Privacy API export/erasure support
- REST API — Full REST API under
ambassadorhub/v1
安装:
- Upload the
ambassadorhubfolder to/wp-content/plugins/. - Activate the plugin through the Plugins menu in WordPress.
- Navigate to AmbassadorHub → Settings to configure the plugin.
- Enable and configure a payment connector under Settings → Payments.
屏幕截图:
常见问题:
Does this plugin require WooCommerce?
No. The plugin uses Action Scheduler (bundled) for background jobs, but does not depend on WooCommerce itself.
Can I use both Stripe and PayPal at the same time?
Only one PSP can be active at a time. You can configure both but select the active one under Settings → Payments.
Where do ambassadors log in?
Ambassadors use a frontend portal block (not wp-admin). Add the Account block to any page to create the ambassador dashboard.
更新日志:
1.2.1
- Fixed: team leaders could still invite members to a team that had ended, or whose fundraiser had ended or passed its end date. The "Invite member" option is now hidden for these teams, and the site refuses the invitation.
- Fixed: opening an invitation to a team that has ended now says straight away that the team no longer accepts new members, instead of first asking the visitor to sign up or log in. The invitation is no longer used up when joining is refused.
- Fixed: when you created a group right after creating a fundraiser, the group got the fundraiser's picture. The group form now starts with an empty image field.
- Fixed: the "Create a group" form shown after creating a fundraiser could not be submitted, because its button stayed disabled.
- Ambassadors can log out from their account page.
- Added "Forgot password?" to the login form. It uses WordPress's own password reset and then returns the ambassador to the login page.
- Ambassadors can change their password in the Profile tab. Changing it logs out their other devices.
- The ambassador password rules now also apply when resetting a password.
- The WordPress toolbar is no longer shown to ambassadors on the site.
- Only ambassadors can create fundraiser pages. Other logged-in users see an explanation instead of the form.
- Fixed: team leaders could not remove members from their team.
- Fixed: opening a team invite while logged in as an administrator or editor changed that account into an ambassador account, which locked it out of the dashboard. Subscribers and customers still become ambassadors when they accept an invite. Invites to teams that have ended are now refused.
- A page created from a team invite is published once the ambassador confirms their email address, like any other new page.
- Fixed duplicate emails: "Your fundraiser is live" arrived twice after joining a team, each edit sent two "edited" emails, publishing a page also sent an "edited" email, and new invitees got two verification emails.
- Fixed a server error when an email verification link arrived without its user ID.
- Fixed: after activating the plugin, fundraiser page addresses could show "Page not found" until the permalinks were saved again.
- Fixed: when the plugin was activated with WP-CLI, fundraiser pages logged database errors until someone opened wp-admin.
- Fixed: add-on fields did not appear in the form when an ambassador started a new fundraiser.
- Fixed: the "Minimum Target Amount" setting was ignored, so ambassadors could set any target. It now applies when an ambassador sets or changes a target. Set it to 0 for no minimum.
- Deleting the plugin now also removes its spam protection, fundraiser and setup wizard settings.
- The account page now works on sites installed in a subfolder and with plain permalinks.
- The login form fields are now labelled for screen readers and password managers.
- Smaller download: the plugin zip no longer includes the Plugin Directory banners and screenshots, or AI assistant instruction files bundled by a third-party library.
- Categories for fundraisers, and for petitions when the AmbassadorHub Petitions add-on is active. Add them under AmbassadorHub → Categories, and choose them for a fundraiser or petition in the editor. When there is at least one category and ambassadors are allowed to start new fundraisers, they choose categories when they start one, and can change them later. Team pages, personal pages and sub-petitions get the categories of the fundraiser or petition they belong to. Category pages and category counts show each fundraiser or petition once, without its team and personal pages.
- Developers: new
ambh_account_password_changedaction. Thenamespacekey was removed from theambhConstantsscript data; userestUrlinstead. Categories use the newambh_categorytaxonomy; add your own post types with theambh_category_post_typesfilter. Category pages list only top-level actions; return false from the newambh_category_archive_top_level_onlyfilter to also list sub-pages. The fundraiser REST endpoints accept and returncategories.
- Security: removed the public REST endpoints for creating donations (
POST /ambassadorhub/v1/donationsandPOST /ambassadorhub/v1/fundraisers/{id}/donations) and the public donation list (GET /ambassadorhub/v1/fundraisers/{id}/donations). They skipped the spam protection of the donation form, and nothing in the plugin used them. Visitors donate through the Donation Form block, as before. - Privacy: the marketing-consent checkbox on the signup and donation forms is now optional. Visitors can sign up or donate without agreeing to marketing email, and consent is only recorded when they tick the box. The privacy-policy checkbox is still required.
- Fixed: the marketing-consent checkbox on the signup form was stretched to full width, with its label pushed below it.
- Developers: the
ambh_donation_rest_savedaction and theambh_donation_create_paramsfilter no longer fire, because the endpoints that triggered them are gone.
- Redesigned the frontend ambassador account dashboard: fundraisers and petitions now share one unified "My Actions" grid, filterable by type (Fundraisers, Petitions, Groups, Personal pages), instead of separate per-module sections.
- Added a single "+ New action" menu for starting a new fundraiser, team, or petition, replacing the separate "+ Start a..." buttons each module previously rendered on its own.
- KPI/stat tiles now stay visible on both the Dashboard and Profile tabs instead of disappearing when switching away from Dashboard.
- Added
ambh_account_dashboard_stats,ambh_account_dashboard_actions, andambh_account_dashboard_create_actionshooks so add-ons (Petitions, Premium) can plug into the new stats row, actions grid, and create-action menu. The genericambh_account_dashboardhook remains for backwards compatibility with existing integrations.
- First stable release — AmbassadorHub is now available directly from the WordPress.org Plugin Directory.
- Added built-in spam protection for the public signup, donation, and team-invite forms: an invisible honeypot field, a submission-timing check, per-visitor rate limiting, a disposable/blocked-email-domain filter, and a link-count filter on the donation message field. Every check runs entirely on this site — no CAPTCHA provider, no external service, nothing sent off-site — and is configurable (including fully disabled) from the new Settings → Spam Protection tab, which also shows a log of recently blocked attempts.
- Added a per-account daily cap on team-member invitations, closing a gap where the existing per-team hourly limit could be bypassed by repeatedly creating new teams.