Ignition Platform Mode v0.4.0

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.