Record known combinations
Maintain conflict rules for plugins your team encounters. Keep a reusable explanation of the concern so operators can understand the warning before they choose a maintenance action.
Plugin conflict rules
Give your team a shared set of rules for reviewing incompatible plugins, redundant roles and combinations that need closer attention.
Illustrative client site
THE ORBIT DESK
An inventory tells you what is installed. Conflict rules help explain which combinations warrant investigation. Orbit evaluates the site stack against known relationships and agency rules, making concerns visible in the context of the client website rather than leaving them in a teammate’s memory.
Maintain conflict rules for plugins your team encounters. Keep a reusable explanation of the concern so operators can understand the warning before they choose a maintenance action.
Use functional roles to spot tools performing similar jobs. A possible overlap is a prompt to inspect configuration and client needs before removing or replacing anything.
Find affected installations and compare the warning with active plugins, versions and agency standards. Keep the decision with a person who understands the site.
Rule-based warnings identify known relationships. They do not test every runtime interaction or guarantee that a plugin combination is compatible.
Keep exploring
Connect this capability with the rest of your website maintenance workflow.