Best practices for updating data base
More and more, I am recommending hosts like WP Engine, Get Flywheel, and Site Ground because of their good performance, security, backups, and a one-click staging environments.
Pretty soon, all of these things add up, and the cost of setting these things up manually versus taking advantage of the service makes more sense.
To better match your local environment to the live, hosted environment, many developers use Vagrants — virtual development environments. It costs .95 (or .95 if you use my short-time discount code of Winter2016).
With Desktop Server, you can quickly create a local replica of your hosted site, test your updates, make note of or fix issues, then repeat the process on your live site.
Many people offer maintenance plans to help you stay up to date.
The problem with some of these plans is that they offer weekly, monthly, or quarterly updates.
Changelogs will clue you into whether a major update has been made or simply minor bug or admin interface fixes as in these two examples: Every developer uses different numbering system, so this is not a fault-proof guide, but it can help inform you of major revisions you should approach with caution.
That approach does not work due to the need for timely updates in the face of a security vulnerability.
Those updates need to happen asap, not on a pre-determined schedule.
This upgrade broke compatibility with many third-party plugins, and completely changed how the Next GEN plugin functioned, too.
There were many bugs in this release, so people waited to upgrade or rolled back to the 1.9.13 version.2.0.7 – Many bug fixes.