WXR file as backup for upgrade process

[RanYanivHartstein]

In WordPress 2.7, before performing an upgrade, users are urged to backup their stuff. This is great.

Immediately after recommending a backup, users are offered to do a "Backup" of their blog using the WXR format. This is not great.

The WXR format is far from a comprehensive backup - and using it is no substitute for backing up the database and entire WordPress directory.

Putting the backup button right there in the upgrade screen will make 99% percent of the users think that they actually have a full backup of their blog - and thus never actually do a real backup.

I recommend the current backup button either be replaced with a proper backup function, be properly disclaimed to make sure users are aware that they are not backing up substantial portions of their blog, or simply be removed entirely.

[jacobsantos]

This should be discussed on wp-hackers first. Secondly, you have two suggestions in there. Right now, I think it is fine. The main concern is the files, where most of the problems will be is copying. That is done, then the upgrade is finish, which is quick.

You are correct that the WXR should be extended to be a full backup and I plan on working on that in 2.8, however that would be a feature and not a defect. The defect is that the user expects the backup to be full and it is not.

[ryan]

We can disclaim and suggest doing a phpMyAdmin backup as well with a link to:

​http://codex.wordpress.org/Backing_Up_Your_Database

[RanYanivHartstein]

I think it would also be best to remove the "Backup" button from the upgrade, replacing it with a link to the "Export" page. Having a button labeled "Backup" right there on the page is too much of a call to action, and would just be too tempting.

[MichaelH]

+1 for removing the button if it does not produce a COMPLETE backup of the user's data and files. The Button is misleading and is going to upset users if they depend on that backup and find out it isn't a complete set of data. Imagine using that backup because you decide to revert to a previous version...just wear a flak jacket when you visit the forums to answer those questions.

-1 for the disclaimer route--how would it be phrased--"Here's the Backup button, but it's not really a backup upon which you should depend!"

+1 for a statement explaining that before proceeding with the upgrade, the user should backup both their data and their WordPress files (including images/uploads), with links to the appropriate Codex articles.

[ryan]

Fine. Remove button and replace with link to Backing_Up_Your_Database.

[ryan]

(In [9253]) Link to codex for instructions on backing up the blog instead of suggesting export. see #7899

[ryan]

Replaced button with a link to codex. The text could use some rewording if anyone wants to clean it up.

[MichaelH]

Suggesting a different article to link. to and a change to the text.

[ryan]

(In [9258]) Link to better codex article for backups. Props MichaelH. see #7899

[MichaelH]

Doing away with a somewhat redundant link--but not too sure I coded that correctly!!!

[ryan]

(In [9279]) Update backup link. Props MichaelH . fixes #7899