Ignition Crowdfunding v0.12.0

This release introduces a new Payments settings tab where every payment gateway lives — the offline method ships as the seed gateway, and future add-ons (Stripe, PayPal, etc.) register themselves through a stable public API and appear alongside it with the same listing, status badges, and instant enable/disable behavior. Two new wp-admin screens — Backers and Creators — summarize who is pledging and who is raising across the whole site, with per-user detail pages. Administrators now also receive transactional emails when campaigns are submitted for review, go live, hit their goal, or end — and can opt into a notification on every new pledge.

New Features

• Payments settings tab — A new Payments tab in Ignition → Settings lists every registered payment gateway with a status badge, enabled checkbox, and per-gateway Configure link. The Offline gateway is seeded by Core and ships enabled; future gateway add-ons appear in the same listing. Enabling and disabling happens instantly via AJAX without a full page reload. Sub-pages at ?gateway={id} host each gateway’s own settings — the offline payment instructions editor has moved from the General tab to Payments → Offline. See Payments.
• Admin user-summary pages — Two new wp-admin screens, Ignition → Backers and Ignition → Creators, give administrators a site-wide view of pledging and campaign activity per user. The Backers list shows total pledged, total paid, distinct campaigns backed, and last pledge date, with All / Registered / Guest / Unverified filter views. The Creators list shows total campaigns, total raised, backers reached, and last campaign created, with All / Active / Inactive / Unverified filters. Each row links to a detail page that pivots the user’s pledges or campaigns by status. See User summaries.
• Admin email notifications — Administrators now receive transactional notifications at key moments in the campaign lifecycle. Three new notification categories — New campaigns awaiting review, Campaign lifecycle (admin digest), and Every new pledge — bundle six new emails: Campaign Pending Review, Campaign Live, Goal Reached, Campaign Succeeded, Campaign Failed, and New Pledge. The first two categories are on by default; the per-pledge notification is off by default so high-volume sites can opt in deliberately. Admins manage their personal preferences from the Crowdfunding Notifications section on their WordPress Profile page. See Email notifications — Admin emails.

Improvements

• Currency setting moved to Setup — The site currency dropdown now lives on the Setup tab alongside the other one-time configuration items, freeing the General tab for day-to-day toggles. See Settings — Setup.
• Offline payment instructions moved to Payments → Offline — The rich-text instructions shown to backers after pledging now live on the per-gateway Offline sub-page rather than in the General tab. Existing instructions are preserved unchanged.

Developer

• Payment gateway extension API — Add-on authors can now register payment gateways through a stable public API. Implement the new Igcf_Payment_Gateway abstract class, hook the new igcf_register_payment_gateways action, and call igcf_register_payment_gateway( new My_Gateway() ). Each gateway exposes get_id(), get_label(), is_configured(), and register_settings_fields(). Once registered, the gateway appears in the Payments tab listing and gets a sub-page with its own Settings API form for free. See Registering a payment gateway and Service Layer — Payment gateways.
• New action igcf_checkout_after_pledge_create — Fires after a pledge has been successfully created in Igcf_Checkout::handle_post_submission(), immediately before Core’s default redirect to the receipt. Async-redirect gateway add-ons (Stripe Checkout, PayPal approval URLs) listen here and call wp_safe_redirect() to take over the post-pledge response. Parameters: $pledge_id, $campaign_id, $payment_method. See Actions Reference — Checkout.
• New filter igcf_checkout_payment_method — Gateway add-ons hook this filter inside handle_post_submission() to claim the payment method from the backer’s checkout POST. Returns the gateway id Core should record on the new pledge. Parameters: $payment_method, $_POST, $campaign_id. See Filters Reference — Checkout. The pre-0.12.0 action hook of the same name (a UI render hook) has been removed; gateway UI now flows through Igcf_Payment_Gateway::render_checkout_field().
• New action igcf_register_payment_gateways — Fired by Igcf_Payment_Gateway_Registry::register_core_gateways() on init priority 5, immediately after Core seeds the Offline gateway. The single parameter is the registry instance. Add-ons hook here to register their own gateways via igcf_register_payment_gateway(). See Actions Reference — Payment gateways.
• New action igcf_payment_gateway_state_changed — Fires after Igcf_Payment_Gateway_Service::set_enabled() successfully writes a new enable/disable state. Parameters: $gateway_id, $enabled (bool). Useful for cache busting or for add-ons that ship companion features that should follow the gateway’s enabled state. See Actions Reference — Payment gateways.
• New ability igcf/set-payment-gateway-enabled — A WordPress Abilities API endpoint under the new igcf-payments category, called by the Payments tab’s instant-toggle UI. Input: { gateway_id, enabled }; output: { gateway_id, enabled, message }. Permission: edit_others_igcf_campaigns. See Abilities Reference — Payment gateways.
• New service Igcf_Payment_Gateway_Service — Single source of truth for reading and writing gateway enable/disable state. is_enabled(), get_enabled_ids(), get_enabled_gateways(), get_lock_reason(), get_status(), and set_enabled(). The set_enabled() writer enforces guards for unknown ids, unconfigured gateways, and the last-enabled gateway. See Service Layer — Igcf_Payment_Gateway_Service.
• New services Igcf_Backer_Service and Igcf_Creator_Service — Power the new admin user-summary pages. Each exposes query_paginated( $args ) for the list view (search, filter, orderby allowlist, pagination, status pivot) and get_aggregates_for_user( $user_id ) for the detail view. Both exclude test-campaign data so the dashboards stay honest. See Service Layer — Igcf_Backer_Service and Igcf_Creator_Service.
• New method Igcf_Pledge_Service::get_payment_method_stats() — Aggregates pledge count and amount sitewide grouped by payment_method, excluding cancelled pledges. Drives the Pledges column on the Payments tab listing. See Service Layer — Igcf_Pledge_Service.
• New capability igcf_view_user_summaries — Gates access to the Backers and Creators wp-admin screens and to the user-summary links that now appear inside the admin Pledges and Campaigns list tables. Granted to Administrator on activation; revoked on deactivation. See User Roles — Administrator.