Recently i’ve noticed a lot of posts from users, complaining about their website running into problem after updating the WordPress to the latest version.
Let’s say i have a website with a lot of custom functions and codes, which depends on the current core to run. The functions are too many to watch, maybe 30 or more, and WordPress is releasing update every once in a while.
So, how can i leave the auto update to ON and be sure that this feature won’t break my Blog? I know i can make backups regularly, but this is not an actual salvation.
The path notes may be helpful, but still, on custom templates it’s a pain to check it every time an update is release.
Now what are my choices? Do i have to turn the auto update OFF and backup / update manually? Or is there a way / plugin / etc. to prevent such things from happening?
5 Answers
A website is just like any other software product, any change need to go through QA stage first, no matter how trivial it might seem. This is why you should always test all updates on a staging/dev server before pushing it to production.
As always it comes down to a question of ROI. Simple blogs can suffer down time for days while a fix is being work on, while sites that generate 1000$/hour probably less tolerant to hiccups, and the time invested in proper QA to avoid it is totally worth it.
So it is your judgment call in the end of how bad will it be for you if an update will break you site. If you value your time in lets say 40$/hr and the site generates 5$/hr, it is just not worth it for you to have a 3 hours QA cycle on the bi-monthly update release (not official but this is the real life rate), especially if you don’t have any bad hacks in your code and it should in theory be “future prof”
