WordPress 2.0.6 update

January 10, 2007

in Geek stuff, Internet matters, Security, Writing

Only WordPress administrators are likely to care much about the following.

I have upgraded www.sindark.com to WordPress 2.0.6. This is a fairly important security fix, so anyone running their own WordPress setup should take the time to install it. It seem like only yesterday that I was upgrading to 2.0.5. Now, I am working on www.papaflyfilms.com, and the nsn section. You can expect some downtime on all the WP administered pages I run across this evening. That’s the annoying thing about running multiple sites: you need to go through the whole process three times. Please report any bugs that crop up on any of the sites I run.

Version 2.0.6 can be downloaded here. And here are the instructions for the upgrade (remember to backup first).

[Update: 8:50pm] Papa Fly Productions is back online. If you find any trouble with it, please report the issue.

[Update: 9:05pm] nsn section updated. Everything seems to be live and kicking. I feel just like Dr. Tran.

PS. WordPress 2.1 is being released on or around the 22nd of this month. It will be annoying to have to perform a major upgrade during term time; hopefully, all my plugins will be happy to go along for the ride and it won’t hurt any of my themes. If you want to participate in the development process. Have a look at this.

Report a typo or inaccuracy

{ 2 comments… read them below or add one }

Anonymous January 12, 2007 at 7:12 pm

Higher Beings
Mortal Humans
Playful Primates
Large Mammals
Marauding Marsupials
Adorable Rodents
Flappy Birds
Slithering Reptiles
Crawly Amphibians
Flippery Fish
Slimy Molluscs
Lowly Insects
Crunchy Crustaceans
Wiggly Worms
Multicellular Microorganisms
Insignificant Microbes

Milan January 16, 2007 at 12:41 pm

Looks like they have already gone to WordPress 2.0.7.

Leave a Comment

You can use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

{ 2 trackbacks }

Previous post:

Next post: