WordPress 3.0 Released 79
An anonymous reader writes "WordPress 3.0, the thirteenth major release of WordPress and the culmination of half a year of work by 218 contributors, is now available for download and comes with 1,217 bug fixes and feature enhancements. Major new features in this release include a new default theme called Twenty Ten. Theme developers have new APIs that allow them easily to implement custom backgrounds, headers, shortlinks, menus (no more file editing), post types, and taxonomies."
3.0, the XIIIth (Score:5, Insightful)
If only there were some way of counting major releases, such that one could tell how many there were, and by extension, know how many versions had been released prior...
Re:The upgrade process was painless (Score:4, Insightful)
I clicked one bottom and it updated. Everything seems to be working normally.
What fun is this ;)
Re:The upgrade process was painless (Score:3, Insightful)
Re:Thanks Wordpress (Score:3, Insightful)
I think that looks more like a person controlling tools to me.
Since no one has asked yet... (Score:4, Insightful)
I have to ask: Is it no longer a steaming pile of security holes? Seriously, most people I know have given up blogs and moved to Facebook or some hosted blogging service to get their message out. After getting hacked a couple of times I've put it in the same category as PHPNuke -- too much trouble to be worth it to anyone for whom it's not their job.
Re:The upgrade process was painless (Score:3, Insightful)
Sounds like your issue is with plugins, not with Wordpress.
It sounds like both the plugins, wordpress, and the admin himself.
Wordpress should not mess with the API without warning. That warning should come in the form of depreciated functions in one version, removal one or two versions after.
The plugins might take advantage of undocumented APIs, or perform some hacks to accomplish a task.
The admin should always read the changelog.