Make WordPress Core

Opened 13 years ago

Closed 13 years ago

#7899 closed defect (bug) (fixed)

WXR file as backup for upgrade process

Reported by: RanYanivHartstein Owned by:
Milestone: 2.7 Priority: normal
Severity: normal Version:
Component: Administration Keywords:
Focuses: Cc:


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.

Attachments (2)

7899.diff (928 bytes) - added by MichaelH 13 years ago.
Suggesting a different article to link. to and a change to the text.
7899_2.diff (1.0 KB) - added by MichaelH 13 years ago.
Doing away with a somewhat redundant link--but not too sure I coded that correctly!!!

Download all attachments as: .zip

Change History (11)

#1 @jacobsantos
13 years ago

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.

#2 @ryan
13 years ago

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


#3 @RanYanivHartstein
13 years ago

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.

#4 @MichaelH
13 years ago

+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.

#5 @ryan
13 years ago

Fine. Remove button and replace with link to Backing_Up_Your_Database.

#6 @ryan
13 years ago

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

#7 @ryan
13 years ago

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

13 years ago

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

#8 @ryan
13 years ago

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

13 years ago

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

#9 @ryan
13 years ago

  • Resolution set to fixed
  • Status changed from new to closed

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

Note: See TracTickets for help on using tickets.