Given the issues raised previously regarding installations of MODX 2.3.x:
I can see that there are many other 2.3.x issues besides. Not least the 2.3.x Extras Compatibility List not necessarily being a true reflection of an Extras compatibility. If an Extra is broken at the management end, the end user compatibility is quite frankly irrelevant as it will be a house of cards ready to collapse at any time.
I'm not convinced either that it is safe to simply blindly ignore Extra installation errors.
This whole exercise has raised the issue, in my view, of it clearly being necessary to set up (ideally) a 3-tiered system incorporating Development, Testing and Live platforms to avoid this sort of scenario in future. Does anyone already have such a system setup in place? If so, how was this achieved?
In addition I am wondering if there is any change management facility within MODX to provide an audit trail of
all changes made to the MODX system - both management and end user changes. With any database backend solution where users, be they end users or management users, are entering data mistakes will always be made. Has anyone implemented such a system?
Also what would be the best approach for a backup strategy given a MODX system incorporating several additional external MySQL databases?
Lastly, I feel given it would be advisable as with other software developers to offer both stable and development versions as download options. The Extras Compatibility List should also be simplified using something like a traffic light system so that it is evident what the true compatibility status is.
In order for full compatibility to be met the Extra should have to be thoroughly tested both from the management and end user perspective. The matter of compatibility should also be incorporated into the Package Management system so that users are aware at the time of installation of any potential issues.
Any advice would be greatly appreciated.