I’ve been keeping an eye on what folks are saying about their WordPress 3.0 upgrade experiences and it appears that most folks are finding the upgrade to be a pretty smooth sailing experience. Kudos to everyone who contributed to 3.0, this is not a small accomplishment (especially considering the fundamental changes in 3.0).
If you do need any help upgrading to WordPress 3.0, don’t hesitate to contact my WordPress HelpCenter team. You can call them directly at: (303) 395-1346 from 9am-8pm US/Eastern M-F or email anytime to help@wphelpcenter.com.
This post is part of the project: WP HelpCenter. View the project timeline for more context on this post.
Today I tried upgrading WordPress to 3.0, but kept running into an error message on a file in the wp-includes directory having to do with taxonomies. Of course I completely deleted and repeatedly re-uploaded the new version of the wp-includes directory, hoping that this would solve the problem. But no matter what I did, nothing worked. Then I read an obscure comment on some blog which mentioned this same problem, quoting the exact same error message down to the filename and line number. The commenter said something about a podcasting plugin causing the problem with the upgrade to 3.0, and said that you should deactivate it prior to attempting an upgrade to WP 3.0.
Since the error message was blocking my ability to log in to the WordPress admin control panel, my only other option was to delete the plugin itself, which I did (But I FTP’d it for backup purposes first).
As Borat once said, Great Success! This solved the problem. To all who encounter the error message about “taxonomy,” to solve that problem just upgrade, deactivate or delete the following plugin and you’ll once again be on track:
“Podcasting Plugin by TSG“
The installation seemed to go without a hitch. But, graphics I wish to use will not appear. Selecting to put the graphic onto the post returns a totally blank browser page with the word Done in the lower left hand corner.
There are other minor glitches that are annoying but that I can live with. In the past two years of using WordPress, this is the buggiest upgrade I have experienced.
One thing that I am very disappointed by, because it points to an apparent lack of any sort of change impact review by contributors to WordPress.org development was the “feature” to automatically change “WordPress” to “WordPress”. This is some misguided attempt at “brand control” or something that wasted many hours of my time. The only way of restoring my site to a pre-upgrade state was to download a plugin to change “WordPress” back to “WordPress.” Why would this feature ever make it through any sort of review of the contributors? It provides no value to the WordPress community, and it has only served to make me and I’m sure thousands of other WordPress users hesitant to ever upgrade again. Will the next upgrade bring similar unwanted, undocumented features? I hope not.
Upgraded to version 3.0 the other day and had no problems at all,but its good to know help is out there. I’ll bookmark your page in case trouble starts a brewing.
I upgraded to WordPress 3 and then could not log in, just had blank white pages. We have now disabled the Events Calendar and got the site back up, but cannot put back the Events Calendar
I upgraded to 3.0 and now I can’t upload any plug-ins or even re-install WP. The file permissions are correct but it doesn’t work. – ANY THOUGHTs?
The error message I get is:
Downloading update from http://wordpress.org[...]0.zip…
Unpacking the update…
Could not create directory.: /wp-content
Installation Failed
I upgrade my blog with more than ten plugins and I had problems with Headspace, but after switching off tags page module, it works fine now