We map which plugins depend on or interact with each other — useful before removing or replacing a plugin, when it’s not obvious what else on the site actually relies on it, or as groundwork before a larger plugin consolidation project.
Plugin dependency & interaction map
Plugin dependencies mapped before you remove or replace one.
- 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 the site’s code and active plugin list
- Confirmation of any specific plugin you’re considering removing or replacing, if that’s what prompted this
- Your preferred report format
This or something else?
| You want to understand how your plugins depend on or interact with each other | This fix covers it |
| You’re experiencing an active plugin conflict right now, not mapping dependencies proactively | Worth describing the specific conflict directly — a diagnostic fix instead |
| You want your theme’s custom code documented, not plugin dependencies | Theme & codebase documentation generation |
| You want a general plugin and theme inventory with rationale for why each is used | Plugin & theme inventory with rationale, in the Documentation & Handover category |
What we do
- Review active plugins and how they interact
- Identify dependencies (one plugin relying on another) and potential conflicts
- Map these relationships clearly
- Flag anything unusual or risky found along the way
- Compile findings into a written report
- Recommend caution points if you’re considering removing a specific plugin
What is included
- A map of plugin dependencies and interactions
- Flags for anything unusual or risky
- A written report
- Recommendations if you’re considering a specific removal
Not included
- Resolving an active, current plugin conflict — a separate, diagnostic fix
- Removing or replacing any plugin — a separate, related fix once you’ve reviewed this map
- An inventory with rationale for why each plugin is used, a different, related document
- Ongoing updates as plugins change
Questions about this fix
Why would I need this before removing a plugin?
Some plugins are relied upon by others in non-obvious ways — removing one without knowing this can break unrelated functionality, which this map is specifically meant to reveal beforehand.
Is this the same as the plugin and theme inventory with rationale?
No — that document explains why each plugin is in use; this maps technical dependencies and interactions between them, a different, more technical focus.
Will this catch every possible interaction?
We map what's technically discoverable through code and configuration review — a genuinely obscure or undocumented interaction could still exist, though this significantly reduces that risk.
Is this worth doing even if I'm not planning any changes right now?
It's most valuable when you're actually planning a change — as a purely proactive exercise with no planned action, the value is more modest.
Will you tell me which plugins are safe to remove?
We'd flag genuine dependency risks for anything you're specifically considering, though the final decision to remove something remains yours.
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.