Ticket #494 (new enhancement)

Opened 10 months ago

Last modified 10 months ago

Alternative method to upgrade blogs

Reported by: hovenko Assigned to: somebody
Priority: normal Milestone:
Component: component1 Version:
Severity: normal Keywords: has-patch
Cc:

Description

If your server, for some reason, refuses to call the URLs for each blog you are updating, then it could be nice to get a list of all the URLs.

Then you can list them in a script and execute it from your workstation.

Attachments

wpmu-upgrade-site.patch (1.6 kB) - added by hovenko on 11/08/07 14:15:34.
Added possibility to list all URLs to execute with curl.

Change History

11/08/07 14:15:34 changed by hovenko

  • attachment wpmu-upgrade-site.patch added.

Added possibility to list all URLs to execute with curl.

11/08/07 14:15:56 changed by hovenko

  • keywords set to has-patch.

11/16/07 11:54:24 changed by donncha

Interesting, but can you add paging to the patch. Any wpmu blog with more than a handful of blogs will display a huge list of commands!

11/19/07 13:49:11 changed by hovenko

I disagree. If I was upgrading 500 blogs, each page displayed 50 commands, then I would have to browse through 10 pages, copy and paste them into a shell script and then execute the script. This takes much longer time than just copying and pasting once.

A better solution would be to provide a download-link to download the shell script, getting rid of that copy/paste stuff all together, but this just provides a workaround for those (not so many) times where the webserver can not call on itself (for example because of firewall vs. loadbalancing scenarios).

(follow-up: ↓ 5 ) 11/23/07 17:58:42 changed by momo360modena

Hum, make a "mu-plugin" for this *specific* feature ?

(in reply to: ↑ 4 ) 11/24/07 01:33:29 changed by hovenko

Replying to momo360modena:

Hum, make a "mu-plugin" for this *specific* feature ?

That would give two entry points to basically the same feature (since there are no sensible hooks on the upgrade page).

11/24/07 01:34:49 changed by hovenko

Another note:

The patch should probably be rewritten when integrated (or sometime later), because it makes, as an example, the same SQL query as the original upgrade rutines.

A good change to the original upgrade code would be to display errors when calling the following line:

@$client->fetch($siteurl . "wp-admin/upgrade.php?step=1");

When using the original upgrade rutines, I got no errors and thought everything was OK, but the blogs were not upgraded at all (and nothing strange in the logs!).