Comments on: How To Upgrade WordPress Using Subversion

By: PiterKokoniz

PiterKokoniz — Tue, 07 Apr 2009 23:13:23 +0000

Hello ! ;)
I am Piter Kokoniz. oOnly want to tell, that I like your blog very much!
And want to ask you: will you continue to post in this blog in future?
Sorry for my bad english:)
Tnx!
Piter Kokoniz, from Latvia

By: RaulBaztpo

RaulBaztpo — Sat, 28 Mar 2009 22:30:19 +0000

Hello!
Very Interesting post! Thank you for such interesting resource!
PS: Sorry for my bad english, I’v just started to learn this language ;)
See you!
Your, Raiul Baztepo

By: Kudungga

Kudungga — Thu, 11 Sep 2008 13:38:10 +0000

thanks a lot for sharing. Good luck for you

By: Tarun Kumar

Tarun Kumar — Sun, 17 Aug 2008 21:53:09 +0000

Excellent article. one question is.
How do i get database updates using subversion upgrade of wordpress?

By: Kelly

Kelly — Tue, 12 Aug 2008 07:31:37 +0000

Great post here.
Automatic Upgrade plugin allows that it automatically upgrade wordpress installation following official instructions listed here. It performs tasks: backing-up database, plugin deactivation, downloading latest wordpress version, upgrading files/database, etc all automatically.

By: Stephen R

Stephen R — Thu, 07 Aug 2008 01:55:01 +0000

Very nice. Clear and straightforward. I had tried to do this previously, but the insistence in other documentation that you must name the directory “trunk” just made it too hard.

Two questions:

1) Is there any way to tell it _not_ to update Akismet? I don’t use that, and really don’t need it in my plugins directory.

2) If I wanted to use SVN to track my own plugins separately within an SVN install of WordPress, how would I set that up? Maybe another article??? :) (Pretty Please?)

P.S. — You have two separate “subscribe to comments” buttons — one in the form and one below it.

By: David

David — Wed, 06 Aug 2008 21:51:53 +0000

See, that period at the end of the command, that’s why it is important. Without it, you get the issue you are having with it creating its own directories inside of where you already are.

Also, I have used that exact command on over 40 blogs, so the error you received, I can’t replicate. The URL does exist. Did you put a space between the end of the url and the period?

By: James D Kirk

James D Kirk — Wed, 06 Aug 2008 17:39:25 +0000

I now believe the challenge I was experiencing has to do with “where” I was typing in that “period”. There is a space between the end of the svn URL and the period, yes? That seemed to be the cause of my challenges, and when I entered the space, the download stayed in the directory I was working in.

Please let me know if this sounds about right! Thanks.

By: adam

adam — Wed, 06 Aug 2008 17:16:58 +0000

It’s mentioned in the body of the article that the WordPress guide to setting up WordPress via Subversion is lacking – it only shows you how to install trunk. I agree that the guide that was linked to in the body of the article is lacking especially if you’re new to Subversion.

In looking back I did notice that at the bottom of the article under “More Resources” there is a link to the guide I linked to so I apologize for not seeing that. While the Codex guide may not be as extensive (read have as much text) it is a good guide and there is something to be said for brevity.

By: Kiltak

Kiltak — Wed, 06 Aug 2008 10:31:46 +0000

The guide is nowhere as extensive and doesn’t cover all the possibilities. Please note that the link to the article you mentioned is already in the text.. (maybe you didn’t readit all? :) )

By: Luca Gervasi

Luca Gervasi — Wed, 06 Aug 2008 07:57:10 +0000

I love the automated plugins update in wordpress 2.6. What about an svn client to update wordpress in the same way we use to the plugins?

It would be great :)

By: James D Kirk

James D Kirk — Wed, 06 Aug 2008 07:18:50 +0000

Okay, here’s what I did, you tell me where I’m going wrong:
No problem getting svn installed on my SliceHost server.
I create the “public_html_new” directory; no challenges.
Made sure I surf the command line to that new directory and check out the trunk by typing exactly the line you state above, only to receive an error that the URL does not exist.
I check out the SVN page at WordPress.org and it has no “period” that you’re stating is important, so I try the URL with no period.
It works (and it works with or without the trailing slash).
The challenge, however is that it downloads a copy of WordPress and puts it into a directory called “trunk”!
And I did the same with the /tags/2.6/ and it created a directory called “/2.6/” (imagine that!)

So, what to do? Now I should move all up one directory, which shouldn’t be a problem, but I’m concerned when I do an update that the files will get put in to a folder one directory below “public_html”, and having to move them all manually kind of defeats the purpose.

Otherwise I really am excited to learn about this. Thanks for any info you can share on this!