Ignition Crowdfunding v0.13.2

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.