What is this?
Because my own Plugin Elements use System Events that other Plugins might use, I made a resolver that helps to alleviate this. It works quite well and fixes conflicts that could arise with Priorities on installation, uninstallation and update. This is a cooperative effort, so it requires that authors and users be willing to analyze and disclose what priorities may be necessary to allow the user to just install and go, rather than tool around with before actually getting it to work.
What makes this resolver so useful is that it tracks what is installed in the known list. The file is managed on GitHub. It makes sure that your Plugin has a Priority based on what is installed only. On uninstallation, it resolves correctly, adjusting the other Plugins in the list, if they are installed.
Official Page:
on GitHub Pages
Repository:
FuzzicalLogic/PluginCompatibilityList/
Adding your Plugins
If you would like to add your plugins to the list, instructions are included. Fork the repo, add them to the proper place, then make a pull request detailing your addition. You may also
message me with the System Events and Plugin Names (not addon).
Unfortunately, adding the resolver is not necessarily as simple, unless you are using
MyComponent to make your build scripts. The process is dependent on how you build your Transport Package.
Add-Ons that use this Resolver
Final Note
This is by no means an official solution, and unfortunately, there is no way for the MODx Team to automatically know what priorities must be set for Plugins to be compatible with each other. My own extras all use this resolver, but it only has entries that I know have created conflict.
[ed. note: fuzzicallogic last edited this post 14 years ago.]
