Ignition Crowdfunding v0.15.0

This release adds an Add-ons tab to Settings for discovering and downloading extensions, and tightens the rejection workflow: a reason is now required whenever an administrator rejects a campaign or an update, and creators are notified — with that feedback — when one of their updates is turned down.

New Features

• Add-ons tab — A new read-only Add-ons tab in Ignition > Settings lists the add-ons that extend Ignition Crowdfunding, shows which ones you have installed and whether they are active, and links you to download or update each one. Installing and activating still happens on the WordPress Plugins screen — the tab is a discovery surface. See Add-ons.
• Update rejection feedback — When an administrator rejects a campaign update, the creator is now notified by email and sees the reviewer’s feedback when they open the update to edit it. Saving the edited update resubmits it automatically — back to review if your site moderates updates, or straight to published if it doesn’t. See Campaign Updates — Rejected updates and Email Notifications.

Enhancements

• Rejection reason now required — Rejecting a campaign or an update now requires a reason, so the creator always receives an explanation of what needs to change. The reason is recorded in the status history and shown to the creator. See Reviewing submissions.

Developer

• Rejection abilities require a reason — igcf/reject-campaign and igcf/reject-update now require a non-empty reason parameter and return a 400 error when it is missing or blank. See the Abilities Reference.
• New overridable email template — The update-rejected creator notification renders from emails/update-rejected.php, which you can override from your theme like any other email. See Template Overrides.