Wordpress Upgrade 'Fail'

Wordpress 2.8.2 fixes a XSS vulnerability introduced in v2.8.1. Since I don't want to be vulnerable, I did the automatic upgrade from within the admin panel.

The proces, which worked so far since v2.7, hung after approximately 30 seconds. After that the only responds I got was:

"Briefly unavailable for scheduled maintenance. Check back in a minute."

It took about 10 minutes to start feeling a bit uncomfortably. The upgrade failed somewhere along the line. At least so it seemed. Searching Google I found this link. It seems that removing the .maintenance file in the Wordpress blog root removes the message and should (re)start the upgrade automatically.

Guess what? It did. So kudos to the developpers for creating failsaves in the upgrade engine.

Internal Server Errors

I've been experiencing some 500 errors on my blog (HTTP Error 500 - Internal server error). During these occasions, the SymCAImport tools seems to work fine, while the Wordpress installment hogs. So PHP screw-ups are less likely.

A brief conversation with the support department @ Dreamhost, suggested a Wordpress theme/plugin malfunction. So I downloaded the latest theme version, and deactivated most plugins. Let see how long thing keep working.
Anyone other ideas?

UPDATE: Got additional information from Dreamhost about the 500 errors. It seems that there was a 'naughty' person clogging up the cluster/server resources.

Move To Hosting Provider

When you're reading this it will mean that I've moved my website to an external hosting service. This has some drawbacks:

• The SymCAImport tool will be available through another URL (http://symcaimport.redelijkheid.com /symcaimport/). I also editted all previous posts with the old SymCAImport URL.
• Some other services will also be moved to other locations. More on that when they are up and running.

The advantages are a more reliable uptime, and faster up- and download speeds.

There might be some things I might have missed in the transfer. Leave a comment if you find errors or strange behaviour on the website.

UPDATE: I forgot the MIME type settings on the SymCAImport tool. If you did encounter problems importing, you might wanna try again. Sorry for the inconvenience.

Wordpress 2.6.1 Fixed the Permalink Bug

The highly anticipated Wordpress version 2.6.1 is finally released. This version fixes the permalin bug I reported on earlier.

Upgrading was a piece of cake (I think). First gonna check all the plugin functionalities......

There Goes My Traffic

Last week I reported that the upgrade to Wordpress 2.6 didn't go as planned. Well, the upgrade went fine, but it seems that there's a permalinks bug. The 'old' URL's won't work, so I have to cope with a "?p=449" notation of the links to my posts. A direct consequence of this is that everybody using a search engine to find stuff on my blog ends up on my website, but not on the page with the actual article.

From over 600 pageviews per day a week ago, there's a small 40 a day left :-( .

It may be that the new Wordpress 2.6.1 Beta 2 solves this issue, but it may also break other things. Let's hope they release the next (working) version yesterday.

Major Wordpress 2.6 Bug

A couple of days ago I upgraded to Wordpress v2.6. After the upgrade I opened the blog, and added a new post. Both of those actions worked properly.

After the upgrade I noticed a major decrease in comment and trackback spam. But today I discovered the real reason why comments AND page views were close to zero.

There's a bug in Wordpress 2.6 where the permalinks are not working correctly. If you're using permalinks with the date, name, etc. (e.g. /index.php/switched-to-mac/) you get a 'Not Found' error. A definite WTF moment.

When you change the permalinks setup in the wordpress admin pages to default the pages/posts are accessible again. It seems that the issue is known and will be fixed in Wordpress 2.6.1. Untill then, most of the Google search results which end up on my website will result in a 'Not Found' error.

I would go back to an earlier version if I could. After the upgrade (which I thought that worked correctly) I removed the 2.5 installment... Yet another lesson for the future.

UPDATE: the pageviews are returning to normal :)

Upgrading is Getting Easier

Normally I would be planning a Wordpress update/upgrade, because I have made several changes to some core files. Just to make life a little easier (mostly mail related).
But this time, I had about ten minutes to spare, and 'what the heck.., why not upgrade this minute?'.

Well 3 minutes later everything was up and running again (I even upgraded PHP to a more recent version in the same timeframe). Either I'm getting better at this, or upgrading has been made much easier :)

UPDATE: there's also 'some' improvement on catching commentspam. Before the upgrade I had about 20-30 comment/trackback spams in my Aksimet queue. But since the update the queue remains empty :-)

All Comments Held For Moderation....

Ever since I upgraded to Wordpress 2.5 I had to moderate every comment posted on this blog. Note that I hadn't turned this on in the Wordpress settings.

Some research showed that it might have to do something with 'older' plugins. After a trail and error period I found out that the WP Hashcash plugin was to blame. Ever since I de-activated it, the problem seems to be gone.

Wordpress v2.5 Upgrade

Today, I upgraded to Wordpress 2.5. The upgrade proces was easy as usual. Before the upgrade I checked all the plugins used, and upgraded those first. The new features / layout of the adminpages are great. Also the new editor works like a charm (even on Safari). Somehow it feels a bit more intuitive.

Only downside is that the Wordpress Stats on the dashboard won't work in FireFox. It works fine in Safari. Instead of showing the graph in FireFox it shows the actual dasboard page from wordpress.com.