Curious how others handle doing upgrades after they've put code customizations in place.
 
The current upgrade process is to just copy files over your existing installation.
 
A question for the Moo folks:  Would it be possible to get a git patch file for the upgrade instead of just a huge ZIP file of the current state?
 
 
Applying this patch might have some of its own issues, but it would be nice as it would make clear what things are changes as far as the upgrade goes and I wouldn't have to manually investigate/distinguish which "changes" are really just older code that I have implemented customizations around.
 
Is there any guidance from Moo on this sort of situation?  Surely there are times when Moo has done custom work for folks and that runs the risk of being overwritten upon upgrade.
 
Super interested to hear how others might be solving this problem.
Comments (1)
ketkew  
Our network does have a lot of customizations. Currently it is really hard to apply a new moo version, because indeed every single custom feature needs to be re-implementend AFTER the upgrade is done.. We do this on a separate dev site to test first before go live. Write down each custom feature and test it one by one. Moo helps to re-implement the custom features, but they do not log which features are custom (our experience). So you need to check yourself what has been done custom, provide th...  more
No login
Login or register to post your comment
Cookies on mooCommunity - Social Networking Script.
This site uses cookies to store your information on your computer.