Instead of disabling the conflicting plugins outright, can some variable or option be set, notifying the plugins of the conflict? That way, an author could disable the part(s) of his plugin that conflicted but let other parts continue working.
If there are, say, two Facebook plugins – one providing login and one providing syndication – they wouldn’t both try to add data to the header, and could potentially share other data.
Maybe an administrator could even select which of the conflicting plugins should provide the feature in question.
I love the idea of this plugin, and think it’s something that could really help keep people from reinventing the wheel so often in plugins.
- The topic ‘[Plugin: Plugin Dependencies] conflict management idea for "Provides"’ is closed to new replies.