
Originally Posted by
DrByte
That's why we always advise to do your upgrade in a testing area, separate from the live website, first. Then once you've tested everything, including payment handling, you can apply the upgrade to the live site. This results in almost no downtime for the customer and avoids emergencies such as you're posting about today.
A proper "downgrade" would be the following steps:
a) delete the new version from your server
b) restore all the files for the old version, from your backups
c) restore the database for the old version, from your backups.
Done.
Naturally, downgrading a live site by going back to backups will result in losing any data added to the database since the last backup. Yet another reason why testing in a staging area is smart.
Bookmarks