WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#15640 closed enhancement (invalid)

Installer to archive changed pages during upgrade

Reported by: nonegiven Owned by:
Milestone: Priority: normal
Severity: major Version: 3.1
Component: Upgrade/Install Keywords:
Focuses: Cc:

Description

Yes, I know, it is the user's responsibility to back up and that they are warned ... BUT ...

Suggestion:

the installer should backup changed pages during the upgrade process and zip them into an archive to be saved on the server and/or downloaded during the process according to the admin's preference.

Let's face it, we all get caught out at some point.* It is worse for newcomers.

I always thought phpBB3 upgrader was the benchmark in this department showing you the changes, and allowing you the choice to merge or overwrite during its upgrade process.

(* NB 3.0.2 makes changes that wipes out simple customizations as I have just found out on a demo site!)

Change History (2)

comment:1 @demetris5 years ago

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

WordPress only replaces files that you are not supposed to edit.

When you want to modify or extend WP you should use the methods offered by the Plugin API:

http://codex.wordpress.org/Plugin_API

Then your modifications are separated from the core files and keep working upgrade after upgrade.

If you have a case that is not catered for by the Plugin API, you can always open a ticket and suggest an addition or improvement.

comment:2 @nacin5 years ago

  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.