We configure how plugins and themes are managed across your multisite network — network-activating what should apply everywhere, restricting what individual subsite admins can activate themselves, and cleaning up inconsistent activation across subsites that accumulated without central coordination.
Network-wide plugin & theme management
Plugin and theme activation brought into one consistent, intentional policy across the network.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to your network admin dashboard
- Confirmation of which plugins and themes should be network-wide versus subsite-optional
- Confirmation of what level of control individual subsite admins should have
This or something else?
| You want network-wide plugin and theme activation and access managed consistently | This fix covers it |
| A specific plugin isn’t multisite-compatible and is causing errors, not just an activation management question | Worth describing the specific issue directly — likely a diagnostic fix rather than a management configuration task |
| You want to set up the network itself, not manage plugins on an existing one | Multisite network setup & configuration, the prerequisite step |
| You want user roles synchronised across the network, a related but distinct concern | User role sync across network |
What we do
- Confirm your desired plugin and theme management structure
- Network-activate what should apply across every subsite
- Configure subsite-level access appropriately, restricting or allowing activation as specified
- Clean up inconsistent activation across existing subsites to match the intended structure
- Verify each subsite functions correctly under the new management structure
- Document the plugin and theme management policy for future reference
What is included
- Network-wide plugin and theme management configured to your specification
- Cleaned-up, consistent activation across existing subsites
- Appropriate subsite-level access controls
- A written note on the management policy
Not included
- Fixing an individual plugin’s own multisite compatibility issues, a separate, diagnostic fix if that’s discovered
- Setting up the network itself, if not already done
- User role synchronisation across the network, a separate, related fix
- Ongoing management as new plugins are added over time
Questions about this fix
What's the benefit of network-activating a plugin versus letting each subsite activate it individually?
Network activation ensures consistency and reduces the management burden of individually maintaining the same plugin across many subsites, though it does mean every subsite gets it whether or not they'd otherwise choose to.
Can I let subsite admins install their own plugins, or should that be restricted?
This is a genuine trade-off between subsite autonomy and centralised control and security — we can configure either approach, or a hybrid, depending on how much you trust and want to empower individual subsite administrators.
What happens if I network-activate a plugin that's not compatible with multisite?
This can cause errors or inconsistent behaviour across the network, which is why we'd verify compatibility before broadly network-activating anything, rather than assuming every plugin works identically across a network as it does on a single site.
Will this clean up plugins that are currently activated inconsistently across my subsites?
Yes, bringing existing subsites in line with your intended, consistent structure is part of this fix, not just configuring the policy going forward.
Can different subsites have genuinely different plugins if that's what I actually want?
Yes, this fix can accommodate a structure where some plugins are network-wide and others are optional per subsite, based on what you specify rather than forcing complete uniformity.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.