Updating best practices

You are here:
Estimated reading time: 1 min

There are two known truths:

  • nobody likes dealing with updates;
  • software has bugs.

Such as many powerful extensions out there, Rey may also contain bugs that were shipped into an update. These bugs can be caused by refactoring a component, a feature addition to an existing component or even a small “fix” that turned out to only cover a few scenarios.

The main rule here is that bugs are prioritised for fixing into the upcoming update. This is good to know but it doesn’t solve the problem of dealing with the bug until the update.

That’s why it’s best to try any of these:

Run a backup

Before running an update you can create a backup of your site. There are powerful tools such as WPVivid or Updraft.

If the update is faulty, you can restore the files (not necessarily the database too) .

Also, most web-hostings have some sort of automatic backup mechanism so it’s best to check that out too.

Create a Clone/Staging site

Basically clone your site with tools such as All in one Migrate plugin or create staging with WP Staging .

If an update is faulty, just report the bug and that’s it. The live site will not be affected at all.

It may seem a bit of extra work, but it’s better to cross fingers and spend time trying to restore the site.


Rollback the update. Specifically for Rey, you can access Rey’s dashboard and just select the version to rollback to eg: https://d.pr/i/4gEIeK .

For other plugins, you can use a plugin such as WP Rollback .

Was this article helpful?
Dislike 0
Views: 497

Suggest article improvements

Please use this form to suggest improvements and report missing or outdated content. Support requests will most likely not be answered and it's best to use the Support Request Form instead. Thanks!