Multisite
Ignition Crowdfunding is fully compatible with WordPress multisite. Every site in a network runs its own complete, independent crowdfunding platform.
Why run crowdfunding on a network
Section titled “Why run crowdfunding on a network”A single crowdfunding site works well when one team runs one program. Multisite is for organizations that need several distinct platforms but want to maintain only one WordPress installation:
- Chapters and regions — A nonprofit can give each regional chapter its own site with its own campaigns, backers, and currency, while the network administrator maintains one codebase, one update cycle, and one host.
- Departments and schools — A university or school district can let each department or school fundraise under its own banner, with its own moderators, without any of them seeing another’s pledge data.
- Brands and clients — An agency or umbrella organization can host a separate platform per brand or client, each with its own theme, pages, and settings.
The common thread: the audiences, the money, and the people who manage them are separate, but the software shouldn’t have to be. Because every site is isolated, each one decides independently whether to moderate campaigns, whether to allow guest checkout, which currency to use, and who its administrators are. A choice made on one site never affects another.
Activating on a network
Section titled “Activating on a network”Both activation styles are supported, with no extra setup steps in either case:
- Network activation — Activate once from Network Admin → Plugins to enable the plugin on every site in the network.
- Per-site activation — Leave the plugin network-deactivated and activate it from Plugins on just the sites that need it.
Each site sets itself up automatically the first time it is visited after activation: user roles, database tables, default settings, and scheduled tasks are created for that site. There is nothing to run manually, and adding a new site to an already-activated network works the same way — it provisions itself on its first visit.
Plugin updates follow the same pattern: after an update, each site brings itself up to date automatically on its next visit. There are no network-wide upgrade screens and no command-line steps.
What is per-site
Section titled “What is per-site”Everything. Each site in the network is a self-contained platform:
| Per site | Notes |
|---|---|
| Campaigns and updates | Including categories, tags, and the campaign archive. |
| Pledges, payments, and refunds | Each site’s financial records live in that site’s own database tables. |
| Settings and pages | Moderation, currency, pledge limits, guest checkout, and the page assignments for the dashboard, login, and checkout — all configured per site. |
| User roles | The Campaign Backer role is granted per site. |
User accounts are shared across the network — that is standard WordPress multisite behavior — but a user’s roles and activity are per-site. The same person can be a backer on one site and an administrator on another, and their pledges only ever appear on the site where they pledged.
There is no cross-network aggregation in the core plugin: no network-wide campaign archive and no combined reporting across sites.
Removing a site or the plugin
Section titled “Removing a site or the plugin”- Deleting a site from Network Admin removes that site’s crowdfunding data along with the rest of the site.
- Deleting the plugin runs the full cleanup on every site in the network. See Uninstalling for exactly what is removed.