Ignition Crowdfunding release notes

Ignition Crowdfunding v0.23.0

Fri, 30 Oct 2026 00:00:00 GMT

The person who sets a site up and the person who runs its fundraising are often different people. Until now the second one needed an administrator login, which also let them install plugins, manage users and change payment keys. This release adds operators: staff who approve campaigns, handle pledges and refunds and change business settings, without any of the administrator’s technical powers. The release also lets you close an ended campaign without declaring a result, and shows on each campaign’s page which payment methods it offers and why any are missing.

New Features

Operators — Tick Ignition operator on any user’s profile, or click Make operator on the Users list, and that person can run the fundraising from wp-admin: campaigns, pledges, refunds, backers, exports, staff emails, and the business settings under Ignition > Settings. They keep their WordPress role, and the Users list labels them Operator. Technical settings stay with administrators: payment methods and their keys, the offline payment instructions, page assignments, currency and the sender email address. Operators don’t see those at all, and the settings screen keeps them unchanged when an operator saves. See Administrators and Operators.
Close a campaign without declaring a result — On an ended campaign with no recorded outcome, the campaign’s page now offers Close beside Declare Result. Closing this way records no outcome and sends backers no outcome email. The confirmation box says so, and the status history notes Closed without a recorded outcome. See Declaring Campaign Results.
See why a payment method isn’t offered on a campaign — A campaign’s page in wp-admin has a new Payment methods row. It lists the methods checkout offers on that campaign, and for each enabled method that isn’t offered, every reason why. Administrators also get a link to where each problem can be fixed. The row reads from the same source as checkout, so the two always agree. See Payment methods.

Improvements

“Staff”, not “Admin” — Emails meant for the people running the site now go to administrators and operators alike, and say so: they carry (Staff) in their names on the Emails tab. The front-end Account → Notifications page has an Emails for staff group, so staff can switch them there as well as on their WordPress profile. See Notification preferences.
Settings shows operators only what they can change — An operator sees the General, Emails and Sharing tabs. The Add-ons tab appears only when an active add-on has settings an operator may change, and lists just those add-ons. See Add-ons.

Bug Fixes

Cancelling a pledge stops the payment going through — Cancelling a pending pledge left its payment attempt open underneath. A payment provider that captures later, such as PayPal, could still charge the backer after the pledge was cancelled. Cancelling now closes the attempt as well, and if it can’t, the cancel is refused rather than left half-done.
A campaign closed twice at once is recorded once — Two people closing the same campaign at the same moment, for example one on its page and one with the bulk Close action, each recorded a close. That meant two status-history entries and every closing email sent twice. The second close is now refused.
The campaign wizard keeps its Next and Back links — When the Dashboard page setting pointed at a page that had been deleted or unpublished, the campaign creation wizard showed its steps with no way to move between them. It now falls back to the page it is on.
Amount boxes match the currency — The refund amount box accepted any number of decimal places, and scrolling the mouse wheel over it changed the amount. The minimum and maximum pledge settings always stepped by 0.01. All three now follow the site currency’s decimal places, so yen step by 1 and a three-decimal currency steps by 0.001. Scrolling over the refund box no longer changes it.
Phone-width admin tables keep their column headers for screen readers — Below 601px, wp-admin tables that stack into labelled cards hid their header row from screen readers. Cell-by-cell table navigation now still announces each column.
The Payments list fits on a phone — Its status badge now wraps instead of pushing the table past the screen edge.
Uninstall removes the user-summaries permission — Uninstalling left the permission that opens the Backers screen behind on the Administrator role.

Developer

Three new permissions — igcf_staff, igcf_manage_settings and igcf_manage_campaign_terms are added at check time. The first two go to anyone with manage_options, the third to anyone with manage_categories, and all three go to operators. Core now checks these where it used to check manage_options. Campaign categories and tags use igcf_manage_campaign_terms. See Staff and operators.
Let operators change your add-on’s settings — Declare keys on igcf_operator_settings. Every key you don’t list stays administrator-only, enforced when the option is saved. An add-on that declares keys appears on an operator’s Add-ons tab. Igcf_Settings_Guard::can_edit( $option, $key ) tells a screen which fields to show. See Registering Add-on Settings.
Operator and staff helpers — Igcf_Operator::is_operator(), grant() and revoke(), with the igcf_operator_granted and igcf_operator_revoked actions, plus Igcf_Staff::get_users() and is_staff(). Use Igcf_Staff::get_users() rather than querying for administrators when you email or notify the people running the site.
Gateways say why they aren’t offered — Igcf_Payment_Gateway::get_unavailable_reasons( $campaign_id ) returns a list of code / message / fix_url reasons. Override it instead of is_available_for_campaign(), which now returns true exactly when that list is empty. Other plugins add reasons through igcf_gateway_unavailable_reasons. Igcf_Payment_Gateway_Service::explain_availability() returns the full result, and get_available_ids() is built from it. igcf_gateway_available_for_campaign still works, but new code should use the reasons filter. See Registering a Payment Gateway.
has_operator_settings() on gateways — Return true when your gateway’s screen has a field opened to operators. No shipped gateway does.
Payment switches are administrator-only — The igcf/set-payment-gateway-enabled ability now requires manage_options. Igcf_Payment_Gateway_Service::set_enabled() reports a save that didn’t take as igcf_gateway_save_failed (500), or as igcf_gateway_forbidden (403) when the settings guard held the caller back.
Igcf_Campaign_Service::close() — Closes an ended campaign and records whether a result had been declared. It is used by the close ability and the bulk action. A status change that loses a race with another one now returns igcf_campaign_status_conflict. See the Service Layer.
Focal-point permission narrowed — The focal-point REST route now accepts the image’s uploader, or someone with edit_others_igcf_campaigns for that campaign’s own images only. Previously, anyone who could edit the campaign and had edit_others_posts could pass any image in the media library.
igcf_money_step() — Returns a currency’s smallest step ("0.01", "1", "0.001") for a money field’s step and min. See Currency helpers.
New payment-attempt failure code — pledge_canceled, stamped on open attempts when their pledge is cancelled. See igcf_payment_attempt_failure_codes.

Ignition PayPal Gateway v0.6.0

Fri, 30 Oct 2026 00:00:00 GMT

When PayPal was missing from a campaign, all you could see was that it wasn’t there. With Ignition Crowdfunding 0.23.0 or later, the campaign’s page in wp-admin now lists every reason in plain language, with a link to the settings where the fix lives. This release also closes a gap where PayPal could still charge a pledge that had just been cancelled.

New Features

Every reason PayPal isn’t offered — A campaign’s payment methods in wp-admin explain why PayPal is hidden: fixed funding, missing Live or Sandbox credentials, missing Platform credentials or Account ID, or a creator who hasn’t connected or can’t be paid yet. Every reason is listed at once, not just the first. Messages name the creator and the environment. Credential reasons link administrators to the PayPal settings, and on a test campaign they say PayPal uses Sandbox. No saved credential is ever shown. Requires Ignition Crowdfunding 0.23.0 or later; on an older core, PayPal is offered or hidden exactly as before. See Why PayPal isn’t offered on a campaign.

Bug Fixes

A cancelled pledge could still be charged — If PayPal’s payment notification was already being handled when a pledge was cancelled, the payment could still be captured. A pledge that is no longer pending is now never captured.
Cancelling a pledge PayPal already paid — Cancelling a pending pledge whose PayPal payment had already gone through lost track of a real charge. That cancel is now refused with “This pledge may already have been paid at PayPal. Refund it instead of cancelling.” See Cancel or refund?.

Developer

Unavailability reasons — Igcf_Paypal_Gateway::get_unavailable_reasons() returns every reason PayPal can’t be offered on a campaign, and is_available_for_campaign() is now derived from it. Core 0.23.0 passes the list through igcf_gateway_unavailable_reasons with gateway id paypal. Igcf_Paypal_Platform::split_context() gains a reasons list. See Why PayPal is unavailable for the reason codes.
Cancel veto — The add-on answers core’s igcf_pledge_before_canceled with the WP_Error code igcf_pledge_payment_already_captured. See Blocking a cancel after payment.

Compatibility

Still runs on Ignition Crowdfunding 0.22.0 — The minimum core version is unchanged. The per-campaign explanations appear once you update core to 0.23.0.

Ignition Platform Mode v0.5.0

Fri, 30 Oct 2026 00:00:00 GMT

This release makes Platform Mode work for operators, the staff who run your fundraising without an administrator login. Operators can switch creator sign-ups and campaign moderation on or off, while who receives pledges stays with administrators. The campaign page in wp-admin now says when Offline is hidden because the creator has written no payment instructions. And a creator’s campaign count now splits into groups that always add up to the total.

New Features

Platform Mode for operators — Operators can change Public Campaign Creation and Campaign Moderation under Ignition → Settings → Add-ons → Platform Mode. Who Receives Pledges stays administrator-only: operators don’t see it, and saving the page as an operator leaves it unchanged. Staff are never treated as front-end-only creators, even if they also hold the creator role. On the payment-method screens, the line saying who receives pledges links to Platform Mode settings for administrators only. The Edit user link on the Creators list and on a creator’s detail page appears only to people allowed to edit that user. See Settings.
See why Offline isn’t offered — A campaign whose creator has written no offline payment instructions still hides Offline at checkout. Now the campaign’s payment methods in wp-admin say why and name the creator. See Offline hides itself until a creator can be paid.

Improvements

The creator stats line adds up — The line under a creator’s total campaigns used to split them into active, successful, failed and outcome pending only. Paused, not-started and closed campaigns counted toward the total but appeared in no group. The line now covers active, paused, not started, outcome pending, successful, failed, closed with no outcome, and in test mode. It lists only groups with at least one campaign, and they always add up to the total. See A creator’s detail page.
“Staff” instead of “admin” — Moderation emails and settings now say staff, because operators approve and review too. The moderation setting reads Require approval before campaigns go live, and the staff email is named Campaign pending review (Staff).
Screen-reader column headers — On narrow screens, the campaign table on a creator’s detail page stacks its cells and hides the column headers. They were hidden from screen readers too. They are now kept for screen readers, so each cell is still announced with its column name.

Developer

Operator settings — The add-on answers igcf_operator_settings for its own option, opening allow_public_campaign_creation and require_campaign_approval to operators. See Core money seams it answers.
Offline unavailability reason — The add-on now explains Offline through igcf_gateway_unavailable_reasons, with the reason code creator_offline_instructions_missing. It no longer uses igcf_gateway_available_for_campaign.
Staff are never creator-only — igcf_platform_is_creator_only_user now defaults to false for anyone with igcf_staff, not just manage_options. See the Platform Mode developer reference.
More campaign groups in creator aggregates — get_aggregates_for_user(), and the $aggregates passed to igcf_platform_creator_stat_tiles, gain paused_campaigns, not_started_campaigns, closed_no_outcome_campaigns, test_campaigns and other_campaigns. The group fields always add up to total_campaigns. See Service methods.

Compatibility

Now requires Ignition Crowdfunding 0.23.0 — The operator settings and the reason Offline is hidden both use features that first ship in core 0.23.0. The add-on refuses to start on an older core and tells you to update.

Ignition Platform Fees v0.3.1

Fri, 30 Oct 2026 00:00:00 GMT

Ignition Crowdfunding 0.23.0 adds operators: staff who run the fundraising without an administrator login. This release lets them set the commission, and it requires Ignition Crowdfunding 0.23.0 or later.

Improvements

Operators can set the commission — Operators can open Ignition → Settings → Add-ons → Platform Fees and change the commission rate and minimum, just as administrators can. See Setting your commission.

Requirements

Ignition Crowdfunding 0.23.0 or later — Below it, the add-on does nothing and shows a notice naming the version needed. See What you need.

Developer

Operator settings — The add-on declares both of its stored settings, rate_bps and minimum_minor, on the igcf_operator_settings filter. See Core seams consumed.

Ignition Favorites v0.1.2

Fri, 30 Oct 2026 00:00:00 GMT

Ignition Crowdfunding 0.23.0 adds operators: staff who run the fundraising without an administrator login. This release lets them manage the Favorites settings.

Improvements

Operators can manage the Favorites settings — Operators can open Ignition → Settings → Add-ons → Favorites and change the public favorite count, just as administrators can. This needs Ignition Crowdfunding 0.23.0 or later; on older versions only administrators can change it. See Settings.

Developer

Operator settings — The add-on declares both of its stored settings, count_visibility and count_threshold, on the igcf_operator_settings filter. The filter has no effect on a core older than 0.23.0, so the add-on’s minimum core version is unchanged.

Ignition Contributions v0.1.1

Fri, 30 Oct 2026 00:00:00 GMT

Ignition Crowdfunding 0.23.0 adds operators: staff who run the fundraising without an administrator login. This release lets them manage the Contributions settings, and it requires Ignition Crowdfunding 0.23.0 or later.

Improvements

Operators can manage the Contributions settings — Operators can open Ignition → Settings → Add-ons → Contributions and change every option on it, just as administrators can. See Configuring the options.
Fix links only for those who can use them — When a section warns that backers will not see an option, the link to the screen that would fix it (such as the Payments tab) now appears only for administrators, because only administrators can change those screens. Operators still see the warning and the reason. See When an option cannot reach backers.

Requirements

Ignition Crowdfunding 0.23.0 or later — Below it, the add-on stays inert and shows a notice naming the version needed. See What you need.

Ignition Payouts v0.1.1

Fri, 30 Oct 2026 00:00:00 GMT

A small maintenance release. It fixes an accessibility gap on the Record a Payout screen and brings the add-on’s wording in line with operators, who can now record payouts alongside administrators. It requires Ignition Crowdfunding 0.23.0 or later.

Improvements

The payout email names staff, not just administrators — On the Emails tab, the Payout Recorded email is now described as sent to the creator when staff record a payout to them, since operators record payouts too. See The Payout Recorded email.

Bug Fixes

Column headers stay available to screen readers on narrow screens — On a screen 600 pixels wide or less, the tables on the Record a Payout screen turn each row into a labelled card. Their column headers used to be removed entirely, so a screen reader announced each value with no column name. The headers are now hidden from sight only, and screen readers read them as before. See Recording a payout.

Requirements

Ignition Crowdfunding 0.23.0 or later — The add-on now needs core 0.23.0. Below it, the add-on does nothing and shows a notice naming the version needed. See What you need.

Ignition Crowdfunding v0.22.0

Tue, 08 Sep 2026 00:00:00 GMT

Until now a pledge was one number. Once an add-on can add something on top of it — a tip, a fee the backer chose to cover — one number stops being enough, and every screen has to answer two different questions: what the backer was charged, and where that money went. This release gives both questions one answer, computed once and shown the same way on the checkout, the receipt, the email, the backer’s pledge page and the wp-admin pledge screen.

New Features

An itemised breakdown of every charge — When a charge is made up of more than the pledge itself, backers now see it spelled out: each part on its own line, with a bold Total charged at the foot. The same list appears on the checkout review step (updating live as the backer changes their mind), on the receipt, in the payment-received email and on the pledge’s page in the backer dashboard, so the four never disagree. A plain pledge with nothing added shows no list at all — there is nothing to itemise. See Checkout and Pledge Detail.
The admin pledge page is now two plain statements — Ignition → Pledges → View replaces the old Amount / Refunded / Net block with two tables side by side, one pair per successful payment: Charged to backer, itemised exactly as the backer saw it, and Where it went, the same money split by destination — returned to the backer, kept by the payment processor, taken by the platform, and the Net left over. Each destination is named in plain words, and the Net row says whether the money is still with the operator (owed) or has reached the creator. If the parts of a charge fail to add up to the charge, or if this page’s Net disagrees with the figure the rest of wp-admin reads, the page says so in an error notice instead of quietly showing a wrong total. See Managing Pledges.
A processing-fee column in the pledge exports — Both the wp-admin Export Pledges and the creator dashboard’s Export Pledges now carry a Processing Fee column beside the net, so the fee the payment processor kept is a figure you can read rather than a difference you have to derive. A pledge whose gateway never reported a fee leaves the cell empty — that is “never recorded”, not “zero”. See Settings and Managing a Campaign.

Improvements

Each net figure is named for whoever receives it — The creator dashboard export’s net column reads Net to You, the wp-admin pledge export’s reads Net to Recipient. The backer export keeps Net Received, because that column really is money a backer paid and is the one net on the site that cannot go negative.
A net below zero is shown as a negative number, and explained — When a card payment is refunded the processor keeps its fee, so the pledge can settle slightly under zero. That figure is no longer floored at $0.00: the wp-admin Pledges list prints it signed (-$4.67, sign outside the currency symbol), the creator dashboard shows a short note above the pledge list explaining why, and the CSV exports pass it through as a real negative number a spreadsheet can sum rather than a text-escaped one. See When a refund leaves you below zero.
The payment-received email leads with what was actually charged — It now reads “We received your payment of …” using the amount that left the backer’s card. When that amount is larger than the pledge, the email names both figures and prints the itemised breakdown beneath; when it is not, it stays a single sentence with no table. The two figures are never added together into one “contribution” total.
The backer’s partial-refund email no longer calls the remainder a contribution — It now reads “You have now paid … in total for this pledge.” The figure is the amount charged less refunds, which on a charge carrying a tip or a fee is not the campaign’s share, so describing it as a contribution was wrong. The administrator’s copy of the same email still uses the older “Net contribution” wording.
A selected amount button is bolder, not just darker — The pressed amount button on the pledge form and the checkout’s amount selector now carries a heavier weight as well as the filled background, so which one is selected does not depend on colour alone.
The creator dashboard’s pledge table works on a phone — Below 601px each pledge becomes a labelled card carrying every column, instead of the table dropping the Email column and squeezing the rest.
Two more add-ons in the catalog — Settings → Add-ons now lists Ignition Contributions and Ignition Payouts alongside the rest, with their status and download links. See Add-ons.

Bug Fixes

Pledges show in the currency they were taken in — The Amount column on the wp-admin Pledges list, the {pledge_amount} merge tag in emails, and the amount inside the offline payment instructions all formatted the figure with the site’s current currency setting rather than the pledge’s own. On a site whose currency had changed — or one taking pledges in more than one — that showed the wrong symbol and, for a currency with a different number of decimal places, an amount off by a factor of a hundred.
Long figures no longer spill out of the Campaigns list — The Goal and Ends columns on Ignition → Campaigns were narrower than the values they hold, and because a WordPress list table uses a fixed layout the content escaped sideways over the neighbouring column instead of the column growing. Both are now wide enough for their longest ordinary value and wrap inside the cell rather than overflowing.
The suggested-amounts editor hides its Add control on mobile — At the six-amount maximum the Add field and button stayed visible on narrow screens, because two wp-admin rules overrode the attribute that hides them.

Developer

igcf_pledge_detail_money_rows is removed — It handed an add-on a list of pre-formatted money rows and let it pick its own position and its own plus-or-minus sign, so core could never check that the rows added up to what the backer was charged. Declare an igcf_pledge_settlement_terms term instead: state an amount in minor units and where it went, and core does the ordering, the signs, the formatting and the totals. A callback left on the old name never runs; core detects it while rendering the pledge page and reports it through _doing_it_wrong().
One definition of what a charge is made of — Igcf_Pledge_Breakdown builds both the projected charge (checkout) and the recorded one (everything after payment); add-ons contribute rows through igcf_pledge_breakdown_components, and igcf_render_pledge_breakdown() renders them through the new theme-overridable partials/pledge-breakdown template. Its companion Igcf_Pledge_Settlement answers where that same money went.
Two new checkout seams — igcf_checkout_review_money_before is a render slot on the review step for backer-facing money controls, and igcf_checkout_pre_submission_error lets an add-on refuse a submission after the nonce check but before identity is resolved, so a refusal creates no pledge, no payment attempt and no guest account.
Named fee components, and a projection that needs no attempt — igcf_payment_attempt_application_fee_components breaks the platform’s cut into named parts whose sum is the scalar application fee, and igcf_projected_charge_context answers the same questions for a hypothetical charge, campaign-keyed, before any pledge row exists. See Add-on seams.
The processing fee has an owner — igcf_payment_attempt_processing_fee (per attempt) and igcf_pledge_processing_fees (batched per pledge) are the gateway’s place to report what its processor kept. Core now subtracts the per-attempt figure from the igcf_payment_attempt_net_to_creator default, which consequently can now be negative and is no longer floored at zero — treat it as a display figure, not a payout basis.
Payments record who is holding the money — A new operator_custody column on igcf_payment_attempts (database version 10) is stamped once at create time from igcf_payment_attempt_operator_custody and never re-derived, while igcf_payment_attempt_operator_still_holds answers whether the operator is holding it right now. See the Service Layer.
Ask what a routing choice would cost before making it — igcf_pledge_routing_consequences( $to_creator ) collects what a site would lose by routing pledges the given way, so a settings screen can warn about the option an operator has not picked. Append through the igcf_pledge_routing_consequence() helper rather than by hand. See Who receives pledges.
Two refunds core now refuses — A refund against a payment attempt that never succeeded is rejected unless it carries a gateway reference (igcf_payment_attempt_not_refundable), and a partial refund with no gateway reference against a charge larger than its pledge is rejected as unattributable (igcf_refund_partial_not_attributable). Recording a refund also no longer risks committing a caller’s open transaction: the unreliable MySQL probe is gone, and a caller inside its own transaction declares it through igcf_db_in_transaction to get savepoint semantics.
Two new merge tags — {charged_amount} and {charge_breakdown}, both documented in the Merge Tags Reference.
igcf_format_amount_signed() — Formats a minor-unit amount with the sign outside the currency symbol (-$4.67, not $-4.67). Non-negative amounts come back identical to igcf_format_amount().
A shared dashboard table look — .igcf-dashboard__table and its --grouped, __col-amount and __cell-value companions are the frontend dashboard’s one table style, available to add-ons. .igcf-dashboard__pledge-table stays on the pledges table alongside it. See CSS Classes.

Ignition PayPal Gateway v0.5.0

Tue, 08 Sep 2026 00:00:00 GMT

PayPal takes a processing fee out of every payment, and until now your site had no idea how much. This release asks PayPal, the moment a payment completes, what it actually settled — the fee PayPal kept, the amount it worked from, and on a split pledge the cut it passed to your platform — and records those figures against the payment. The fee then shows up on the pledge page, comes off every net figure, and fills the Processing Fee column in your exports.

New Features

PayPal reports what it settled — Every completed PayPal payment now carries PayPal’s own settlement figures, read from PayPal rather than estimated on your site. The fee varies with the payer’s country, their funding source and your PayPal pricing, so the only trustworthy number is the one PayPal reports back. See What PayPal keeps.
The fee appears where you read the money — The pledge page in wp-admin gains a Processing (gateway) line in its Where it went table; the net for a PayPal pledge has the fee taken off wherever an admin or a creator reads it; and pledge exports fill in the Processing Fee column beside the net. A pledge PayPal has not reported a fee for leaves the cell empty rather than claiming a fee of zero. This is also why a fully refunded PayPal pledge settles at a small negative net — see When a refund leaves you below zero.
A recovery check for settlements PayPal never reported — Reading the settlement figures is a separate call to PayPal, and a network blip can lose it without affecting the payment itself. A background check now runs twice a day, picks up recent payments that still have no figures, and fills them in. See When PayPal cannot be reached.

Improvements

Settings headings match the rest of wp-admin — The Live and Sandbox group headings on the PayPal settings screen now use core’s shared heading style rather than PayPal’s own copy of it, so they line up with every other Ignition settings screen.

Bug Fixes

A refund that arrived before its payment — If PayPal’s payment notification never reached your site but a refund for that same payment did, the pledge stayed pending and neither the payment nor the refund appeared in any total. A refund is proof PayPal took the money, so the payment is now settled first and the refund recorded against it.

Developer

Settlement seams — The add-on answers core’s per-attempt and per-pledge processing-fee seams, the pledge-net seam, the pledge settlement-terms seam, the operator-custody seam and the projected-charge-context seam. Presence is a marker, not a value: a payment whose breakdown has been read answers even a genuine zero, while one that has never been read answers nothing. See the PayPal developer reference.
Scheduled event — igcf_paypal_settlement_sweep runs on the twicedaily schedule, is registered on load when missing, and is cleared on deactivation and uninstall. See Scheduled events.
Platform-fee reconciliation — On a split capture the add-on compares the platform fee PayPal reported settling against the fee the order asked for and writes a diagnostic to the PHP error log when they differ. Nothing is corrected; money PayPal has already settled cannot be moved from here.
Storage — The add-on’s own table gains its settlement columns and its storage version moves to 6. The upgrade runs automatically.

Compatibility

Now requires Ignition Crowdfunding 0.22.0 — This release reads and answers core’s settlement seams, which 0.22.0 introduces, and its settings-screen headings render a shared component that ships in core’s admin styles from the same version. The add-on refuses to start on an older core and tells you to update.

Ignition Platform Mode v0.4.0

Tue, 08 Sep 2026 00:00:00 GMT

A correction and a warning. The email a creator gets when you close their campaign no longer tells them their funds have been disbursed — closing a campaign locks it, it does not move money. And the Who Receives Pledges setting now lists, before you commit to a switch, which of your other settings the choice you have not picked would turn off.

Improvements

The pledge-routing setting says what switching would cost — Ignition → Settings → Add-ons → Platform Mode → Who Receives Pledges now lists what the choice you have not picked would turn off, with a short reason for each, before you pick it. Contributions names the backer options that would stop working; Platform Fees names a commission that would be left with nothing to take a cut of. Each names only what is working on your site today, so a setting you already switched off is not listed, and when nothing would be affected there is no list at all. The note ends with the part that matters most: your settings are kept, and start working again if you switch back. See What switching would turn off.

Bug Fixes

The campaign-closed email no longer claims funds were disbursed — Closing a campaign is a wind-up milestone: it locks the campaign so its details can no longer be edited. It has never moved any money. The email sent to the creator said their funds had been disbursed anyway — telling creators money was on its way when nothing had moved. It now says the campaign is closed and its details are final, gives the final amount raised, and leaves the money question alone. See Closing a campaign.

Developer

Platform Mode answers igcf_payment_attempt_operator_custody for offline payments — It answers true when the site routes pledges to the platform, and passes every other payment method through untouched. This matches core’s own default rather than diverging from it: the point is to mark offline as the method this add-on owns, the way a gateway add-on owns its own. Core stamps the answer once, when the payment attempt is created, so a later change to the routing setting never rewrites payments already taken — and that stamp is what Ignition Payouts reads to work out what an operator is holding. See the Platform Mode developer reference.
Your add-on can join the routing warning — The Who Receives Pledges screen renders whatever add-ons answer core’s igcf_pledge_routing_consequences question, so a setting of yours that works under only one routing can be listed alongside the rest. Build the answer with core’s igcf_pledge_routing_consequence() helper, and note that the filter is handed the routing being asked about — the one the operator has not picked — not the one in force. An entry missing a label or reason is skipped, so a malformed answer costs you your own line rather than the screen. See Warning about your own setting when routing changes.

Compatibility

Now requires Ignition Crowdfunding 0.22.0 — the Who Receives Pledges screen asks core what a routing change would turn off, and that question ships in 0.22.0. The add-on refuses to start on an older core and tells you to update.
Ignition Payouts requires this release — the new Ignition Payouts add-on needs Platform Mode 0.4.0 or later and will not start on an earlier one.

Ignition Platform Fees v0.3.0

Tue, 08 Sep 2026 00:00:00 GMT

A commission that never gets collected used to be something you found out about after the fact. This release says so up front — on the Platform Fees settings screen, on the Platform Mode routing screen, and across wp-admin — and it names the specific reason each time. It also makes the safety net that protects creators measure itself against the pledge itself rather than against the total the backer was charged, and, with Ignition Contributions installed, lets a backer volunteer to cover the commission at checkout.

New Features

Warnings for a commission the site cannot collect — The Platform Fees settings screen now checks your rate and minimum against the smallest pledge you accept and says so when the two do not fit. A minimum at or above your smallest pledge, no smallest pledge set at all, or a rate high enough to round a small pledge’s commission up to the whole pledge each get their own warning naming the amounts involved and what to change. A rate of 100% or more gets a separate warning: it would take the whole pledge on every pledge, so nothing is ever collected. See Warnings on the settings screen.
Backers can volunteer to cover the commission — With Ignition Contributions active, this add-on now supplies the commission figure that checkout needs, so a backer can be offered the option to pay the platform’s cut on top of their pledge instead of the creator absorbing it. It is offered only on an online pledge in the site’s own currency, on a payment method that settles the platform’s cut, and only where the commission is above zero and below the pledge. See When backers cover the commission.
The routing screen says what central collection would cost — On Ignition → Settings → Add-ons → Platform Mode, a site currently routing pledges to creators now sees Platform Commission listed under what switching to “The platform” would turn off, with the reason spelled out: commission is taken out of a pledge as it is split to the creator, so there would be nothing to take a cut of. It appears only when you actually have a commission configured. See When pledges come to you instead.

Improvements

The “nothing can collect this” warning now checks your payment methods — The site-wide wp-admin warning used to fire on whether any gateway had registered itself as able to settle a platform fee. It now asks your payment methods directly: a method counts only if it is switched on, can split a pledge, and reports itself as finished being set up. A gateway that is installed but half-configured no longer counts as able to collect. The warning also fires on a minimum-only commission (a 0% rate with a floor still collects), and it stays quiet on a site that routes pledges to the platform, where the settings screen already explains the situation in more detail. See When no payment method can collect.
The commission cap is measured against the pledge, not the total charged — A commission is dropped to nothing when it would reach the whole pledge, so a misconfigured floor cannot leave a creator with nothing. That comparison is now made against the pledge amount itself. Previously it was made against the total the backer was charged, which meant a voluntary tip or cover added on top of a pledge could raise the total enough for a commission to be collected that would otherwise have taken the creator’s entire share. See When the commission would swallow the contribution.
Commission reads as a settlement line on the pledge page — The admin pledge detail page now shows where each charge went, one block per successful payment, and the commission appears there as a Commission (platform) line beside the net that reaches the creator. After a refund the line shows what the platform kept — the commission recorded, less what was reversed — and shows $0.00 rather than vanishing when all of it was given back, so “fully reversed” and “this platform takes no commission” stay distinguishable. See On a single pledge.

Bug Fixes

A per-pledge net below zero is no longer rounded up to $0.00 — When the commission and the payment processor’s retained fee together came to more than the money that stayed in, the add-on used to force the pledge’s net figure up to $0.00, hiding a genuine shortfall. It now reports the real number. See When a refund leaves you below zero.

Developer

Commission is contributed as a named fee component — The add-on now answers igcf_payment_attempt_application_fee_components with a commission key rather than adding to the scalar igcf_payment_attempt_application_fee, so the platform’s cut is itemised by contributor instead of arriving as one opaque total. It also answers the attempt-free igcf_projected_charge_context, at a priority above the gateway’s, so checkout can price a commission before any payment attempt exists. See the Platform Fees developer reference and the add-on seams.
The pledge money statement replaces the money-rows filter — The add-on now declares a commission term through igcf_pledge_settlement_terms. Core removed igcf_pledge_detail_money_rows in 0.22.0; an older Platform Fees left hooked to it renders no commission lines at all on the pledge page. See settlement terms.
Igcf_Fees_Calculator::breakdown_for_amount( $pledge_amount_minor ) — Computes the commission from a bare pledge amount, for callers with no pledge row to hand. breakdown_for( Igcf_Pledge $pledge ) delegates to it and is unchanged. The cap that drops a commission reaching the whole pledge now lives here, so every caller gets the same answer. See Calculation.

Compatibility

Now requires Ignition Crowdfunding 0.22.0 — the settlement-terms, fee-components, projected-charge and routing-consequences seams this release is built on all ship in core 0.22.0. The add-on refuses to start on an older core and names what to update.

Ignition Contributions v0.1.0

Tue, 08 Sep 2026 00:00:00 GMT

The first release of Ignition Contributions, a premium add-on for Ignition Crowdfunding. At checkout a backer can choose to cover the platform commission the creator would otherwise absorb, cover the payment processing cost, or add a tip for your site — each one opt-in, each one itemised, and each one refusable before they authorise the payment. Requires Ignition Crowdfunding 0.22.0 or later.

New Features

Three voluntary additions at checkout — A panel on the review step headed Add to your payment offers up to three separate choices on top of the pledge: cover the platform fee, cover the processing fee, and a tip chosen from your percentage presets. Each is independent, and a backer who wants none pays exactly their pledge. See What a backer sees.
A settings screen per option — Turn each option on or off, pre-select it or not, and write your own backer-facing wording of up to 80 characters. The tip takes up to four percentage presets and a default; the processing cover takes the percentage and per-transaction fee you copy from your gateway’s pricing page. See Configuring the options.
Warnings when an option cannot reach backers — Each section says so on its own when its option cannot work on this site — no online payment method, pledges collected centrally rather than routed to creators, Platform Fees missing or too old — names the reason in a sentence, and links to the screen that would fix it. A warned section goes grey and keeps everything you configured, so it starts working again untouched when the condition clears. See When an option cannot reach backers.
A heads-up before you change pledge routing — With this add-on installed, the Who Receives Pledges setting in Platform Mode lists by name which Contributions options the other choice would turn off, and why, before you switch it. Only options you have switched on that work today are listed, in the same words the Contributions screen uses. See Who receives pledges.
A live total the backer can trust — The breakdown, the total above it and, where the checkout offers a choice of payment method, a Total to be charged line under that chooser all move together as the backer picks and unpicks options. Switching payment method swaps the panel for what that method can offer and recalculates. If the total is ever recalculated to something other than the figure the page was showing, the payment is refused rather than taken — no pledge, no charge, no account created.
The same breakdown everywhere after payment — The on-site receipt, the payment received email, the backer’s own pledge page and the wp-admin pledge money statement all itemise the charge with the same rows, the same labels and the same order, ending in Total charged. The admin statement additionally shows a backer’s tip as a Tip (platform) line under Where it went. See On the receipt, in email, and on their pledge page.
Refunds account for the additions — A refund is issued against the whole charge, so a full refund returns the additions along with the pledge, and a returned tip stops counting as your revenue. A payment that carried a voluntary addition cannot be partially refunded from wp-admin: Ignition declines it and asks you to refund in full, rather than guess which of the money was pledge and which was extra. See Refunds.

Known limitations

A partial refund still takes off the whole tip — If a partial refund reaches a pledge that carried a tip — one issued in the gateway’s own dashboard and reconciled back, rather than through Ignition — this release deducts the tip in full rather than in proportion. That can leave the pledge’s net below zero, and it is shown that way rather than rounded up to $0.00. See When a refund leaves you below zero.

Developer

No hooks of its own yet — This release exposes no action, filter or registry for other plugins to extend. It is a consumer of core’s money seams — the checkout review money slot, the pledge breakdown components, the amount to charge, the application fee and net-to-creator seams, and the settlement terms behind the admin pledge statement — all of which are documented under add-on seams in the core reference.

Compatibility

Requires Ignition Crowdfunding 0.22.0 — The checkout money slot, the shared charge breakdown and the settlement-terms statement it builds on all arrive in core 0.22.0. The add-on refuses to start on an older core and names what to update.
The commission cover needs Ignition Platform Fees 0.3.0 — Platform Fees older than that charges no commission this add-on can see, so the commission cover is withheld and its section says so. The tip and the processing cover are unaffected.

Ignition Payouts v0.1.0

Tue, 08 Sep 2026 00:00:00 GMT

The first release of Ignition Payouts. When your platform collects pledge money on behalf of your creators, this is the record of paying it back out: one screen showing every creator you owe and how much, a form to record each payment you made, a history to audit it against, and — on the creator’s side — a page and an email telling them what arrived.

It records payments; it does not send them. Every payout describes money you already moved at your own bank, which is why the suggested figure is on screen before anything leaves your account rather than after.

New Features

The To Pay queue — Every creator you are holding money for, one row per creator per currency, with what you owe, how many payments make it up, and how long the oldest has been waiting. Rows split into Ready to Pay and Held Back, so money behind an all-or-nothing campaign that fell short is separated from money that is safe to send — and never mixed into the same row. See The To Pay queue.
Record a payout — A form that shows exactly what it settles before you commit: the campaigns, every held payment with its backer and date, any refunds netted off since the last payout, and the suggested amount. The amount arrives pre-filled and stays editable, because the money moved at your bank and your figure is the true one. Both numbers are stored, so a difference stays visible on the record instead of disappearing. See Recording a payout.
Unreliable figures are marked before the money moves — Where a payment’s underlying data is known to be incomplete, the queue and the record form say so and say which direction it is wrong in: too high when a payment processor never reported its fee, too low when a partial refund of a tipped charge deducted the whole tip. The mark never changes the amount and never blocks you; it exists so the correction happens on screen rather than at the bank. See When the suggested figure is marked unreliable.
Payout history — Every payout you have recorded, newest first, filterable by creator and by month, with a per-currency total that covers everything the filters match rather than just the page on screen. Each payout opens into a full record: what it covered, what refunds it absorbed, and an append-only status history. See Payout history.
Reversing a payout, without rewriting history — A payout recorded in error is reversed, never edited or deleted. The original stays in the ledger marked Reversed, a reversing entry appears beside it, the payments it covered return to the To Pay queue, and the two net each other out in the totals. See Reversing a payout.
Creators can see what arrived — A read-only Payouts page on the creator dashboard listing every payout they have received: date, amount, method, your reference, and — expandable per payout — every payment it settled, grouped by campaign. A lifetime total closes the table. It is what lets a creator reconcile a bank deposit against their pledges without asking you. See What creators see.
A payout-recorded email — Sent to the creator when you record a payout, in the past tense because the money has already gone, with the amount, date, method, your reference, and what it covered. Creators can switch it off from their own account page. The confirmation you see after recording tells you whether it actually went. See The payout-recorded email.
Trace one pledge to its payout — The Payment Attempts table on the wp-admin pledge detail page gains a Payout column naming the payout that carried each payment, or saying it has not been paid out yet.
Live and Test kept apart — Every wp-admin screen follows the Live / Test switch, so rehearsal money never appears in a real queue or a real total. The creator’s own page shows both, badged, so a rehearsal payout is visible to the person who was told about it.
Refunds that arrive after you paid — A refund recorded after the creator was paid is never clawed back. It comes off their next payout instead, is shown on the record form as its own line, and is listed on the payout that eventually absorbs it.
Fails loudly, not silently — The add-on refuses to start, naming what to update, when Ignition Crowdfunding is below 0.22.0 or Ignition Platform Mode is missing or below 0.4.0.

Developer

The Payout is a first-class entity — A filterable transitions map, a creation action and the three-tier status-change actions core gives its own entities, a filter over the row about to be written, a per-status veto, and an append-only read API with a bulk coverage lookup. Recipient, currency and mode are derived from the payments a payout covers and cannot be overridden through the filter. See the Payouts reference.
Answers core’s custody question — The add-on answers igcf_payment_attempt_operator_still_holds with false for a payment an in-force payout already covers, so core’s own money statements stop describing held money once it has actually gone out.

Requirements

Ignition Crowdfunding 0.22.0 or later
Ignition Platform Mode 0.4.0 or later, active
WordPress 6.9 or later, PHP 8.2 or later

No payment gateway is required. Recording a payment you made at your own bank needs none.

Not in this release

Sending money through a payment gateway, tracking what a creator owes the platform, and accounting exports are planned for later versions. Payouts can be recorded and reversed; pending and failed payouts exist in the record for the send-money path but cannot be reached yet.

Ignition Crowdfunding v0.21.0

Fri, 21 Aug 2026 00:00:00 GMT

Test campaigns have always been isolated on the way in — a test campaign takes pledges through the real pipeline and settles them against sandbox credentials. This release finishes the job on the way out. A toggle in the admin bar puts every admin screen into Live or Test view, and the two sides never mix. Along the way it closes a real leak: test money was inflating the revenue chart on your dashboard.

New Features

Live and Test view — A toggle at the far right of the admin bar switches every admin screen between live money and test money. The Pledges list, the Backers list, the Campaigns list, campaign and backer detail tiles, the dashboard cash-flow chart, the payment-method pledge counts and the CSV exports all follow it. The whole admin bar turns teal in Test view, so you can tell at a glance which side you are on. Settings do not scope — configuration reads the same either way; only the numbers change. See Live and Test view.
Empty screens that explain themselves — The failure this guards against is flipping to Test view, getting distracted, and returning to find zeros where forty backers used to be. So every empty list and every zero total says why, in words, where the rows or the figure would be: “You’re in Test view. No test pledges yet.” Zero-valued tiles in Test view carry a caption. Live view says the same thing about filters rather than the view. See Live and Test view.
The view travels in the link — The mode rides in the page address, so a link copied out of Test view opens in Test view for a colleague, and two tabs can sit in different views without fighting. Your last choice is remembered as where you land next time, per site — on a network, switching one site’s view leaves the others alone.
Creation follows the screen, not your habits — In Test view, Add New Campaign becomes Add New Test Campaign. The button reads the current address rather than your remembered default, so a tab left open since yesterday cannot create a campaign on the wrong side. That mistake is unrecoverable: a campaign’s side is fixed once it has pledges.
The switch sits with the settings — A payment method’s on/off switch moved from the Payments listing onto the method’s own Configure screen, so you set a method up and turn it on in one place instead of configuring it here and remembering to enable it there. The listing now shows a Configure → link. See Payments.

Improvements

Add-on Settings links can point anywhere — An add-on whose real settings screen lives elsewhere — a payment gateway’s own page under the Payments tab, say — now gets its Settings link sent there, instead of needing a second, near-empty page under Settings → Add-ons. See Add-ons.
Sign in, not log in — Frontend buttons now use Title Case, and the vocabulary is consistently “sign in” and “sign out” rather than a mix of both.
Test campaigns are teal — The Test status badge has its own colour rather than borrowing the amber that Paused and Pending Review already use.

Bug Fixes

Test money no longer inflates your revenue chart — The dashboard cash-flow widget ran its three queries with a date window and no campaign filter at all, so every test pledge was counted as real income on the chart and in the running Received, Pending and Refunded totals. It now follows your view. See Dashboard Widget.
A backer who only pledged to a test campaign is no longer invisible — The Backers list excluded test pledges unconditionally, which meant a backer whose only pledge was to a test campaign did not appear anywhere. They now appear in Test view. See User Summaries.
Backers can see their own test-campaign pledge again — A backer’s frontend dashboard hid their pledge to a test campaign. It is a real pledge on a real account that received real email, so it belongs there. It now shows, badged with the campaign’s status so it is not mistaken for an ordinary one. See Pledges.
Campaign pages render in the right order on block themes — Single campaign and campaign archive pages built their output before the theme’s header and footer had registered their block styles and scripts, so a block theme’s navigation and header could render unstyled or broken. They now follow WordPress’s own render order.
Exports match the screen you ran them from — The Pledges and Backers export links only carried the view mode when it was Test, which encoded “no parameter means Live”. It does not — an absent parameter means “use my stored default”. An admin whose default was Test, looking at a Live screen, got a CSV of test money. Both links now carry the resolved view either way.
A backer’s Cancel pledge button no longer hangs — Cancelling a pledge from the backer dashboard could leave the button stuck reading “Canceling…” after the cancellation had actually gone through.
A bad scope no longer takes the page down — An admin screen asked for an unrecognized data scope produced a fatal error rather than a message. It now refuses the query and says the list could not be scoped.

Developer

Cross-campaign queries require a scope — Every service method that aggregates across campaigns now takes a scope of 'live', 'test' or 'unscoped'. There is no default and no silent fallback: omitting it triggers _doing_it_wrong() and returns the empty shape. A wrong revenue figure gets pasted into a board deck; an empty screen gets reported. Queries already narrowed to one campaign or pledge are exempt. Money paths — Igcf_Refund_Service::query() and Igcf_Payment_Attempt_Service::query() — take no scope at all, deliberately, so a viewer’s chosen view can never reach a decision about real money. See Query scope.
Pledges carry a durable mode stamp — Each pledge row records the side it was written on at creation, in an igcf_pledges.mode column, rather than deriving it from the parent campaign’s current status. A post status is mutable and vanishes entirely when a test campaign is permanently deleted, which used to convert its pledges into live money. Igcf_Test_Campaign::campaign_scope_clause() builds the SQL fragment over it. See the Service Layer.
Menu badges know the view — igcf_admin_menu_badges passes the resolved mode as a second argument. Data-driven counts should follow it so the bubble agrees with the screen it links to; config-driven counts should ignore it. Receiving it is opt-in via accepted_args. See Filters.
One seam for who receives pledges — igcf_pledges_go_to_creator() is the single site-wide answer to whether a pledge goes to the platform or to the campaign’s creator. Core returns false; Ignition Platform Mode answers it from its own setting. Gateways branch on it rather than each carrying their own duplicate of the same choice. See Filters.
A render slot on payment-method screens — igcf_payment_gateway_settings_after_header fires on a method’s settings screen, after the header and before the form, for context that spans methods rather than belonging to one. See Actions.
Settings URLs for add-ons that live elsewhere — igcf_addon_settings_url registers an absolute URL per add-on slug, for add-ons whose settings already have a home. Relative paths and unsupported schemes are dropped rather than rendered as a broken link. See Filters.
The gateway toggle ability reports back — igcf/set-payment-gateway-enabled now returns the method’s resulting status badge and its lock_reason, so a caller can repaint the UI without a second request. See Abilities.
The show_test_campaigns_for_admins setting is gone — Whether an administrator sees test campaigns is a capability check and a view mode, not a stored option. Igcf_Single_Campaign::get_status_semantic_map() and its igcf_single_campaign_status_map filter are removed as dead code.

Ignition PayPal Gateway v0.4.0

Fri, 21 Aug 2026 00:00:00 GMT

PayPal used to carry its own Direct / Platform selector, which meant a multi-creator site could answer “who receives the money” one way for PayPal and another way for offline payments. That question now has one site-wide answer, and PayPal follows it.

Improvements

One place decides who gets paid — The Integration model selector is gone from the PayPal settings page. Whether pledges go to you or to each creator is set once, under Ignition → Settings → Add-ons → Platform Mode, and every payment method follows it. See Choosing who gets paid.
Only the credentials you actually need — The settings page now shows a single credential group rather than two: Merchant keys when pledges come to you, Platform keys and your Account ID when they go to creators. Each still has its live and sandbox pair with a per-environment connection test. You are never asked to fill in a set of keys the site will not use.
Settings link on the Plugins screen — PayPal’s row on the Plugins screen now carries a Settings link that opens its screen under the Payments tab, rather than a near-empty page of its own.
The switch sits with the settings — Turning PayPal on is now the Accept PayPal toggle at the top of its own settings screen, alongside the credentials, rather than a checkbox back on the Payments listing.
Sign in, not log in — Wording on the creator-facing PayPal account screen matches core’s Title Case buttons and “sign in” vocabulary.

Compatibility

Now requires Ignition Crowdfunding 0.21.0 — this release reads core’s site-wide pledge-routing setting, which 0.21.0 introduces. The add-on refuses to start on an older core and tells you to update, rather than failing partway through a checkout.

Ignition Platform Mode v0.3.0

Fri, 21 Aug 2026 00:00:00 GMT

Two changes worth knowing about. Who receives a pledge is now one setting for the whole site rather than a choice buried in each payment method, and a backer who decides to run a campaign no longer has to ask you for permission.

New Features

Who Receives Pledges — A single setting under Ignition → Settings → Add-ons → Platform Mode: either you collect every pledge and pay creators out yourself, or pledges go straight to the campaign’s creator. It applies to every payment method at once. That is the point of it living here — “who gets the money” is a fact about how your platform works, and a site where PayPal pays creators while offline payments come to you is a site nobody can reason about. Each method’s settings screen then follows the choice instead of asking again: Offline drops its site-wide instructions field when creators collect, PayPal shows only the credential set the choice needs, and Platform Fees warns you when your commission has nothing to take a cut of. See Who receives pledges.
Backers can become creators — Someone who signed up to back a campaign, and later wants to run one, presses Start a Campaign in their own dashboard. They get the creator role alongside what they already have and land in the campaign wizard, keeping their account and their pledge history. The offer appears only while Public Campaign Creation is on, and only to someone who has never held creator access — so revoking a creator’s access sticks. It is withheld until the person has proven the email address is theirs: a guest is offered Claim Your Account instead, and an unverified account is asked to verify first. See Backers who decide to create.

Improvements

The Creators list follows the Live/Test view — The roster, each creator’s stat tiles, and their campaign table all scope to whichever view you are in, matching every other admin screen. A creator whose only campaign is a test campaign appears in Test view. In Test view a zero tile is captioned rather than left to look like a creator who has raised nothing. See The Creators list and Live and Test view.

Developer

A take-over seam for granting creator access — igcf_platform_pre_creator_access fires at both doors that grant the role — registration and the dashboard upgrade. Return a URL to take over: no role is granted, and from the dashboard the person is sent there instead. This is where a verification, application or identity-check add-on hooks. See the Platform Mode developer reference.
Creator stat tiles receive the view mode — igcf_platform_creator_stat_tiles gains a fourth $mode argument, and the $aggregates it passes are already scoped to it. Scope your own figure the same way or your tile will disagree with the ones beside it. Receiving it is opt-in via accepted_args. See the Platform Mode developer reference.
Creator queries require a scope — Igcf_Platform_Creator_Service::query_paginated() and get_aggregates_for_user() now take an $args array with a required scope, mirroring core’s backer service. Note that user_id does not narrow it: one creator can have campaigns on both sides. See the Platform Mode developer reference.

Compatibility

Now requires Ignition Crowdfunding 0.21.0 — the Creators screens scope to the Live/Test view, which 0.21.0 introduces. The add-on refuses to start on an older core and tells you to update.

Ignition Platform Fees v0.2.0

Fri, 21 Aug 2026 00:00:00 GMT

A commission is taken out of a pledge as it is split to the creator. If a site routes pledges to the platform instead, nothing is being split — so nothing is collected, whatever rate you set. This release says so, out loud, instead of leaving a configured rate silently uncollected.

New Features

A warning when nothing can be collected — Set a rate or a minimum on a site where pledges go to the platform rather than to creators, and the settings screen says “No commission is being collected” and explains why. You can leave the commission set up ready for later, or change Who Receives Pledges. The warning appears whenever either field is set, not just the rate — a 0% rate with a minimum still collects, so a minimum-only setup would otherwise slip past unnoticed. See When pledges come to you instead.

Improvements

Commission figures follow the Live/Test view — The Platform Commission and Net after Commission tiles on a creator’s admin detail view scope to whichever view you are in, so they reconcile with the gross figures beside them. In Live view a creator with no commission still gets no tiles, exactly as before. In Test view the tiles always render, zero included — a captioned $0.00 tile is the honest answer, where showing nothing would be indistinguishable from the add-on not being installed. See Per creator.

Developer

Commission reads take a scope — Igcf_Fees_Net::commission_for_creator( $user_id, $scope ) requires a scope, since it reads across campaigns. gross_terms_by_campaigns() takes an optional one, applied to the charge and reversal halves together so a scoped charge can never net against an unscoped reversal. See the Platform Fees developer reference and query scope.

Compatibility

Now requires Ignition Crowdfunding 0.21.0 — commission figures are counted under core’s query scope, which 0.21.0 introduces. The add-on refuses to start on an older core and names what to update.

Ignition Favorites v0.1.1

Fri, 21 Aug 2026 00:00:00 GMT

A one-line wording change, released to keep Favorites in step with core’s vocabulary.

Improvements

Sign in, not log in — The heart shown to a signed-out visitor is labelled Sign in to favorite, matching the “sign in” and “sign out” wording used everywhere else on the frontend. Screen-reader users hear the label; it does not appear on screen. See Favoriting a campaign.

Ignition Crowdfunding v0.20.0

Thu, 13 Aug 2026 00:00:00 GMT

This release is mostly groundwork. It adds the extension points that the new Ignition Platform Fees add-on builds on — a way for a payment gateway to say it will settle a platform’s cut, a single place where a platform deduction is applied to the money a creator nets, and a financial breakdown on the wp-admin pledge detail page. Alongside that, one correction backers will notice: the contribution figures shown to a backer are once again the backer’s own.

Bug Fixes

Backers see their own contribution, not the creator’s — On a site running a platform commission, the net figure on a backer’s dashboard pledge card and in their refund emails could show what the creator received after the platform’s cut, rather than what the backer actually contributed. On a half-refunded $100 pledge that meant a backer reading $47.50 where their own figure was $50.00. Both now show the backer’s own contribution less any refund. A platform’s cut is an arrangement between the platform and the creator, and is never part of what a backer is told they gave. See Refunds.

Developer

Gateway settlement question — Igcf_Payment_Attempt_Service::settles_application_fee() asks whether a gateway will actually settle this attempt’s platform fee when it captures the payment, with the igcf_payment_attempt_settles_application_fee filter for gateways to answer. It describes the gateway, not the configuration, so a fee add-on can hold back on attempts nothing can collect from. Defaults to no, which keeps commission entirely inert on a site with no split-capable gateway. See the Service Layer and Filters.
One place to adjust net-to-creator per pledge — The new igcf_pledge_net_amounts filter applies to both the batch read behind list screens and exports, and the single-pledge read behind the wp-admin pledge detail page. An add-on that deducts money from a creator hooks it once and every creator- and admin-facing net figure agrees. The older igcf_payment_attempt_net_to_creator is per attempt and has no core consumer; per-pledge is what display surfaces actually render. See Filters.
Pledge detail financial breakdown — Five filters let an add-on show its working on the wp-admin pledge detail page: a line item beside Amount, Refunded and Net, plus extra columns and cells on the Payment Attempts and Refunds tables. Core owns ordering and escaping, and discards a contribution that is not the documented shape, so a misbehaving add-on degrades to core’s own figures instead of breaking the page. See Filters.
Per-campaign gateway availability — igcf_gateway_available_for_campaign lets an add-on take an enabled gateway away from a specific campaign. It fires only for gateways already reporting themselves available, so a listener can only remove one, never add it back. This is how a gateway that can pay some creators but not others — one needing the creator to have connected an account — keeps itself off the campaigns it cannot serve. See Filters.
Creator pledge-row actions — igcf_dashboard_campaign_pledge_row_args is the creator-table counterpart to the backer-table row filter, so an add-on can put per-row actions such as “Mark payment received” on a creator’s campaign-pledges table. See Filters.
Backer-safe refund figures — Igcf_Pledge_Service::get_pledge_refund_amounts() returns a pledge’s money figures with no net adjustment applied, for surfaces shown to backers. Its sibling get_pledge_refund_display() keeps applying the seam, for admin and creator surfaces. Picking the wrong one is what caused the bug fixed above. See the Service Layer.

Ignition PayPal Gateway v0.3.0

Thu, 13 Aug 2026 00:00:00 GMT

This release makes the PayPal gateway work with the new Ignition Platform Fees add-on. Platform Fees only takes a commission where a gateway will genuinely settle it at the moment of payment, and PayPal now answers that question for its own pledges — so a commission is only ever recorded against money PayPal actually splits.

New Features

Works with Platform Fees — On a pledge paid through PayPal in Platform mode, PayPal now reports whether it will settle the platform’s cut when it captures the payment. It answers yes only where the split is genuinely viable for that campaign — the same check the checkout already runs before offering a split — so the fee that gets recorded and the money that actually moves can never disagree. A pledge PayPal cannot split carries no commission at all, rather than one recorded and never collected. See Platform mode.

This answer describes the gateway, not your settings. In Direct mode, or on a campaign whose creator has not connected a payable PayPal account, the answer is no and no commission is taken.

Bug Fixes

Repeat refunds after a sandbox reset — The reference sent to PayPal to stop a refund being submitted twice is now tied to the specific captured payment, not just the refund record. This only shows up while testing: resetting a development database recycles low refund numbers, while PayPal remembers references across resets, so a re-test could be rejected as a duplicate request. Live sites were never affected, because refund numbers there are never reused.

Requirements

Ignition PayPal Gateway 0.3.0 requires Ignition Crowdfunding 0.19.0 or later. Platform mode additionally requires Ignition Platform Mode, and collecting a commission requires Ignition Platform Fees.

Ignition Platform Mode v0.2.0

Thu, 13 Aug 2026 00:00:00 GMT

Offline payment on a multi-creator platform had one shape: backers paid you, and you confirmed every transfer by hand in wp-admin. This release adds the other shape. Creators can publish their own payment details, take the money directly, and confirm it arrived from their own dashboard — with the platform never touching it.

New Features

Creators collect their own offline payments — A new Integration model setting under Ignition → Settings → Payments → Offline chooses who collects. Direct, the default, keeps today’s behaviour exactly: one set of payment instructions that you write, and you confirm receipt. Platform hands both to the creator. See Offline payments.
Per-creator payment instructions — In Platform mode each creator gets an Offline payments section in their dashboard’s Account area, where they write how a backer should pay them. Three placeholders — {amount}, {campaign_name} and {pledge_id} — are filled in per backer, so a creator can ask for a payment reference that ties the money back to a specific pledge. Backers see the instructions on the confirmation screen, in their confirmation email, and on the pledge in their dashboard. See Writing payment instructions.
One-tap “Mark payment received” — When the money arrives, the creator confirms it from their campaign’s pledges list. Everything that normally follows a successful payment follows this too: the backer’s payment-received email, the pledge moving to succeeded, and the campaign’s collected total updating. Only the campaign’s own creator sees the action; administrators keep the ability they already had. See Confirming a payment arrived.
Offline hides itself until a creator can be paid — A campaign whose creator has written no payment instructions no longer offers offline payment at checkout, because there is nothing useful to show a backer. A submission asking for it anyway is refused rather than quietly switched to another method. A pledge already made offline stays confirmable even if the creator later clears their instructions, so editing them never strands money in flight. See Offline hides itself until a creator can be paid.

Developer

Creator money tiles — igcf_platform_creator_stat_tiles lets an add-on that owns its own per-creator money dimension append tiles to a creator’s wp-admin detail view, beside Total Pledged, Total Received, Refunded and Canceled. Contributions are shape-checked and anything malformed is skipped, so a misbehaving listener costs you its own tile rather than the page. See the Platform Mode reference.

Requirements

Ignition Platform Mode 0.2.0 requires Ignition Crowdfunding 0.20.0 or later.

Ignition Platform Fees v0.1.0

Thu, 13 Aug 2026 00:00:00 GMT

The first release of Ignition Platform Fees. Set a percentage and a floor, and your platform’s commission is taken out of each contribution at the moment the backer pays — the creator receives their share, you receive yours, and the payment provider settles both. No invoice to send, no payout to chase.

New Features

Commission rate and minimum — Two settings under Ignition → Settings → Add-ons → Platform Fees: a percentage, and a floor applied when the percentage works out smaller. The commission on a contribution is whichever is larger, so a percentage of a small pledge can never fall below what it costs you to process. A commission that would equal or exceed the contribution itself is dropped entirely, so a misconfigured floor cannot leave a creator with nothing. See Setting your commission.
Charged only where it can actually be collected — A commission is taken only where the gateway will genuinely settle it as the backer pays: today, a pledge through PayPal in Platform mode on a campaign whose creator has connected a payable account. Offline pledges, Direct-mode pledges, and campaigns whose creator cannot be paid carry no commission at all. Nothing is ever recorded that the platform has no way to collect. See Which contributions are charged.
Proportional refund reversal — Refunding a contribution gives back the commission in proportion: half a refund reverses half the commission. PayPal performs the reversal at the gateway, and the add-on records it so your figures keep reconciling. See Refunds.
A pledge that reconciles — The wp-admin pledge detail page reads as a ledger — amount, commission, refunded, commission reversed, net to the creator — and the Payment Attempts and Refunds tables gain a commission column, so the totals can be checked against the rows beneath them. See Where the numbers appear.
Per-creator totals — A creator’s wp-admin detail view gains Platform Commission and Net after Commission beside the gross figures, so you can see what a creator generated and what they actually netted.
Creators can reconcile themselves — A creator’s pledge export gains Commission and Net after Commission columns, matching what you see in wp-admin, so a creator can check their own income without asking you.
Never shown to backers — Your commission is an arrangement between your platform and your creators. It never appears on a backer’s receipt, in their emails, on their dashboard, or in the net figure shown for their own contribution. See What backers see.
Fails loudly, not silently — The add-on refuses to start, naming what to update, if core or Platform Mode is missing or too old, or if PayPal is installed but older than 0.3.0. If no split-capable gateway is present at all it still starts — a future gateway may fill that role — but warns you as soon as a rate is configured, because a rate nothing can collect is worse than no rate.

Developer

Built entirely on core seams — The add-on exposes no hooks of its own. It reads core’s settlement predicate to decide when to engage, answers the application-fee and per-pledge net seams, and fills the pledge-detail breakdown, creator stat-tile, and creator-export seams. Its own surface for other add-ons is a set of read accessors for commission by attempt, pledge, campaign, or creator. See the Platform Fees reference.

Requirements

Ignition Crowdfunding 0.20.0 or later
Ignition Platform Mode 0.2.0 or later, active
A gateway that splits payments — Ignition PayPal Gateway 0.3.0 or later, in Platform mode

Not in this release

Per-creator and per-campaign commission rates, and a reconciliation-focused export, are planned for later versions.

Ignition Crowdfunding v0.19.0

Wed, 29 Jul 2026 00:00:00 GMT

This release smooths several frontend rough edges — where the account card sends you, how the image-framing tool behaves on short screens, where the dashboard verification notice sits, and restoring a test campaign — and adds the gateway-capability groundwork that the Ignition PayPal Gateway’s new Platform mode builds on.

Enhancements

Checkout keeps what you typed — If a pledge submission is rejected for any reason, the review step now comes back with the email address and shipping details you already entered still filled in — previously only a missing required field preserved them.
Refund failure reason in wp-admin — When a refund fails, the pledge’s admin detail now shows the reason reported by the payment gateway, so a failed refund isn’t a silent dead-end. See Refunds.

Bug Fixes

Account card links to your dashboard — The “you are logged in” card on the account page now shows a single Go to your dashboard link for every signed-in user, instead of a “Start a Campaign” button that dead-ended for backers who can’t create campaigns. See Creating a Campaign.
Image framing on short screens — The Adjust framing tool now scales the image to fit the dialog on short viewports, so the whole image stays visible and draggable on smaller screens. See Creating a Campaign.
Verification notice placement — On the dashboard, the “verify your email” notice now spans the full width above the two-column layout instead of being squeezed into one column.
Test campaign restore — Restoring a test campaign from Trash now correctly returns it to the Test status. See Test Campaigns.

Developer

Gateway capability seam — Gateways can advertise named capabilities with Igcf_Payment_Gateway::supports(), and code can resolve them with Igcf_Payment_Gateway_Service::gateway_supports() and get_ids_supporting(). A dependent add-on queries a capability (such as platform_mode) rather than a gateway slug or version, so a future gateway advertising the same capability composes with no change to the consumer. See the Service Layer.
Refund failure-code registry — Igcf_Refund_Service::failure_codes() exposes a code => label registry, filterable via igcf_refund_failure_codes. Core ships it empty and gateway add-ons populate it, mirroring the payment-attempt failure codes; it powers the new admin refund-failure label. See the Service Layer and Filters Reference.
Pledge-context registration role — The frontend registration form now propagates the pledge context to the igcf_registration_role filter, so a visitor who registers while pledging is classified correctly — kept as a backer rather than becoming a creator on Platform Mode sites. See the Filters Reference.

Ignition PayPal Gateway v0.2.0

Wed, 29 Jul 2026 00:00:00 GMT

This release adds Platform mode: on a multi-creator platform, PayPal can now pay each pledge directly to the campaign’s own creator and take an optional cut for your platform — settled automatically by PayPal, with no manual payouts. Direct-mode checkout (every pledge into your own account) is unchanged and remains the default. Platform mode requires the Ignition Platform Mode add-on and Ignition Crowdfunding 0.19.0 or later.

New Features

Platform mode (marketplace fee splitting) — Switch PayPal from Direct mode to Platform mode and each pledge is split at PayPal the moment a backer pays: the creator receives their share in their own PayPal account and your platform receives its cut in yours. Built on PayPal for Marketplaces. See Platform mode.
Creator PayPal onboarding — Creators connect their own PayPal account from their dashboard under Account → PayPal, through PayPal’s guided click-through — business or personal accounts, no keys to copy. Their connection status is visible to you in the wp-admin Creators list. See How your creators connect.
Integration-model selector — A Direct mode / Platform mode choice on the PayPal settings page, with a separate Platform-app credential set and its own per-environment connection test. See Choosing the integration model.
Split-or-nothing safety — PayPal is offered on a campaign only when its creator has connected and can actually be paid; otherwise it’s hidden and backers use the other methods. A pledge is never quietly routed to your own account instead of the creator’s. See Split-or-nothing.
Split-aware refunds — Refunding a split pledge reverses your platform’s cut in proportion to the amount returned, so creator and platform each give back their share. See Refunds in Platform mode.

Developer

New event actions — igcf_paypal_split_order_created fires alongside igcf_paypal_order_created for split orders, and igcf_paypal_creator_onboarding_started, igcf_paypal_creator_connected, and igcf_paypal_creator_connection_revoked track a creator’s PayPal connection. See the PayPal developer reference.
Platform-active override — A new igcf_paypal_platform_is_active filter overrides whether the add-on treats Platform Mode as active, for tests and specialized setups. See the PayPal developer reference.
Gateway capability — The gateway advertises core’s new platform_mode capability, so platform-fee and payout add-ons can detect split-capable checkout through Igcf_Payment_Gateway_Service::gateway_supports(). The platform cut rides on core’s application-fee seam. See the PayPal developer reference.

Ignition Crowdfunding v0.18.0

Mon, 20 Jul 2026 00:00:00 GMT

This release polishes the campaign-viewing experience: campaign video now loads only when a visitor chooses to watch, the image-framing tool is more forgiving, and campaign cards are clickable end to end. It also clarifies the email settings, retires the permalink status check, and lays gateway-facing groundwork for premium payment add-ons.

Enhancements

Click-to-play campaign video — When a campaign has both a video and a featured image, the header now shows the image with a play button; the video (and any third-party player and its trackers) loads only when a visitor clicks play. This applies to the campaign page hero and the Featured Campaign block. See Campaign Page.
Easier image framing — The Adjust framing tool now loads the full, uncropped image and lets you click or drag anywhere on it to place the focal point, so subjects near the edges are reachable. See Creating a Campaign.
Clickable campaign cards — In the campaign archive and the Campaign Grid block, the whole card is a link to the campaign, not just the title. See Managing Campaigns.
Clearer email settings — On the Emails settings tab, account-level emails (the Welcome email and the security emails) now show an All recipient badge instead of “Backer,” since they go to the account holder whatever their role, and the admin per-pledge alert explains that each administrator opts in from their own profile. See Email Notifications.

Changes

Permalink status check removed — The Setup tab no longer shows a “Permalink Status” row or a “Fix Permalinks” button. Campaigns resolve correctly under any WordPress permalink structure — including “Plain” — so the check was unnecessary. For cleaner, more shareable links you can still choose a pretty structure under Settings → Permalinks. See Quick Start.

Bug Fixes

Receipt reflects pledge status — Returning to a pledge receipt now shows a heading that matches the pledge’s current state (for example, “Pledge Canceled” for a canceled pledge), and the offline payment instructions appear only while the pledge is still awaiting payment.

Developer

Backer dashboard row seam — A new igcf_dashboard_pledge_row_args filter lets add-ons attach link actions to, or adjust the status label on, each backer-dashboard pledge row. See the Filters Reference.
Abandoned-pledge auto-expiry — An hourly igcf_expire_abandoned_pledges cron cancels stale, unpaid gateway pledges with the payment_abandoned reason; offline pledges are exempt. Tune it with igcf_pledge_expiry_minutes, igcf_pledge_durable_methods, and igcf_pledge_is_expirable, and observe it with the igcf_pledge_expired action. See the Actions Reference and Filters Reference.
Campaign-aware gateway availability — Gateways can declare per-campaign availability via Igcf_Payment_Gateway::is_available_for_campaign(), and checkout validates the chosen method against the campaign-available set (Igcf_Payment_Gateway_Service::get_available_ids() / get_available_gateways()). See the Service Layer.
Refund gateway references — Igcf_Refund_Service::set_gateway_reference() records a gateway’s own refund id on a refund, and gateway_reference now carries a unique index so a duplicate delivery adopts the existing refund idempotently. See the Service Layer.
Removed filter — The unused igcf_has_pretty_permalinks filter has been removed along with the permalink status feature.

Ignition PayPal Gateway v0.1.0

Mon, 20 Jul 2026 00:00:00 GMT

The first release of Ignition PayPal Gateway, a premium add-on for Ignition Crowdfunding. Backers on a direct-mode install can pay online with PayPal or a credit/debit card, and pledges settle automatically. Requires Ignition Crowdfunding 0.18.0 or later and a PayPal Business account.

New Features

Online PayPal payments — Backers pay with PayPal or a card through PayPal’s hosted approval flow, so no card data touches your site. Offered on flexible-funding campaigns. See Ignition PayPal Gateway.
Connect with live and sandbox credentials — Save your PayPal Business API credentials on the Payments tab and verify them with a built-in connection test. The environment is chosen per campaign — test campaigns use sandbox, real campaigns use live — with no site-wide switch. See Connecting your PayPal account.
Automatic settlement — Payments capture and pledges settle automatically once a backer approves, kept in sync with PayPal without polling.
Complete an interrupted payment — A pending PayPal pledge shows a Complete payment action on the backer dashboard, so a failed or abandoned payment isn’t a dead-end. See Finishing an interrupted payment.
Refunds through PayPal — Issue full or partial refunds from core’s refund action; they settle through PayPal to the backer’s original payment method. See Refunds.

Developer

PayPal event actions — The add-on fires igcf_paypal_order_created, igcf_paypal_payment_retried, igcf_paypal_payment_captured, igcf_paypal_payment_failed, and igcf_paypal_payment_refunded so other plugins can react to PayPal payment events. See the PayPal developer reference.

Ignition Crowdfunding v0.17.0

Sat, 04 Jul 2026 00:00:00 GMT

This release refocuses the free core on direct mode — one organization crowdfunding its own projects, where administrators and staff author campaigns. The features for running a site on behalf of outside creators — the campaign creator role, self-service registration, campaign and update moderation, the admin Creators list, and the creator email notifications — move into a new premium add-on, Ignition Platform Mode. Core also gains two new administrator emails and a shortcut from wp-admin into a campaign’s frontend management view.

Platform Mode is now a premium add-on

Everything needed to open a site to independent creators has been re-homed into Ignition Platform Mode:

the non-admin Campaign Creator role and self-service registration,
campaign and update moderation — the review queue, Approve/Reject, and the pending-review and rejected states,
the wp-admin Creators list, and
the creator email notifications (new-backer, approval, rejection, and the campaign lifecycle series).

In a default install, core now runs in direct mode: administrators and staff create and manage campaigns themselves, campaigns publish without a review step, and everyone who signs up is a backer. Activate Ignition Platform Mode when you want the creator role, self-service sign-up, and an approval workflow. See User Roles and Ignition Platform Mode.

New Features

Campaign Ended (admin email) — Administrators are notified when a campaign ends and its result is ready to declare. Part of the Campaign lifecycle admin category. See Email Notifications.
Backer Canceled (admin email) — Administrators are notified when a backer cancels a pledge. On by default, since cancellations are low-volume. See Email Notifications.
Manage on Dashboard — The wp-admin campaign detail page gains a Manage on Dashboard button that opens the campaign’s frontend management view — where you review its pledges and post updates — alongside the existing View and Edit buttons.

Developer

Campaign extension seams — Core now exposes render and decision seams that add-ons build on: the actions igcf_campaign_form_rejection_banner and igcf_campaign_detail_banners, and the filters igcf_campaign_form_submit_button, igcf_campaign_detail_lifecycle_verbs, igcf_determine_initial_status, and igcf_determine_update_status. See the Actions Reference and Filters Reference.
Frontend confinement filter generalized — The former igcf_is_creator_only_user filter is now igcf_is_frontend_only_user, since core confines backers generically rather than a creator role. See the Filters Reference.
Moderation and creator APIs moved — The moderation abilities (igcf/approve-campaign, igcf/reject-campaign, and their update counterparts), the creator role, and the creator email classes now live in Ignition Platform Mode. Code that relied on them in core should depend on the add-on.

Ignition Platform Mode v0.1.0

Sat, 04 Jul 2026 00:00:00 GMT

The first release of Ignition Platform Mode, a premium add-on for Ignition Crowdfunding. It turns a single-owner site into a multi-creator platform: independent creators sign themselves up, run their own campaigns entirely from the frontend, and submit them for review — while administrators keep oversight through an approval queue. Requires Ignition Crowdfunding 0.17.0 or later.

New Features

Campaign Creator role — A dedicated, non-admin role. Creators work entirely on the frontend, never see wp-admin, and can manage only their own campaigns, uploads, and data. See Ignition Platform Mode.
Self-service registration — With Public Campaign Creation enabled, new frontend sign-ups become campaign creators and can start a campaign right away; turn it off to keep sign-ups as backers. See Self-service registration.
Creator dashboard — Each creator gets a Campaigns section listing all of their campaigns, with the right action for each state (Edit, Edit & Resubmit, or Manage). See The creator dashboard.
Campaign and update moderation — Creators submit campaigns and updates for review; nothing goes live until an administrator approves it. A wp-admin queue adds Pending Review and Rejected views, Approve/Reject row and bulk actions, and pending-count badges. See Reviewing submissions.
Rejection feedback — Rejecting requires a reason, which the creator sees in their dashboard so they can revise and resubmit. See Rejection reasons and feedback.
Moderation emails — Creators are emailed on approval and rejection; administrators are notified when a submission is awaiting review.
Creators list — A wp-admin Ignition → Creators screen to review every creator alongside their campaign and pledge activity, with per-creator detail pages, filter views, and search. See The Creators list.

Developer

Frontend roster and confinement seams — The add-on exposes the igcf_dashboard_campaign_actions filter (add per-campaign actions to the creator roster — the seam a companion add-on uses for lifecycle controls), plus igcf_platform_is_creator_only_user and igcf_platform_creator_allowed_upload_mimes for tuning frontend confinement. See the Ignition Platform Mode developer reference.

Ignition Crowdfunding v0.16.0

Thu, 25 Jun 2026 00:00:00 GMT

This release builds out add-on extensibility. Add-ons can now surface their own settings under Ignition > Settings > Add-ons, and new render hooks let them place UI directly on campaign cards and pages. It also polishes the Campaigns and Updates admin screens.

New Features

Add-on settings pages — Add-ons can register their own settings page, which appears under Ignition > Settings > Add-ons and is also linked from the add-on’s row on the WordPress Plugins screen. The first add-on to use this is Ignition Favorites. See Administration → Add-ons.

Enhancements

Cleaner Add-ons catalog — The Add-ons tab no longer lists the internal reference add-on that ships for add-on developers, so the catalog shows only add-ons you would actually install.

Bug Fixes

Steady “Add New” button — On the Campaigns and Updates admin screens, the “Add New” button no longer briefly flashes in its default position before it is relinked to the frontend dashboard.

Developer

Campaign render hooks — Three new actions let add-ons place UI on campaign cards and pages without overriding templates: igcf_campaign_card_media (a card image’s corner), igcf_after_campaign_title (beside the title on single-campaign pages and the Featured Campaign block), and igcf_campaign_progress_stats_end (the end of the progress stats line). See the Actions Reference.
Add-on settings framework — Register a settings page that core surfaces under Settings → Add-ons via the new igcf_addon_settings filter. See Registering Add-on Settings and the Filters Reference.

Ignition Favorites v0.1.0

Thu, 25 Jun 2026 00:00:00 GMT

The first release of Ignition Favorites, a premium add-on for Ignition Crowdfunding. Signed-in visitors can favorite the campaigns they care about and return to them from their dashboard, and you can optionally show an aggregate favorite count as social proof. Requires Ignition Crowdfunding 0.16.0 or later.

New Features

Favorite control — A heart toggle appears on campaign cards and beside the title on single-campaign pages. Signed-in visitors favorite or unfavorite instantly, with no page reload; signed-out visitors are prompted to log in first. See Ignition Favorites.
Favorites dashboard section — A new Favorites section in the frontend dashboard lists every campaign a user has favorited, newest first, with a one-click remove. See Finding your favorites.
Public favorite count — Optionally show how many people have favorited a campaign, inline on cards and as a line on the campaign page. You choose whether it shows always, never, or only once a campaign passes a favorite threshold. See The public favorite count.
Privacy ready — A user’s favorites are included in WordPress personal-data exports and removed when their data is erased.

Developer

Favorite events, REST route, and service API — The add-on fires igcf_favorites_favorited and igcf_favorites_unfavorited on each change, exposes a PUT/DELETE igcf/v1/campaigns/{id}/favorite REST route, and ships the Igcf_Favorites_Service API. See the Favorites developer reference.

Ignition Crowdfunding v0.15.0

Wed, 17 Jun 2026 00:00:00 GMT

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.

Ignition Crowdfunding v0.14.1

Sun, 14 Jun 2026 00:00:00 GMT

A polish release for notices and the admin Campaigns list. Every notice across pledging, checkout, the dashboard, and the sign-in screens now shares one consistent look and reveals itself more gently when it appears, the campaign list now counts pending pledges alongside succeeded ones, and saving a campaign as a draft once again shows its confirmation.

Enhancements

Consistent notices everywhere — Success, error, warning, and informational messages across the pledge form, checkout, the creator and backer dashboards, and the sign-in and registration screens now share a single notice style. Notices also scroll into view more gently, revealing themselves without jumping the page when the message is already close to where you are looking.
Campaign list Pledges count — The Pledges column on the wp-admin Campaigns list now counts pending pledges alongside succeeded ones, so it reflects every active pledge a campaign has taken — including those still awaiting offline payment. The Goal, Pledged, Ends, and Pledges columns also keep their figures on a single line instead of wrapping at narrow widths. See Managing Campaigns.

Bug Fixes

Draft-save confirmation restored — Saving a campaign as a draft returned the creator to a view that could not display the “Draft saved” message, so the confirmation was silently lost. Saving a draft now lands back in the editor and shows the confirmation.

Developer

Canonical igcf-notice notice primitive — All frontend notices now render from one shared primitive: the partials/notice template (rendered in PHP via igcf_render_notice()) and a matching window.igcfNotice JavaScript factory, which emit identical markup. Restyle every notice at once by overriding partials/notice.php in your theme. See the Notices class reference and Template Overrides.

Ignition Crowdfunding v0.14.0

Thu, 11 Jun 2026 00:00:00 GMT

This release rebuilds the wp-admin Campaigns screen around the moderation queue: the list now surfaces only the action each campaign is waiting on, and a new per-campaign detail page gathers every lifecycle action, statistic, and historical record in one place. Three admin-side fixes round it out — clearer status messages, filter links that no longer expire, and a guard against duplicate pledge actions.

New Features

Redesigned wp-admin Campaigns screen — The Campaigns list is now queue-first. Each row shows where the campaign sits in its lifecycle and surfaces only the action that clears it from a moderation queue (approve/reject, announce goal reached, declare result, or close), with everything else moved to a new per-campaign detail page. Open a campaign’s Manage action to reach it: moderation actions, feature and duplicate, stat tiles (pledged, received, refunded, goal, backers, days left), a details table, the five most recent pledges and updates, and a complete status history all live in one place. The list columns were reworked to match (Campaign, Status, Goal, Pledged, Ends, Pledges), and the Ignition > Campaigns menu now carries a badge counting everything that needs attention. See Managing Campaigns and the campaign detail page.

Bug Fixes

Readable status messages in admin notices — After a campaign or update action, the confirmation notice now names the new status in plain language (e.g. “Active”) instead of showing the internal status slug (e.g. “igcf_active”).
Filter links no longer expire — Filtered views of the Campaigns, Campaign Updates, and Pledges lists can now be bookmarked and shared. The read-only status and month filters previously carried a security token that expired, breaking saved links; those filters are now token-free and keep working.
Duplicate actions on the pledge detail page — On a pledge’s detail page, double-clicking an action (record offline payment, cancel, or issue refund) could fire the same change twice before the page reloaded. Every action button now locks while a change is in flight. See Managing Pledges.

Developer

igcf_campaign_detail_sections — A new action hook fires at the end of the wp-admin campaign detail page, after the built-in sections, passing the campaign ID. Echo markup here to add your own section to the page. See Actions Reference.

Ignition Crowdfunding v0.13.2

Wed, 10 Jun 2026 00:00:00 GMT

This release brings full WordPress multisite support, closes the moderation feedback loop — creators now see why a campaign was rejected and can resubmit in place — and lets moderators and campaign authors preview unpublished campaigns on the real campaign page. The funding goal is now required on every campaign, and the admin refund dialog received two fixes.

New Features

Multisite support — Ignition Crowdfunding now runs on WordPress multisite networks. Network-activate it or activate per site; every site gets its own fully independent platform — campaigns, pledges, settings, and roles are all per-site, and new sites added to the network set themselves up automatically on their first visit. See Multisite.
Rejection feedback for creators — When an administrator rejects a campaign, the optional rejection reason now reaches the creator: the dashboard card notes that changes were requested and offers Edit & Resubmit, and the campaign form shows the reviewer’s feedback in a banner while the creator works. Saving changes keeps the campaign in Rejected status — it returns to review only when the creator clicks Resubmit for Review. See Reviewing submissions.
Campaign preview for moderators and authors — Moderators and the campaign’s own creator can now open a Draft, Pending Review, or Rejected campaign’s page and see it exactly as it will appear when published — content, reward tiers, pledge options, and backer list included, with all pledge options rendered display-only. Visitors on a Preview campaign see the same display-only pledge options ahead of launch. See Campaign Page — Previewing non-public campaigns.

Improvements

Funding goal is now required — Every campaign must have a funding goal greater than zero before it can be submitted for review or published (drafts can still be saved without one). Goal-less display variants — progress sections without a goal figure and “keep growing” share copy — have been removed in favor of consistent goal-based presentation. See Creating a Campaign.
Dashboard revenue widget readability — The weekly cash-flow chart now draws received, pending, and refunded amounts on a single shared scale, so bar heights above and below the baseline are directly comparable, and a minimum bar height keeps small amounts visible. The refund band gained its own hover tooltip. See Dashboard Widget.

Bug Fixes

Refund amounts in whole currency units — The refund dialog now asks for the amount in your currency’s major units (e.g. dollars), prefilled with the remaining refundable amount, instead of expecting minor units (cents). Zero-decimal currencies are handled correctly. See Refunds.
Pledge list after a refund — After issuing a refund from the wp-admin Pledges list, the row now refreshes with the authoritative server-rendered state, so the refund chip, net amount, and available actions are immediately correct — and fully refunded pledges no longer offer Issue refund.
Mobile horizontal scroll on the campaign form — A hidden measurement element behind the tags field could stretch to the full form width, adding roughly 30 pixels of horizontal scrolling on narrow screens. The form now fits the viewport.

Developer

Campaign visibility helpers — New helpers formalize the content-visibility contract: igcf_is_campaign_previewer(), igcf_campaign_content_visible(), and Igcf_Campaign_Post_Type::is_pre_publication_status(). See Service Layer — Campaign visibility helpers.
Igcf_Refund_Service::refundable_remaining() — Returns the amount still refundable against a payment attempt, counting pending as well as succeeded refunds. See Service Layer — Igcf_Refund_Service.
Backers REST visibility — GET /igcf/v1/campaigns/{id}/backers now returns a 404 on non-public campaigns unless the requester is the campaign author or holds edit_others_igcf_campaigns. The backer-list setting still takes precedence for every requester. See REST API — Backers.
igcf_activated fires per site — With lazy per-site provisioning, igcf_activated fires whenever a site is provisioned: on activation, on a new multisite subsite’s first load, and after a plugin update brings a site up to date. See Actions Reference.

Ignition Crowdfunding v0.13.1

Thu, 04 Jun 2026 00:00:00 GMT

This release adds an Ignition Crowdfunding widget to the main wp-admin Dashboard, giving administrators a 12-week cash-flow snapshot — received, pending, and refunded — at a glance. It also fixes four issues across checkout, the campaign update form, Better Sharing emails, and reward tag editing.

New Features

Dashboard revenue widget — A new Ignition Crowdfunding widget on the wp-admin Dashboard shows weekly cash-flow over the last 12 weeks, with running Received / Pending / Refunded totals and a per-week bar chart. Each amount lands in the week the money actually moved, so it reads as a true cash-flow view. Visible to administrators only. See Dashboard Widget.

Bug Fixes

Checkout amount precision — The checkout tier amount field no longer drops a trailing decimal zero, so an amount like $25.00 keeps its cents on the pledge page.
Campaign update form controls — The campaign update form now initializes its dashboard controls correctly when opened, so its interactive fields behave the same as the rest of the dashboard.
Sharing email progress bar — The Better Sharing email progress bar no longer shows roughly half-full for a campaign that is at 0% funded; an empty campaign now renders an empty bar.
Reward tags on save — A reward tag typed but not yet committed is no longer dropped when you save; pending tag input is now captured on submit.

Developer

Igcf_Reports_Service — A new read-only reporting service powers the dashboard widget and is a stable seam for reporting add-ons. get_weekly_cashflow() returns per-week received/pending/refunded totals in minor units, anchored on the date money actually moved (COALESCE(processed_at, updated_at) for payments and refunds, falling back to the succeeded-transition time when no gateway settlement date is set). See Service Layer — Igcf_Reports_Service.

Ignition Crowdfunding v0.13.0

Wed, 03 Jun 2026 00:00:00 GMT

This release rebuilds how pledges, payments, and refunds are modelled. A pledge now carries a simple Pending / Succeeded / Canceled lifecycle, while payments and refunds are tracked as their own records behind it — so a refund is finally a first-class thing the plugin understands, shown as a neutral Partial Refund / Full Refund chip beside the status rather than a confusing extra state. Campaign money is split into a public Pledged figure and an internal Collected figure, and administrators now Declare a campaign’s outcome and Announce a reached goal as deliberate actions. The wp-admin Pledges list and pledge detail screens were rebuilt around the new model, with refund issuing, offline-payment recording, and a Net column.

New Features

Refunds — Administrators can issue full or partial refunds against a paid pledge from the wp-admin pledge detail screen. A refund never changes the pledge’s status — the lifecycle badge stays Succeeded and a neutral Partial Refund / Full Refund chip appears beside it, with the net contribution shown alongside. Refunds flow through to the backer’s dashboard, the creator’s pledge list, and the CSV exports consistently. See Refunds.
Pledged vs Collected — Every campaign now tracks two figures. Pledged is the public-facing number on the progress bar (what backers have committed, less any refunds); Collected is the money actually received, and it’s the figure that decides whether a goal is met. For offline-payment campaigns the public bar moves when a backer pledges, while the goal decision waits until payment is recorded. See Campaign Page — Progress bar.
Declare result and announce goal — When a campaign ends, an administrator Declares its outcome (Successful, Failed, or Funded) as an explicit action that sends the outcome emails to backers. A reached goal is Announced the same way. Both are separate from Closing the campaign, and ended-but-undeclared campaigns surface in an Outcome Pending view. See Declaring Campaign Results.
Rebuilt admin Pledges screens — The wp-admin Ignition → Pledges list was rebuilt with status filter chips, a Net column, and per-row actions (record offline payment, cancel, issue refund). The pledge detail screen now shows the full payment-and-refund history with a Pledged / Refunded / Net breakdown and a Refunded total tile. See Managing Pledges.
Refund emails — Three new notifications fire when a refund is issued: one to the backer, one to the campaign creator, and one to administrators (in the per-pledge admin category). See Email Notifications.

Improvements

Simpler pledge statuses — Pledges now use Pending, Succeeded, and Canceled everywhere — on the campaign page, both dashboards, the admin screens, and the API. The old paid and settled states are gone; “money received” is now a single, unambiguous state.
Net-first pledge lists — The backer pledge list and the creator pledges table now show each pledge’s live contribution to the campaign total — the full amount while pending, the post-refund net once succeeded, and $0.00 for a canceled or fully-refunded pledge — so every row reconciles with the progress bar.
Reward slots release on full refund — A fully-refunded pledge releases its limited-quantity reward slot automatically, the same as a cancellation; a partial refund keeps the slot claimed.
Reshaped CSV exports — The admin and creator pledge exports gain a Net Received column and a Cancel Reason column, and the backer export’s per-status pivot now reflects the new lifecycle. See Settings — Admin pledge and backer exports.
Responsive admin tables — The pledge and user-summary detail tables stack cleanly on narrow screens.

Developer

Pledge decomposition — The pledge is now one of three records: Pledge (the backer’s intent), Payment_Attempt (one try at collecting money), and Refund (money flowing back). Each has its own three-state machine, audit log, and three-tier transition hooks (igcf_pledge_*, igcf_payment_attempt_*, igcf_refund_*). A pledge moves to succeeded when one of its payment attempts succeeds — transports never mutate pledge status directly. See Service Layer and Actions Reference — Pledge lifecycle.
New services Igcf_Payment_Attempt_Service and Igcf_Refund_Service — Sibling services for creating, transitioning, and querying payment attempts and refunds, following the existing static-method pattern. Igcf_Pledge_Service gains display helpers (displayed_status(), refund_indicator_label(), status_badge_view()), a combined status log, and net/refund aggregation helpers. See Service Layer.
Add-on seam filters — Eight filters give gateway and fee add-ons their composition points without core knowing about fees: igcf_pledge_amount_to_charge, igcf_payment_attempt_application_fee, igcf_attempt_net_to_creator, igcf_refund_proportional_fee_reversal, plus the registries igcf_pledge_cancel_reasons, igcf_payment_attempt_failure_codes, igcf_refund_reasons, and igcf_payment_methods. See Filters Reference — Pledge lifecycle.
Reworked pledge abilities — igcf/settle-pledge and igcf/confirm-pledge-payment are removed. New abilities: igcf/record-offline-payment, igcf/issue-refund, igcf/retry-payment-attempt, and igcf/mark-attempt-failed; igcf/cancel-pledge now retires the campaign-author branch (creator-side mutation moves to the Creator Controls add-on). Campaigns gain igcf/declare-campaign-result and igcf/announce-goal-reached. See Abilities Reference.
New REST resources — Payment attempts and refunds are exposed read-only at /igcf/v1/pledges/{id}/payment-attempts and /igcf/v1/payment-attempts/{id}/refunds. The pledge response gains displayed_status, net, is_full_refund, latest_attempt, and refund_summary fields. See REST API Reference — Pledges.
New action igcf_campaign_result_declared — Fires from Igcf_Campaign_Service::declare_result() with $campaign_id, $result (successful / failed / funded), and $actor_id; the outcome emails listen here. Its counterpart igcf_campaign_goal_announced fires from announce_goal_reached(). See Actions Reference — Campaign result and goal.
New merge tags — {refund_amount} and {pledge_net} are available to email templates. See Email Notifications.

Ignition Crowdfunding v0.12.0

Fri, 22 May 2026 00:00:00 GMT

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.

Ignition Crowdfunding v0.11.0

Tue, 19 May 2026 00:00:00 GMT

This release unifies the frontend dashboard around a single sidebar navigation — the legacy tab strip and the separate “My Account” view are gone, replaced by one nav landmark that uses aria-current="page" for the active leaf and collapses to an off-canvas drawer on mobile. Reward tiers can now opt in to Requires shipping address, and backers pledging for those tiers fill in a Name + Address + City + Region + Postal + Country block at checkout; the address surfaces on the backer’s pledge detail, on the admin pledge detail, and in the admin Pledges CSV. Settings get a new Setup tab between General and Emails that groups the one-time configuration (permalink check, page assignments, Terms page, Share Buttons install panel) with an attention dot when items still need configuration.

New Features

Unified dashboard navigation — The Creator and Backer Dashboards now share a single sidebar nav with one optional level of nesting. Top-level items (Campaigns, Pledges, Account) appear flat for users who only see them; the Account item expands to its sections (Profile, Email, Password, Notifications, Privacy) for the active user. On screens below 600px the sidebar becomes an off-canvas drawer with a hamburger toggle, focus trap, Escape-to-close, and body scroll lock. The label on every nav item drops the “My” prefix it used to carry. See Frontend Dashboard and Account.
Pledge-scoped shipping address capture — Each reward tier now carries a Requires shipping address toggle. When a backer pledges for a tier that requires shipping, the checkout review screen adds a Shipping Address fieldset (Recipient name, Address line 1, Address line 2, City, State / Region, Postal code, Country). The address persists with the pledge and renders read-only on the pledge detail page, on the wp-admin pledge detail screen, and as seven appended columns in the Export Pledges CSV. See Reward Levels.
Setup settings tab — A new Setup tab sits between General and Emails and groups every one-time configuration item: Permalink Status, Login / Register Page, Dashboard Page, Checkout Page, Terms & Conditions Page, and Share Buttons. The tab label shows an attention dot (Setup •) whenever any of those items still needs configuration, so administrators land on the right page after activation. The remaining knobs (currency, moderation, public creator registration, test campaigns, reward levels, guest checkout, backer list, campaign ending) stay on the General tab. See Settings — Setup.

Improvements

Dashboard footer prompt for first-time creators — The “Start a Campaign” button moves to a single footer row under the campaign list and is preceded by a “Got something to fund?” prompt, so the empty-list state and the populated-list state share the same CTA placement. See Creating a Campaign.
1200px dashboard width tier — The dashboard is now rendered through the new igcf-page-wide block template (1200px constrained, no post-title) so creators have more horizontal room for the campaign list, pledge tables, and shipping address rows. The narrow (480px) and standard (800px) tiers are unchanged. See Page width tiers.
Dashboard layout polish — Detail sub-views now match the dashboard’s page width, section heading rhythm is consistent across Campaigns / Pledges / Account, reward-tier descriptions no longer ship with extra wpautop paragraph margins, account section help text breathes properly under inputs, and notification toggles tighten the vertical rhythm between rows.

Bug Fixes

Dashboard nav hover symmetry — Nav-item labels are vertically centred so their hover backgrounds render symmetrically. (Carried over from the 0.10.0 dashboard work.)
Logout state preserves intent — Logging out from the dashboard now reaches the home page with an igcf_logged_out=1 flag, which triggers a one-shot post-logout flash notice on the next page. Add-ons can rewrite the destination via the new igcf_logout_redirect_url filter.

Developer

Igcf_Dashboard_Nav_Registry — New static registry for dashboard nav items. register_item( $id, $args ) accepts label, priority, capability, callback, template, and parent; nesting is capped at one level (registering a child whose parent is itself a child is rejected via _doing_it_wrong()). get_visible_top_level_items() and get_visible_children( $parent_id ) resolve what the current user can see. The legacy igcf_dashboard_tabs and igcf_account_tab_sections filters are removed; register items through the registry instead. See Service Layer — Igcf_Dashboard_Nav_Registry.
Shipping address surface — New service class Igcf_Shipping provides the field schema (default_field_schema(), get_field_schema()), per-context requirement decision (default_requires_shipping(), requires_shipping()), sanitization (sanitize_address(), find_missing_required()), persistence helpers (get_decoded()), and render helpers (render_read_only(), csv_safe()). The reward-level meta key is exposed as the constant Igcf_Shipping::REWARD_LEVEL_META (_igcf_requires_shipping). See Service Layer — Igcf_Shipping.
New filters — igcf_pledge_requires_shipping ($bool, $context) gates the requirement per-tier per-context, igcf_pledge_shipping_field_schema ($fields) modifies the collected fields, igcf_pledge_shipping_address ($decoded, $pledge_id) rewrites the decoded address on read, and igcf_logout_redirect_url ($url) rewrites the destination of the dashboard’s logout link. See Filters Reference.
New actions — igcf_pledge_shipping_form_fields ($context) fires inside the checkout shipping fieldset so add-ons can render extra fields, and igcf_pledge_shipping_saved ($pledge_id, $persisted_shipping_address) fires from Igcf_Pledge_Service::create() once the address has actually been persisted. See Actions Reference.
Igcf_Pledge_Service::create() accepts shipping_address — Pass a sanitized associative array keyed by the schema field keys; the service JSON-encodes and stores it in the new shipping_address column on wp_igcf_pledges. The Igcf_Pledge data object exposes the raw column as $shipping_address (string or null); decode via Igcf_Shipping::get_decoded( $pledge ) to apply filters.
Reward levels carry requires_shipping — Igcf_Reward_Level_Service::create(), update(), and clone_for_campaign() all read/write the new tier meta. The REST schema for /igcf/v1/reward-levels exposes requires_shipping on read and accepts it on create/update. See REST API — Reward Levels.
Template renames + new block template — The dashboard PHP templates lose their dashboard-my- prefix: dashboard-my-campaigns.php → dashboard-campaigns.php, dashboard-my-pledges.php → dashboard-pledges.php, and the standalone dashboard-my-account.php view is removed entirely (account sections render through the unified nav). A new block template igcf-page-wide (1200px constrained, no post-title) is registered for the frontend dashboard; it is selectable in the block editor as Ignition Page (wide) and adds the igcf-page--wide body class. Theme overrides need to re-sync. See Template Overrides.
Unified nav CSS classes — The .igcf-dashboard__tab* and .igcf-account-subnav* classes are gone. New element classes: .igcf-dashboard__menu-toggle, __menu-toggle-icon, __menu-toggle-label, __nav, __nav-item, __nav-item--active, __nav-item--logout, __nav-subitems, __nav-subitem, __nav-subitem--active, __nav-divider, __content, __scrim; modifier .igcf-dashboard--drawer-open and global .igcf-no-scroll on <body> while the drawer is open. See CSS Classes — Creator dashboard.

Ignition Crowdfunding v0.10.0

Sun, 17 May 2026 00:00:00 GMT

This release adds Test Campaigns — an admin-only mode that runs full pledge flows against an isolated, publicly-hidden campaign so payment gateways and email pipelines can be exercised without polluting real data. The wp-admin Pledges screen gains two CSV exports: Export Pledges (line items, respects filters) and Export Backers (one row per backer × currency, with a per-status pivot). Site owners can now flip a single Public campaign creation switch to keep new registrants on the backer role while leaving the door open to creators. The pledge review screen consolidates its identity section into two clear states — logged-in (with an inline Sign out link and live “Pledging as” preview) and logged-out (equal-weight Guest / Sign in / Register paths) — and the new-user welcome email is now a fully branded HTML message with a working Set-your-password link.

New Features

Test Campaigns — Administrators can duplicate a real campaign as a test campaign ([TEST] … prefix, isolated Test status) or click Add New Test Campaign to start one from scratch. Test campaigns accept pledges through the real pipeline so gateways, emails, and dashboards can be exercised, but they never appear in the public archive and their pledges are excluded from guest- and verification-cleanup aggregates. A new Test Campaigns admin-side toggle hides them from the admin campaign list for admins who don’t want to see them. See Test Campaigns.
Admin CSV exports for pledges and backers — Two new buttons sit next to the H1 on the wp-admin Pledges page. Export Pledges emits one row per pledge (16 columns) and respects every filter on the list — status, campaign, month, search. Export Backers emits one row per (backer, currency) pair with a per-status pivot (15 columns) and ignores the status filter by design so a single CSV captures a backer’s whole picture across Pledged / Paid / Cancelled / Settled. See Settings.
Public campaign creation toggle — A new Public campaign creation field in Settings → General lets site owners decide whether anyone who registers through the frontend lands as a campaign creator (default) or as a regular backer. Existing creators are unaffected; the toggle only controls new registrations. The plugin’s auth form no longer reads the WordPress Anyone can register setting — the Register tab is always available, and the new toggle plus add-on filters carry the policy. See Ignition Platform Mode.
Branded welcome email — New users created through wp-admin → Users → Add New (Backer or Campaign Creator role) now receive a branded HTML welcome email with a working “Set your password” button. The hijacked WordPress-default plain-text email is suppressed for plugin roles and preserved for everyone else. See Email Notifications.

Improvements

Pledge review identity (logged-out) — Logged-out backers now see explicit, equal-weight paths on the review step: a full-width “Continue as Guest” CTA (with inline email entry) when guest checkout is enabled, plus a two-column outlined Sign in / Register row underneath. When guest checkout is off, the email field disappears and only the Sign in / Register row remains. The Register link pre-selects the Register tab on the auth page. See Checkout — Identity section.
Pledge review identity (logged-in) — The “Pledging as” card now shows a Sign out link aligned right of the backer’s name, and the Hide my name checkbox is a live preview of the public backer-list row — toggling it flips the visible name between the backer’s display name and “Anonymous” without a reload. The card no longer displays the user’s email, since it is now a preview of the public row where email is never shown. The Terms & Conditions checkbox was moved to sit directly above the Confirm Pledge button.
Reward levels carry through campaign duplication — The wp-admin Duplicate row action now clones every reward tier — title, amount, quantity limit, one-per-backer flag, featured image, display order, and active/inactive state — with the claimed count reset to zero on each clone. Duplicating no longer produces a draft with no tier structure. See Managing Campaigns — Duplicating a campaign.
Creator dashboard export rename — The creator-side Export Backers button on the campaign detail view is now labelled Export Pledges to match what it actually emits (one row per pledge). The downloaded filename follows the new pattern campaign-{slug}-pledges-{date}.csv.

Developer

New actions — igcf_user_welcome_needed (a new user needs the branded welcome email — fires after WP’s plain-text suppression for plugin roles), igcf_checkout_identity_before and igcf_checkout_identity_after (wrap the entire identity section on the pledge review step). See Actions Reference and Authentication.
New filters — igcf_can_create_campaign (gate the campaign-creation form per-user; create-mode only), igcf_welcome_set_password_url (rewrite the set-password URL embedded in the branded welcome email), igcf_checkout_identity_html (wrap or fully replace the rendered identity section HTML), igcf_admin_pledge_export_columns / igcf_admin_pledge_export_row (admin pledge CSV shape), igcf_admin_backer_export_columns / igcf_admin_backer_export_row (admin backer CSV shape), and igcf_pledge_backer_aggregates_args (adjust the query args for the aggregated-backer query). See Filters Reference.
Filter rename (creator export) — igcf_backer_export_columns / igcf_backer_export_row are renamed to igcf_creator_pledge_export_columns / igcf_creator_pledge_export_row. The creator-side query var ?igcf_action=export_backers is renamed to export_pledges, the nonce action igcf_export_backers_{id} to igcf_export_pledges_{id}, and the underlying class Igcf_Backer_Export to Igcf_Creator_Pledge_Export. This is a pre-release breaking change with no compatibility shim.
Service layer additions — Igcf_Campaign_Service::create() now accepts is_test => bool; when set with edit_others_igcf_campaigns, the new campaign is promoted to the igcf_test status with the [TEST] title prefix. New helpers: Igcf_Test_Campaign::promote(), is_test(), get_test_campaign_ids(), pledge_exclusion_clause(), prefix_with_marker(); Igcf_Pledge_Service::query_backer_aggregates() and build_args_from_request(); Igcf_Reward_Level_Service::clone_for_campaign(). See Service Layer.
REST: is_test on campaign create — POST /igcf/v1/campaigns accepts a top-level is_test boolean (edit context, admin-only). When true, the service-layer guard requires edit_others_igcf_campaigns — non-admin callers receive WP_Error('igcf_test_capability', …). See REST API — Campaigns.
New post status: igcf_test — Custom post status used by the test-campaign isolation layer. Test campaigns are publish-locked at igcf_test; transitioning to any other status is reverted server-side. The status is excluded from public archive queries and visible only to users with edit_others_igcf_campaigns.
New merge tag: {set_password_url} — Available in the welcome email template; resolves to the user’s set-password URL (filtered by igcf_welcome_set_password_url).
Checkout identity BEM consolidation — The three legacy identity-section modifiers (.igcf-checkout__identity--logged-in, --guest, --auth-required) collapse to two (--logged-in and --logged-out). New element classes: .igcf-checkout__identity-row, __display, __signout, __toggle, __guest-path, __email, __email-help, __error, __guest-submit, __divider, __auth-row. Theme overrides of checkout.php need to re-sync. See CSS Classes — Checkout.

Ignition Crowdfunding v0.9.0

Wed, 13 May 2026 00:00:00 GMT

This release brings frontend account management out of wp-admin. Backers and creators now have a dedicated Account tab on the dashboard with Profile, Email, Password, Notifications, and Privacy sections — including one-click unsubscribe and a privacy-by-default toggle. A branded lost-password and reset flow replaces the bare WordPress default email, registration and claim capture first and last names so the backer list can display real names instead of “Guest,” and password fields ship with a strength meter and show/hide toggle. Dashboard tabs were trimmed to drop the redundant “My “ prefix, wrap on narrow screens, and use a per-tab underline.

New Features

My Account dashboard tab — Backers and creators now manage their account from a frontend Account tab with five sections: Profile, Email, Password, Notifications, and Privacy. Privacy defaults to “Hide my name on backer lists” for new accounts, and a logout link sits next to the section nav so no one needs to enter wp-admin. See My Account.
Email change with confirmation — The Email section sends a confirmation link to the new address; the change only takes effect when the link is clicked. Both old and new addresses are notified afterwards.
Frontend password change — The Password section accepts a current-password check and a new password (verified by strength meter), then sends a security-alert email once the change completes.
Notification preferences with one-click unsubscribe — The Notifications section groups transactional emails into toggle-able categories. Every notification email includes a one-click unsubscribe link that flips the matching category off without requiring login. See Email Notifications.
Branded lost-password and reset flow — A frontend Lost password? link on the auth form starts a request flow that sends a branded HTML email. The reset link opens an in-site set-password form rather than wp-login.php. The WordPress-default plain-text reset email is suppressed so users only ever see the branded version. See Lost Password.
First and last name capture at registration and claim — Registration and the guest-claim form now collect first and last name. The backer list displays a real name when one is on file, falling back to “Guest” for unclaimed guest accounts and “Anonymous” for backers who have hidden their name.

Improvements

Password strength meter and show/hide toggle — All password inputs (register, claim, reset, account password change) share a partial that renders a four-step strength indicator and an eye-icon toggle. The password-confirm field was dropped site-wide; the show/hide control covers fat-finger errors.
Mobile account navigation — On narrow viewports the section nav stacks as a vertical list and tapping a section opens it on its own screen with a back link. The desktop layout keeps the side nav + content split.
Dashboard tab polish — Tabs are now labelled Campaigns, Pledges, and Account (the “My “ prefix is gone), they flex-wrap on mobile so all three fit, and the active tab is marked with a per-tab underline.

Developer

New actions — igcf_email_change_requested (a confirmation link was just generated), igcf_email_changed (an email change completed), and igcf_password_changed (a frontend password change completed). See Actions Reference.
New filters — igcf_account_tab_sections (register extra sections on the Account tab), igcf_notification_categories (register extra notification toggles + their email types), and igcf_password_reset_url (rewrite the reset URL embedded in the branded reset email). See Filters Reference.
WordPress-default reset email suppression — add_filter( 'retrieve_password_message', '__return_empty_string' ) is registered so only the branded Igcf_Email_Password_Reset email is delivered when a reset is requested. Add-ons that emit their own reset email should adjust priority accordingly.
Four new security email types — password_reset, email_change_request, email_changed, and password_changed register through the email registry but are locked on in Settings → Emails (they cannot be disabled). Templates live at emails/password-reset.php, emails/email-change-request.php, emails/email-changed.php, and emails/password-changed.php and can be overridden by themes. See Template Overrides.
New overrideable templates — dashboard-my-account.php (account container with section nav), the five account-sections/*.php templates (Profile, Email, Password, Notifications, Privacy), partials/password-field.php (shared password input + strength meter + show/hide), and partials/auth-form-lostpassword.php / partials/auth-form-reset.php / partials/auth-form-confirm-email.php / partials/auth-form-unsubscribe.php for the new auth routes.
New CSS classes — .igcf-account, .igcf-account-subnav (with __item, __divider, __logout), .igcf-account-section (with __title, __help, __form, __field), .igcf-password-field (with __toggle, __strength, __strength-bar, __strength--0 through __strength--4, __strength-label), and .igcf-notifications-toggle (with .igcf-notifications-group and .igcf-notifications-toggles). See CSS Classes.
Dashboard tabs renamed — Tab keys are unchanged, but labels rendered through igcf_dashboard_tabs are now Campaigns, Pledges, and Account. Add-ons that overrode labels via this filter should re-check their assumptions.

Ignition Crowdfunding v0.8.0

Fri, 08 May 2026 00:00:00 GMT

This release tightens campaign presentation end to end. Every campaign now ships with a featured image — either the creator’s own upload or one picked from an admin-curated starter library — and a focal-point control so the same image renders well across the hero, card grid, dashboard, and social unfurls. Built-in og:* meta tags make campaign links unfurl with the right image without needing an SEO plugin. The pledge selection step now lives on the checkout page, two new display blocks (Campaign Grid and Featured Campaign) make it easy to surface campaigns on landing pages, and post-pledge sharing leads with the cause instead of “tell your friends.”

New Features

Required featured image with a starter library — Campaigns now require a featured image to submit or publish. Creators can upload their own or pick from a Starter Images tab in the media frame, sourced from a library admins curate inside the Media Library. See Creating a Campaign and Starter Images.
Focal-point control for campaign images — A new Adjust framing button on the campaign form opens a modal where creators pick the subject of the image. All sized variants regenerate centered on that point so heroes, card grids, dashboard thumbs, and social unfurls all crop sensibly without a designer in the loop.
Built-in social meta on campaign pages — Single-campaign pages now emit the eight og:* tags (type, url, title, description, image, image:width, image:height, image:alt) so links unfurl on Facebook, LinkedIn, Slack, and similar surfaces with the campaign’s hero image and excerpt. Sites running an SEO plugin that emits its own meta keep that plugin’s output via priority ordering.
Campaign Grid and Featured Campaign blocks — Two new display blocks for landing pages: Campaign Grid renders a configurable card grid (count, columns, status, category, tag, sort, featured-only filter), and Featured Campaign renders a single hero in either auto mode (most-funded, ending soon, etc.) or manual mode (specific campaign). Both have matching shortcodes. See Blocks & Shortcodes.
Consolidated pledge + checkout — The pledge amount step now lives on the checkout page itself, rather than a separate page. Tier and Pledge-What-You-Want selection happen there, then transition to the review screen on the same page. The standalone Pledge page setting and igcf/pledge block have been removed. See Checkout.
Plugin block templates and page width tiers — Two FSE block templates ship with the plugin: Ignition Page (narrow) at 480px for auth, account, and checkout pages, and Ignition Page (standard) at 800px for the dashboard. Both drop the post title to avoid duplicate H1s. Single campaign and archive pages render at a wide tier via body classes.

Improvements

16:9 image sizes everywhere — The plugin registers three custom image sizes — igcf-campaign-hero (1200×675), igcf-campaign-card (640×360), and igcf-campaign-thumb (160×90) — and uses them across the single-campaign hero, archive cards, dashboard thumbs, the Featured Campaign block, and the Better Sharing email image. Replaces a mix of medium / large / full requests that produced inconsistent crops.
Cause-first post-pledge share copy — The share section on the pledge confirmation page now leads with the campaign’s goal rather than “tell your friends,” and surfaces a live “amount remaining to goal” sub-line. A new {{ campaign_goal_remaining }} token is also available in Better Sharing templates. See Sharing — Tokens.

Developer

New REST endpoint — POST /igcf/v1/campaigns/{id}/focal-point accepts attachment_id, focal_x, focal_y (0–100 percentages), persists the focal point on the attachment, and regenerates sized variants. See REST API.
New filters — igcf_emit_social_meta (kill-switch for the bundled og:* tags), igcf_campaign_grid_query_args, and igcf_campaign_featured_resolved_id (display block customization). See Filters Reference.
New actions — igcf_before_campaign_grid and igcf_after_campaign_grid wrap the Campaign Grid block render. See Actions Reference.
New image sizes — igcf-campaign-hero, igcf-campaign-card, and igcf-campaign-thumb are registered on after_setup_theme. Themes and add-ons can request these via wp_get_attachment_image_src() or any size-aware helper.
New body classes — Pages assigned the plugin’s block templates render with .igcf-page--narrow (480px), .igcf-page--standard (800px), or .igcf-page--wide (campaign CPT pages). See CSS Classes.
Block template overrides — ignitionwp//igcf-page-narrow and ignitionwp//igcf-page-standard are registered via register_block_template() and can be customized by themes through the standard FSE template editor. See Template Overrides.
Block + shortcode removal — igcf/pledge / [igcf_pledge] are no longer registered. The Checkout block (igcf/checkout) handles tier and PWYW selection in addition to the review screen.

Ignition Crowdfunding v0.7.1

Thu, 30 Apr 2026 00:00:00 GMT

This release reworks the campaign archive’s discovery experience with a streamlined toolbar, a results bar, two new sort options, and an empty state that reflects the current filters. It also fixes a Better Sharing recovery edge case and a long-standing usability issue with number inputs.

Improvements

Archive toolbar overhaul — The campaign archive’s discovery controls are now split into a toolbar (filters + search) and a results bar (total count, Clear filters, sort). Filters and the sort dropdown submit automatically on change, and clearing the search field also resubmits. See Campaign archive.
New archive sort options — Added Most Backers (campaigns with the most distinct backers first) and Closest to Goal (active campaigns ranked by how close they are to fully funded).
Context-sensitive empty state — When no campaigns match the active filters, the archive shows a message that reflects the current context (e.g. prompts to clear filters or broaden the search) instead of a generic “no campaigns found” notice.
Frontend form polish — Archive toolbar form controls now match the rest of the frontend styling, and the native search clear button shows a pointer cursor.

Bug Fixes

Better Sharing recovery from a deleted template — If a Better Sharing template post was permanently deleted (not just trashed), every campaign page render emitted PHP warnings and rendered no share UI. Activation now zeroes out the stale template IDs so they get recreated on the next pass, and the campaign-side renderer short-circuits if the stored ID does not resolve to a valid template.
Silent value mutation on number inputs — Number inputs with non-step values (e.g. a campaign goal of 100.50 against a step="1" input) were silently rounded by the browser when focus moved away. The campaign goal and reward editor amount inputs now use a text input with inputmode="decimal" and validate without mutating the entered value.

Ignition Crowdfunding v0.7.0

Tue, 28 Apr 2026 00:00:00 GMT

This release wires the free Better Sharing plugin into Ignition Crowdfunding, giving creators and backers a share widget on every meaningful surface. New accounts now go through an activation-link verification flow, and guest backers can claim their account from the pledge confirmation email to set a password and unlock their pledge history.

New Features

Better Sharing integration — A new Sharing tab under Ignition > Settings turns share buttons on per location: campaign sidebar (active and preview), the post-pledge confirmation page, the backer’s pledge detail view, and the creator’s dashboard campaign detail view (active and preview). The settings tab includes an install/activate panel when Better Sharing is not yet available, and per-location deep-links to the block layout and the email template Better Sharing uses for “Share via email.” See Sharing.
Campaign tokens in share templates — Better Sharing templates used by Ignition can substitute {{ campaign_url }}, {{ campaign_title }}, {{ campaign_goal }}, {{ campaign_raised }}, {{ campaign_percent_funded }}, {{ campaign_backer_count }}, {{ campaign_description_excerpt }}, {{ campaign_image }}, and {{ site_name }}. See Sharing — Tokens.
Email verification for new accounts — Users who register through the auth form receive a “Verify your email” activation link and must verify before logging in again. The login form, dashboard, and verification page all surface a Resend verification email action when the link expires. See Email Verification.
Guest account claim — Pledge confirmation emails sent to guest backers include a Claim my account call to action. Guests can also request a fresh claim link from the auth form. Setting a password through the activation link upgrades the account, removes the Guest marker, and logs the user in. See Email Verification — Guest account claim.
Daily cleanup for unverified accounts — A new daily cron job removes pending-verification users that have no pledges after 30 days. Accounts with pledges are never removed by this job.

Developer

New action hooks — igcf_email_verified, igcf_account_claimed, igcf_unverified_user_deleted, igcf_sharing_pledge_detail, and igcf_sharing_campaign_detail. See Actions reference.
New filter hooks — igcf_better_sharing_is_installed and igcf_better_sharing_is_active for overriding install/active detection in the Sharing settings panel. See Filters reference.
New scheduled event — igcf_verification_cleanup runs daily and fires igcf_unverified_user_deleted before each deletion. See Scheduled events.

Ignition Crowdfunding v0.6.2

Sat, 18 Apr 2026 00:00:00 GMT

When creators open the campaign form with no tags selected, the Tags field now shows the five most-used public tags as placeholder text. It’s a gentle nudge that surfaces the vocabulary already in use on the site without forcing the creator to pick from a closed list.

Improvements

Popular-tag placeholder in the campaign form — The Tags field on the campaign form displays up to five of the most-used public tags as placeholder text when no tags are selected. The placeholder disappears as soon as the first tag is added. See Creating a Campaign.

Developer

New filter igcf_campaign_form_placeholder_tags — Customize the placeholder tag suggestions shown in the campaign form tag field. Useful for category-aware lists or add-on-driven suggestions. See Filters reference.

Ignition Crowdfunding v0.6.1

Fri, 17 Apr 2026 00:00:00 GMT

The campaign form’s tag field now behaves like a pill-style autocomplete, suggesting existing tags as creators type. Browsers sorting the archive by “Ending Soon” no longer see already-ended campaigns interleaved with active ones, and administrators can again reach any creator’s campaign detail page from the frontend.

Improvements

Pill-style tag input — The Tags field on the campaign form is now a pill-based autocomplete instead of a comma-separated text box. Existing tags surface as suggestions after typing two characters; pressing Enter or comma creates a new tag. A gentle reminder appears if more than ten tags are added. See Creating a Campaign.

Bug Fixes

Ending Soon sort pushed ended campaigns to the end — Previously, campaigns that had already ended could appear interleaved with active ones in the default “Ending Soon” sort. The archive now orders active campaigns first, campaigns without an end date next, and ended campaigns last. See Managing Campaigns.
Admin access to frontend campaign detail — Administrators can again open the frontend campaign detail view for any creator’s campaign, including the backer export action on that view.

Ignition Crowdfunding v0.6.0

Wed, 15 Apr 2026 00:00:00 GMT

Campaigns now send automatic email notifications to creators and backers at every key moment — pledge confirmations, status changes, goal milestones, and published updates. Campaign categories and tags are visible on campaign cards and single pages, with a redesigned archive filter bar. Status-based field locking prevents edits to live campaigns, and terms acceptance is now required on every checkout.

New Features

Email notifications — 18 transactional emails keep creators and backers informed automatically. Backer emails cover pledge confirmation, payment received, campaign succeeded/failed, goal reached, and published updates. Creator emails cover new backers, payment confirmations, campaign lifecycle events (approved, rejected, live, paused, resumed, ended, closed), goal reached, and backer cancellations. Each email can be enabled or disabled individually from the new Emails tab in Settings. See Email Notifications and Settings.
Campaign taxonomy display — Campaign categories appear as overlay badges on campaign cards and as linked metadata on single campaign pages. Tags appear as overlays on cards and as a linked list below the campaign description. See Campaign Page and CSS Classes.
Status-based field locking — Campaign fields are locked once a campaign leaves Draft status, preventing creators from altering live campaigns. Administrators can still edit campaigns in most statuses. The campaign form shows a status-specific message explaining why editing is restricted. See Managing Campaigns.
Admin update restrictions — Campaign updates can only be created and edited from the Creator Dashboard. The wp-admin “Add New” button is hidden, and direct URL access redirects to the dashboard. A new “Post Update” row action on the campaigns list links administrators to the frontend form. See Managing Campaigns — Campaign updates.

Improvements

Archive tag filter — The tag filter on the campaign archive is now a dropdown matching the other filter controls. Only tags attached to published campaigns appear in the list. See Managing Campaigns.
Wizard completion badges — Step badges in the campaign form wizard are now solid notification circles with white numbers, making incomplete steps easier to spot.

Bug Fixes

Campaign tags not saved — Tags entered in the frontend campaign form are now saved correctly. Previously, the form sent tag names but the API only accepted term IDs, causing tags to be silently discarded.
Media preview gap — Empty media preview areas in the update form and reward editor no longer render as blank 200px boxes.
Backer list heading count — The backer list heading now shows the unique backer count instead of the total pledge count, matching the progress statistics.
Terms checkbox shown per transaction — The terms acceptance checkbox now appears on every checkout, not just the first time a user pledges. This ensures each pledge has independent terms acceptance.

Developer

Email system — Extensible email infrastructure with abstract base class, registry pattern, and merge tag engine. 9 filters for customizing subjects, bodies, recipients, and send behavior. Add-ons can register custom email types via the igcf_email_classes_registered action. Email templates are overridable via the theme template system. See Actions and Filters.
Field locking API — Igcf_Campaign_Service::get_locked_fields() returns locked fields by status and role. Filterable via igcf_campaign_locked_fields. See Filters.
Taxonomy display data — igcf_campaign_display_data filter now includes categories and tags arrays. New CSS classes for taxonomy overlays on cards and single pages. See CSS Classes.
Campaign goal reached — New igcf_campaign_goal_reached action fires once per campaign when the funding goal is met. See Actions.
Email templates — 18 new overridable templates in the emails/ directory. See Template Overrides.

Ignition Crowdfunding v0.5.0

Tue, 17 Mar 2026 00:00:00 GMT

Creators can now add reward tiers to their campaigns, giving backers structured pledge options alongside the existing pledge-what-you-want flow. The campaign form wizard gains completion tracking and moves into the Creator Dashboard, eliminating the need for a separate form page. Backer CSV exports now include reward details for fulfillment workflows.

New Features

Reward levels — Creators can define tiered pledge rewards with a title, description, image, minimum amount, and optional quantity limit. Backers select a tier on the campaign page and are guided through a dedicated pledge page before checkout. Campaigns without reward tiers continue to use the existing pledge-what-you-want form directly on the campaign page. Administrators can enable or disable the reward system and control whether a “Pledge What You Want” option appears alongside tiers. See Reward Levels and Settings.
Pledge page — A new dedicated page handles the pledge amount step. When a campaign has reward tiers, backers land here after selecting a tier to confirm their amount (pre-filled with the tier minimum). When both rewards and PWYW are enabled, backers who choose PWYW also use this page. Assign the page in Settings. See Making a Pledge.
Wizard completion tracking — The campaign form wizard now shows completion badges on each step. A checkmark indicates a completed step; a numbered badge indicates an incomplete one. The Review step summarizes which fields still need attention before submission.
Dashboard-embedded wizard — The campaign form wizard is now part of the Creator Dashboard. There is no longer a separate campaign form page, block, or shortcode. Creators access the wizard via “Start a Campaign” and “Edit” buttons in the dashboard. See Creating a Campaign and Blocks & Shortcodes.

Improvements

Edit Campaign button — The campaign detail header now includes an Edit Campaign button, so creators no longer need to return to the campaign list to edit.
Backer export columns — The CSV export now includes 13 columns in a fulfillment-first layout: Pledge ID, Backer Name, Email, Reward Title, Amount, Status, Reward Minimum Amount, Date, Currency, Payment Method, Display Preference, Campaign ID, and Reward ID. See Exporting Pledges.

Developer

Reward Levels REST API — Full CRUD endpoints at /igcf/v1/campaigns/{id}/reward-levels with reorder support. See REST API.
Reward level hooks — New actions (igcf_reward_level_created, igcf_reward_level_updated, igcf_reward_level_deactivated) and filters (igcf_is_reward_levels_enabled, igcf_is_pwyw_with_rewards, igcf_reward_level_editable_fields, igcf_rest_prepare_reward_level). See Actions and Filters.
Pledge page block — New igcf/pledge block and [igcf_pledge] shortcode for the dedicated pledge page. See Blocks & Shortcodes.
Removed campaign form block — The igcf/campaign-form block, [igcf_campaign_form] shortcode, and campaign_form_page_id setting have been removed. The wizard is now accessed exclusively through the dashboard.

Ignition Crowdfunding v0.4.3

Wed, 11 Mar 2026 00:00:00 GMT

Creators can now add a video to their campaign that displays in the hero area instead of the featured image. Site administrators can require backers to accept terms and conditions before pledging. Creators can also export their campaign’s backer list as a CSV file.

New Features

Campaign video embed — Creators can paste a YouTube, Vimeo, or other supported video URL when creating or editing a campaign. The video displays in the hero area of the campaign page, with the featured image as fallback. See Creating a Campaign and Campaign Page.
Terms & conditions acceptance — Administrators can select a terms page in Settings. When configured, a required acceptance checkbox appears on checkout, registration, and guest checkout forms. Users who have already accepted the current terms are not asked again. See Checkout.
Backer CSV export — Creators can download a CSV of all backers for a campaign from the Campaign Detail view. The export includes pledge ID, date, backer name, email, amount, currency, payment method, status, and display preference.

Developer

Terms acceptance hook — New igcf_terms_accepted action fires when a user accepts terms, with the user ID, terms page ID, and form context. See Actions.
Terms requirement filter — New igcf_is_terms_acceptance_required filter to override whether terms acceptance is required. See Filters.
Backer export filters — New igcf_backer_export_columns and igcf_backer_export_row filters let add-ons customize CSV export columns and row data. (Renamed to igcf_creator_pledge_export_columns / _row in v0.10.0 — see Filters.)
Campaign video in REST API — The campaign schema now includes meta.video_url for reading and writing video URLs. The Settings endpoint exposes terms_page_url, privacy_page_url, and terms_acceptance_required. See REST API.

Ignition Crowdfunding v0.4.2

Sun, 08 Mar 2026 00:00:00 GMT

Backers can now pledge without creating an account. Guest checkout lets visitors enter an email address and go straight to the pledge flow — no password, no registration. Campaigns also gain automatic date-based scheduling, transitioning between Preview, Active, and Ended statuses on their own.

New Features

Guest checkout — Backers can pledge with just an email address, no account required. Enable it in Settings and visitors in the pledge flow see a “Continue as Guest” option on the login page. Returning guests reuse their identity by email. See Guest Checkout.
Automatic campaign scheduling — Campaigns now transition automatically based on their dates. Preview campaigns go Active when their start date arrives, and Active campaigns End when their end date passes. An hourly background check handles the transitions. See Campaign Lifecycle.

Improvements

Guest user admin indicator — A “Type” column in the WordPress Users list distinguishes guest users from registered backers. See User Roles.
Dashboard restriction for guests — Guest users see an account setup message instead of pledge history on the My Pledges tab, preventing access to previous pledge data.
Guest orphan cleanup — Guest users who never complete a pledge are automatically removed after 24 hours.

Bug Fixes

Campaign update permissions — Tightened REST API permissions to prevent unauthorized access to non-public campaign updates.

Developer

Guest User Service — New Igcf_Guest_User_Service class with create(), find_or_create(), is_guest(), and cleanup_orphaned() methods. See Service Layer.
Campaign transitions filter — New igcf_campaign_transitions filter lets add-ons register custom statuses and modify the campaign state machine. See Filters.
Guest checkout filter — New igcf_is_guest_checkout_enabled filter to override the guest checkout setting programmatically. See Filters.
Action hooks — Three new hooks: igcf_guest_user_created, igcf_guest_user_deleted, igcf_after_guest_checkout. See Actions.
Cron events — Two new scheduled events: igcf_campaign_check_dates (hourly) and igcf_guest_cleanup (daily). See Actions.

Ignition Crowdfunding v0.4.1

Tue, 03 Mar 2026 00:00:00 GMT

This release adds a backer list to campaign pages — showing who has pledged, how much, and when. Backers control their visibility with an anonymity toggle at checkout and from their dashboard, while administrators can enable or disable the feature site-wide.

New Features

Backer list — Campaign pages display a list of backers with name, amount, and date. Anonymous backers appear as “Anonymous”. Load-more pagination for campaigns with many backers. Admins enable or disable the list in Settings. See Campaign Page.
Anonymity at checkout — Backers can check “Hide my name from the backer list” during checkout to appear as “Anonymous”.
Anonymity toggle — Backers can switch between public and anonymous display from the Pledge Detail view at any time.

Developer

REST API — New public GET /igcf/v1/campaigns/{id}/backers endpoint with pagination. New is_anonymous field on pledge schema. New backer_list_enabled field on settings endpoint. See REST API.
Action hooks — Two new hooks: igcf_before_single_campaign_backers, igcf_after_single_campaign_backers. See Actions.
Filter hooks — New igcf_is_backer_list_enabled filter. See Filters.
Templates — New overridable template: single-campaign-backers.php. See Template Overrides.
CSS classes — New BEM tree for .igcf-campaign-backers. New igcf-campaign-backers script handle. See CSS Classes.

Ignition Crowdfunding v0.4.0

Sun, 01 Mar 2026 00:00:00 GMT

This release introduces the full pledge pipeline — backers can pledge from campaign pages, review at checkout, and track pledges from a dedicated dashboard tab. Campaign creators and administrators manage pledges with a state machine, audit trail, and transition actions.

New Features

Pledge system — Backers select suggested or custom amounts on active campaign pages. Pledges follow a state machine: Pledged → Paid → Settled, with cancellation at the Pledged stage. See Pledging.
Checkout flow — POST-Redirect-GET checkout with review screen, confirmation, and offline payment instructions with configurable placeholders. See Checkout.
Backer dashboard — New My Pledges tab on the Dashboard page lets backers view pledge history, check payment instructions, review status history, and cancel pending pledges. See Backer Dashboard.
Currency system — 20 supported currencies with site-wide selection, formatted display, and minor-unit storage for precision. Configure in Settings.
Campaign progress display — Progress bar showing amount raised, goal, percentage, backer count, and time remaining. Full and compact variants available on campaign pages.
Creator pledge management — Campaign creators view pledges on their campaigns, confirm payments, and settle funds from the Campaign Detail view.
Admin pledge management — Administrators manage all pledges across the site with the same confirm, cancel, and settle actions.
Backer role — New igcf_backer role auto-assigned on registration through pledge context. Grants igcf_create_pledge capability. See User Roles.
Auth context messages — Login/Register page displays context-aware messages when redirected from pledge flow, explaining why authentication is required.

Changed

Settings page expanded — New sections for currency and payment configuration, suggested amounts, pledge limits, offline payment instructions, and a toggle for allowing creators to end their own campaigns. See Settings.

Developer

REST API — New pledge endpoints under /igcf/v1/campaigns/{campaign_id}/pledges for listing, creating, and retrieving pledges. Settings endpoint returns new currency and payment fields. See REST API.
Abilities — Three new pledge abilities: igcf/confirm-pledge-payment, igcf/cancel-pledge, igcf/settle-pledge. See Abilities.
Service layer — New Igcf_Pledge_Service with create, query, transition, and audit trail methods. See Service Layer.
Templates — Six new overridable templates: partials/pledge-form.php, checkout.php, partials/campaign-progress.php, dashboard-my-pledges.php, dashboard-pledge-detail.php, dashboard-campaign-pledges.php. See Template Overrides.
Action hooks — ~15 new hooks for pledge lifecycle, pledge form, checkout, campaign progress, and admin pledges. See Actions.
Filter hooks — ~20 new filters for pledge data, form customization, checkout, currency, and dashboard extensions. See Filters.
CSS classes — New BEM trees for .igcf-pledge-form, .igcf-checkout, .igcf-campaign-progress, and .igcf-status-badge. New stylesheet and script handles. See CSS Classes.

Ignition Crowdfunding v0.3.0

Mon, 23 Feb 2026 00:00:00 GMT

This release overhauls the plugin’s backend architecture. Business logic moves into a dedicated service layer, a full REST API replaces most AJAX endpoints, and state-transition actions use the new WordPress Abilities API. The frontend JS is migrated from jQuery.ajax to wp.apiFetch. User-facing behavior is unchanged.

New Features

REST API — Full CRUD endpoints under igcf/v1 for campaigns, campaign updates, and settings. See REST API Reference.
WordPress Abilities API — 11 registered abilities for campaign and update state-transition actions (approve, reject, pause, resume, end, close, feature, withdraw). See Abilities Reference.
Service layer — Igcf_Campaign_Service and Igcf_Update_Service classes extract business logic from handlers into reusable, testable services. Add-ons can call these directly.
Timezone-aware dates — New igcf_is_future_date() helper uses wp_timezone() for correct status transitions when the site timezone differs from UTC.

Changed

Frontend JS migrated from AJAX to REST + Abilities — campaign-form.js, dashboard.js, campaign-list.js, and update-list.js now use wp.apiFetch instead of jQuery.ajax. All four scripts declare wp-api-fetch as a dependency.
Minimum WordPress version raised to 6.9 — Required for the Abilities API. See Installation.
AJAX handlers removed — Campaign moderation actions (igcf_campaign_approve, igcf_campaign_reject, etc.), update CRUD (igcf_update_create, igcf_update_edit, igcf_update_delete), and update moderation (igcf_update_approve, igcf_update_reject) are replaced by REST + Abilities. The auth form AJAX endpoints (igcf_login, igcf_register) and campaign duplication are unchanged.

Bug Fixes

Fixed partial update edits unintentionally removing existing thumbnails.
Fixed campaign status mismatches near midnight when site timezone differs from UTC.

Developer

REST API — igcf/v1/campaigns (CRUD), igcf/v1/campaigns/{id}/updates (CRUD), igcf/v1/settings (read-only). See REST API Reference.
Abilities API — 11 abilities across 2 categories (igcf-campaigns, igcf-updates). See Abilities Reference.
Service classes — Igcf_Campaign_Service (create, update, delete, transition_status) and Igcf_Update_Service (create, update, delete, moderate).
New action hooks — igcf_campaign_before_delete, igcf_campaign_deleted. See Actions Reference.
New filter hooks — igcf_rest_campaigns_query_args, igcf_rest_prepare_campaign, igcf_rest_pre_insert_campaign, igcf_rest_prepare_update. See Filters Reference.
Removed hooks — igcf_campaign_form_before_submit, igcf_campaign_form_after_submit, igcf_campaign_form_validation_failed, igcf_campaign_published, igcf_campaign_form_submit_redirect, igcf_campaign_form_validation — these were part of the AJAX form submission pipeline that no longer exists.
Localized data changes — ajaxUrl and nonce removed from igcfCampaignForm, igcfDashboard, igcfCampaignList, igcfUpdateList. Scripts now use wp.apiFetch for authenticated requests. See Blocks & Shortcodes Reference.
Architecture guide — New doc/architecture.md in the repository documents the three-layer pattern (service → REST/Abilities → JS).

Ignition Crowdfunding v0.2.0

Sat, 14 Feb 2026 00:00:00 GMT

The second release of Ignition Crowdfunding brings a full-featured creator dashboard, campaign updates, and a searchable campaign archive — along with significant developer extensibility improvements.

New Features

Creator Dashboard — Frontend dashboard where campaign creators can manage their campaigns, post updates, and track progress without ever accessing wp-admin. Includes a My Campaigns list with quick actions (Pause, Resume, End Early), a campaign detail view, and campaign updates management. Place it on any page with the Creator Dashboard block or [igcf_dashboard] shortcode.
Campaign Updates — Creators can post, edit, and delete updates from the dashboard. Updates display publicly on the single campaign page with a count indicator. Administrators can moderate updates from wp-admin.
Campaign archive search, filter, and sort — Visitors can search campaigns by keyword, filter by category, and sort by newest, ending soon, or most funded.
Placeholder images — Campaigns without a featured image display a branded placeholder throughout the archive and dashboard.
Date constraints — Campaign form validates start and end dates with both client-side and server-side enforcement.
Creator restrictions — Campaign creators are confined to the frontend. Their media library is scoped to their own uploads and restricted to image files only.
Permalink status check — Settings page displays permalink status with a one-click fix button when pretty permalinks are not enabled.

Enhancements

Image insertion — The campaign form now uses a dedicated Insert Image button that opens the media library filtered to images only, replacing the generic Add Media button.
Minimum requirements — Now requires PHP 8.2 and WordPress 6.7.

Bug Fixes

Fixed broken image display when editing campaigns with inline images.
Fixed media upload failing for creators on the frontend campaign form.

Developer

New templates — 13 new overridable templates for dashboard views, campaign archive filters, and update display. See Template Overrides for the full list.
New action hooks — 25+ hooks for campaign archive, single campaign, dashboard, and updates. See Actions Reference.
New filter hooks — 25+ hooks for archive, dashboard, creator restrictions, and updates. See Filters Reference.
New stylesheet handles — igcf-dashboard and igcf-update-list. See Stylesheet Overrides.
New block — Creator Dashboard block with corresponding [igcf_dashboard] shortcode. See Blocks & Shortcodes.

Ignition Crowdfunding v0.1.0

Wed, 11 Feb 2026 00:00:00 GMT

The first release of Ignition Crowdfunding — a free, open-source WordPress crowdfunding plugin.

New Features

Campaign creation form — Frontend form with title, description, goal, funding model (flexible/fixed), start/end dates, featured image, categories, and tags.
Campaign lifecycle — 8-status state machine: Draft, Pending Review, Rejected, Preview, Active, Paused, Ended, Closed.
Campaign moderation — Optional admin approval workflow. Creators submit for review; admins approve or reject with feedback.
Campaign archive and single templates — Public archive page at /campaign/ and individual campaign pages with status display.
Template override system — Override any plugin template from your theme (child theme → parent theme → plugin fallback).
Frontend authentication — Login and registration form with AJAX handling. New users receive the Campaign Creator role.
Admin campaign management — Custom list table with status-based views, row actions (approve, reject, pause, resume, end, close, feature, duplicate), bulk actions, and quick edit.
Admin dashboard — Overview page under the Ignition menu.
Settings page — Configure campaign form page, login/register page, and moderation toggle. One-click page creation buttons.
User roles — Campaign Creator role with scoped capabilities. Administrator role extended with full campaign management capabilities.
Gutenberg blocks — igcf/campaign-form and igcf/auth-form server-side rendered blocks.
Shortcodes — [igcf_campaign_form] and [igcf_auth_form] equivalents.
Custom taxonomies — Campaign categories (hierarchical) and campaign tags.
Internationalization — Full i18n support with ignition-crowdfunding text domain.
Action and filter hooks — Extensive hook system for extending campaign form, lifecycle, templates, admin, and authentication.