Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: ergophobe
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 (or upgrade within your dashboard). Major new features in this release include a sexy new default theme called Twenty Ten. Theme developers have new APIs that allow them to easily implement custom backgrounds, headers, shortlinks, menus (no more file editing), post types, and taxonomies.
Normally this is where I’d say we’re about to start work on 3.1, but we’re actually not. We’re going to take a release cycle off to focus on all of the things around WordPress. The growth of the community has been breathtaking, including over 10.3 million downloads of version 2.9, but so much of our effort has been focused on the core software it hasn’t left much time for anything else. Over the next three months we’re going to split into ninja/pirate teams focused on different areas of the around-WordPress experience, including the showcase, Codex, forums, profiles, update and compatibility APIs, theme directory, plugin directory, mailing lists, core plugins, wordcamp.org… the possibilities are endless.
I re-uploaded my entire backup.
Losing tinymce.js and the importers bought us quite a bit of extra room. There will probably be some setups with lots of plugins and big po and mo files that will bust the limit, but there's only so much butchering we can do. The workaround is to do a manual upgrade. I think we've done enough here.
Another last resort option: we could remove the Prototype.js/Scriptaculous (290KB) and load it from googleapis when queued from a plugin. It hasn't been used in core for a long time and don't think there are many plugins that use it.
There's not much more we can do here for 3.0, which goes RC soon. Addressing root causes will have to wait for 3.1.
It was designed to update once and run multiple sites from that one install, has anyone tried that out yet ?
themes and addons can be installed on a site by site basis to answer ergophobe's concerns.
The WP plugin system is quite a bottleneck for getting people to upgrade. Often the core functionality of a site can depend on a plugin or a series of plugins.
So, when the CMS gets updated there is quite a risk in upgrading, as it might spoil your whole site because some plugin does not work with the new version.