I usually only use renamed copies of snippets distributed along with a MODx release to avoid overwrites of well tested and working snippets. Usually I do not intend to replace those unless i need at least some of the functionality that had been added in a newer version.
Lately I have been thinking though that some (core) snippets however use external includes using fixed paths which makes this a little harder (Ditto, Wayfinder, Maxigallery and probably more). This takes all the gained upgrade safety away and could even introduce a conflict between older snippet code (after all i call my renamed copy everywhere) and updated include files.
Isn’t this a bit of a bad practice? I imagine it would be possible and maybe a better alternative the include directives and files should be made version dependent. Maybe other approaches would also be possible.
Anyone agrees/disagrees/has ideas on this? I’d be interested in reading them.
-
MODX Staff
- 10,725 Posts
Yes, total isolation of the core and add-ons is coming, as well as packaging that can handle configurable path locations for installing dependent files.
