Comments on: Upgrading Multiple WordPress Installations

By: Josh

Josh — Sat, 20 Feb 2010 04:51:23 +0000

I considered going to MU but sometimes, on rare occasions, I have to hack apart the WordPress core. This would have been a disaster on MU, because it’s already a disaster on WP classic. Thanks for the comment.

By: ArtDeco

ArtDeco — Sat, 20 Feb 2010 04:47:09 +0000

This becomes an important topic if you have more than a handful of sites running wp. I went to wpmu a while ago because of the upgrade problem, but this is a better solution. Also if you use a common theme framework, you only have one main theme to upgrade. Now for those pesky plug ins ..

By: Josh

Josh — Sun, 07 Feb 2010 22:17:42 +0000

This is the method they suggest in order to create the SVN repository for an existing wordpress install. In the future, you just need to do an upgrade. I didn’t particularly love the way they did it, but it does preserve everything in case you make a boo-boo, which I am rather prone to doing.

As for A2P, If I don’t have my license.txt in the root of the website, the whole blog goes down. It cost me a lot of money during 2.9.1 when I had stuff down for a couple of days because I didn’t know this. I’ll have to try moving the license.txt to the plugin root.

By: audax

audax — Sun, 07 Feb 2010 07:58:24 +0000

Is creating the new folder and then copying/renaming really necessary? In my experience, if you modify any files locally and then checkout the repository in the future, your modified files will not overwritten.

Also, the license.txt for both A2P and every version of WFR should go in the plugin’s folder. Never any need to put it in the root.

By: Tom

Tom — Sun, 07 Feb 2010 04:36:08 +0000

This is excellent.

By: Joshua

Joshua — Sun, 07 Feb 2010 02:19:55 +0000

Good stuff – I was the one that PM’d you yesterday about it… Will try to get it into action in the coming days.