Incident during Upgrade
Thursday, June 1st, 2006 | WordPress
Tags: WordPress
WordPress announced an upgrade today, so I proceeded with the upgrade. After overwriting all the files, I went into the Dashboard and saw several lines of errors. It looked like they were caused by the plug-in Akismet. So I proceeded with the upgrade by clicking the upgrade link, hoping that the upgrade will resolve the issue. However, it did not. After the successful upgrade, I went into the plug-in section and de-activate and re-activate the plug-in, but the error messages still appeared on top, both in Administrator panel and my blog. Finally, I resolved the issue by downloading the plug-in from the Akismet web site and uploading it to my blog. I don’t know if the one packaged in WordPress 2.0.3 is different than the one found on Akismet web site, but apparently my blog prefer the one from the Akismet site. Weird! Anyone knows why?
June 03, 2006
7:27 am on Saturday
It happened because you aren’t supposed to overwrite the wp-content folder, which is where all the plugins are stored. The package that’s available from WP isn’t just an upgrade pack, it’s a full installation. There’s actually upgrade instructions at http://codex.wordpress.org/Upgrading_WordPress for future reference.
June 03, 2006
7:28 am on Saturday
‘Your comment looks dirty’? What’s up with that?
June 03, 2006
2:45 pm on Saturday
I just uploaded and replaced all the files, then upgraded db, without de-activating anything or doing the backup. Everything went well. And I’m using the fxxking Akismet too.
June 04, 2006
1:01 am on Sunday
Thanks Steve Johnson! I think that might be my problem, since I replaced the Akismet plugin with the one in WordPress 2.0.3.
June 04, 2006
10:56 am on Sunday
on upgrade the wp-content folder is left untouched, and thus so is the plugins folder and eventually the Akismet plugin.
I also know that between wordpress 2.0.2 and 2.0.3 Akismet launched a new upgrade for it’s anti spam plugin, so the one offered by default in the 2.0.2 package is older than the one offered in 2.0.3,
conclusion, you (probably) had an old version of the plugin.
June 04, 2006
11:02 am on Sunday
i like my comments dirty