It never fails me, no matter how “easy” I try to make the wordpress upgrades with SVN and supllying my own repos there’s always something that goes wrong.
This time when setting up my sites with my own wordpress repo that I apply updates to I mistakingly overwrote the wp-contents folder, taking it out of checkout and then resulting in the svn update to bomb when it got to that folder.
It shouldn’t have been a big deal, just delete the folder or rename it then do another update. Well I ended up running some of the update.php scripts prior to noticing the problem and the upgrade when bad. I’m not sure how they became related but my guess is there were some files in the includes or the admin folder that weren’t included.
I ended up having to restore two dbs, including this one and rerunning the script (again) after a proper checkout. Argg, and I also had to stay up this late messing around when I should be sleeping.
I’m going to suggest that the wordpress devs include a force upgrade script, since that would have alleviated the restores. I wonder what and where get_option(‘db_version’) checks or is it something else I could have reset to force the reinstall.
If you ever get an error like this,
$ svn import /home/user/repos/new file:///home/svn/repos/default/ -m “initial”
svn: Unable to open an ra_local session to URL
svn: Unable to open repository ‘file:///home/svn/repos/default’
after an svn import it’s because, like me, you’re lame. The syntax is wrong and should look like this,
$ svn import /home/svn/repos/default/ file:///home/user/repos -m “initial import”
Notice the source is first then the repo you want to import to. Doh!
After finally setting up Trac and SVN on my new server I’ve moved all my projects off Google Code hosting. But instead of checking in all of the code to the new repositories I updated all of the theme and plugin pages. So the problem, you’ll not be able to download anything until tonight when I get around to updating the repositories. Unless you just want to head over to GCode (link above) where all the latest versions are, plugins don’t count.
Currently I’m planning to keep all of my plugins on extend but if it’s a major plugin like Search Everything I’m making a trac project to make it easier to manage. I’ll be able to do betas there too. Linking plugins to wordpress.org’s extend is almost a requirement now if you want any kind of good exposure or you want to be involved with automatic plugin updates whenever wordpress roles that feature out.
All of my themes will have it’s very own trac project, e.g. iScattered. I had thought Google Code was going to work best but after all the work of getting trac and svn installed and thinking about manageability of two project homes I deleted had to break off of GC.
This whole week I wanted to post about each theme; describing what changed or didn’t change, a showcase almost while updating their project homes and pages at the same time but it didn’t work out since I had to migrate servers Tuesday. I’m going to push it off, hopefully next week will work out but either way the code will be up soon and if you can’t wait just go here.
My scheduled SVN update worked this morning so I don’t have to worry about upgrading to WordPress 2.2.1 but you might if you haven’t already; it’s a required update.
And the update reminds me it’s time to upgrade everyone’s repository from 2.1 on my server. … Read More »
June 21
I already posted about using the technique of updating wordpress through SVN but it just dawned on me that the instructions I (and many others) used committed us to the 2.1 trunk. And since 2.2 is a few weeks away I’m thinking of how to transition.
If your running a few sites, the easy way would be to just run these commands:
svn switch --relocatehttp://svn.automattic.com/wordpress/branches/2.1/\http://svn.automattic.com/wordpress/branches/2.2/
Not that big transition since I can control who gets the updates and who doesn’t just in case 2.2 doesn’t play well. If I don’t use the above steps I’ll just copy my nightly script and simply modify it with the above command to run a single update for everyone in a few seconds.
The other option would be to use the wp trunk rather than the stable release repositories.
http://svn.automattic.com/wordpress/trunk/I’m not to keen with the latter but it is an option.
Just finished setting up all the blogs I host to update wp using SVN. What a relief it is to have all those installs up-to-date and knowing I’ll never have to manually update them again. I went ahead and setup a cron to run a daily update so from now on my site will be updated before we even here of the new release.
I needed to figure out how to download the K2 theme from the SVN repository and I knew there was a better way then just right-click>save as. So I looked around and found out it’s extremely easy on OS X.
First step, install SVN:
Second Step, Check to see if SVN works.
If you have an output like: Type ’svn help’ for usage. Then svn is working correctly.
If /usr/local/bin is not in your path, edit your .profile and add a line like the following:
export PATH=$PATH:/usr/local/bin
Then open another Terminal window and try again with: svn [enter]
Step 3, use SVN. The best way is to use SVNx.
For K2 I used http://getk2.com/svn/ as the path and named it whatever.
3. Double click on the created SVN Repository and you’re now connected.
4. To download the files from the SVN just click “SVN Checkout”.It is that easy.
I have the rest of the tutorial on it’s own page.
