Suggestion: option to backup database and files before upgrading WordPress

[Xavier Borderie-2]

Ever since WP 2.7, we've been able to upgrade WP in a more-or-less
reliable way - depending on the host, and with the hope of not
breaking themes, plugins, etc.

These last issues have been the main reason why lambda people do not
feel like upgrading, and would rather risk being attacked
(unknowingly) than consciously break their theme.

It would be great of the upgrade mechanism would take the time to make
a local backup of the main database table and the changed files, and
present the user with an interface letting her quickly get back to the
previous version, at the click of the mouse.

Getting people to upgrade is getting hard for people too attached to
their customization (theme, plugins...). Having this would let them
drop that fear, and upgrading while knowing they can eventually get
back if need be.

Do you think there's enough meat in there to create a ticket in Trac for WP3.0?

--
Xavier Borderie
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[scribu]

A rollback mechanism was discussed in a dev-meet in September I think.
Don't know if there's a ticket for it alreay or not.

--
http://scribu.net
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Xavier Borderie-2]

Aah, "rollback", that's the keyword I couldn't remember while writing
that long explanation. Would've saved me a couple paragraphs :)

And thus, there's a ticket already:
http://core.trac.wordpress.org/ticket/10666
...albeit it didn't get much traction.

I'd vote for changed from "Future Release" to "3.0". Other projects
implement it already, it would be a shame to see WP lag behind.

-x.


2009/10/27 scribu <scribu@...>:

> A rollback mechanism was discussed in a dev-meet in September I think.
> Don't know if there's a ticket for it alreay or not.
>
> --
> http://scribu.net
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

--
Xavier Borderie
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[William Canino]

> And thus, there's a ticket already:
> http://core.trac.wordpress.org/ticket/10666
> ...albeit it didn't get much traction.

Would such a "rollback" be a simple full-folder-restore +
full-database-restore?  I ask because (a) not all upgrades change the
database schema and (b) what if the existing version is Billy
Strayhorn?

It'll be sweeeeet if WP can rollback a borked 3.0 upgrade back to 1.0.


2009/10/27 Xavier Borderie <xavier@...>:

> Aah, "rollback", that's the keyword I couldn't remember while writing
> that long explanation. Would've saved me a couple paragraphs :)
>
> And thus, there's a ticket already:
> http://core.trac.wordpress.org/ticket/10666
> ...albeit it didn't get much traction.
>
> I'd vote for changed from "Future Release" to "3.0". Other projects
> implement it already, it would be a shame to see WP lag behind.
>
> -x.
>
>
> 2009/10/27 scribu <scribu@...>:
>> A rollback mechanism was discussed in a dev-meet in September I think.
>> Don't know if there's a ticket for it alreay or not.
>>
>> --
>> http://scribu.net
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers@...
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
>
> --
> Xavier Borderie
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[scribu]

On Thu, Oct 29, 2009 at 9:48 AM, William Canino <
william.canino@...> wrote:

> It'll be sweeeeet if WP can rollback a borked 3.0 upgrade back to 1.0.
>

I don't think you'll be able to do that unless you were running 1.0 before
doing an automated upgrade (?) to 3.0 directly.

Come to think of it, if this rollback gets implemented in 3.0, you'll get to
use it only from 3.0 onwards.


--
http://scribu.net
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Xavier Borderie-2]

> Would such a "rollback" be a simple full-folder-restore + full-database-restore?

I don't know how simple it'd be, but yeah, at best it would create a
local backup of the database+files (or only the database
changes+changed files ?). One click and you're done.
Combined with the existing import/export tools, it would make a
top-notch backup function.

See how another great blogware is doing it:
http://fr.dotclear.org/blog/post/2009/10/22/Du-nouveau-dans-les-versions-de-d%C3%A9veloppement


> Come to think of it, if this rollback gets implemented in 3.0, you'll get to
> use it only from 3.0 onwards.

Obviously.
Which is to say, such tool would let you rollback to any version that
was installed since when the rollback tool was available.
So, if it makes it to 3.0, then it'd be 3.0 onward.



--
Xavier Borderie
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers