> The biggest task that takes the most time is FTPing ALL the files up to our server. We don't have direct access to our server, and nor do we have shell access so we have to FTP ALL the files up. This is what takes the most time.
With my cart I must take the rubble road. That takes time.
> I can imagine having direct access to the server would help immensely, but we don't have that.
I hear a different strory from collegues who commute by car.
> But again, the manual process of copying blocks, plug-ins and filter and laborious and prone to human error.
Yes, shouldering the cart wheel is laborious and cause fatigue.
> I understand that there is no direct comparison to WP due to size, but I wanted to mention it because it is fully automatic, and what I would prefer to see is a more automatic basis in doing the upgrade.
You mean something like Google cars? How autonomous is your cart?
> If we didn't have to FTP all the files up, and instead have the upgrade file set come from a Moodle resource (just like WP does), and then also not have to manually re-add all the added blocks etc, then the we would be happy to do an upgrade each time - but currently, because of the time it takes, and the manual approach, then we look at upgrades as a risk.
Kind of convoluted, sorry.
Just a side question: Have you heard of Git? Pardon! That is something for the automobile branch!