Possibly due to a lack of clarity in the pages on the silverstripe.org pages, outlined below, developers are getting into trouble with the interoperability of supported modules. An example could be an expectation that advanced-worklfow will work out of the box with Fluent because they are both listed as commercially supported modules.
Clarify that commercially supported doesn’t mean a promise of interoperability between Modules (update the supported module definition page).
Similarly, a recipe doesn’t promise compatibility with another recipe. We should identify areas to make this clear.
Call out the supported modules that have “high impact on system” in their readme. Being high impact means using this module will have broad implications on the relationships between other modules and how you model data. Technical assessments needs to be made when using high impact module with another high impact module - all module features are not tested for compatibility. Could include:
Overview
Possibly due to a lack of clarity in the pages on the silverstripe.org pages, outlined below, developers are getting into trouble with the interoperability of supported modules. An example could be an expectation that advanced-worklfow will work out of the box with Fluent because they are both listed as commercially supported modules.
https://www.silverstripe.org/software/addons/silverstripe-commercially-supported-module-list/ https://www.silverstripe.org/software/addons/supported-modules-definition/
Considerations