Let’s see the new features on 3.2, since 3.2.1 is a maintenance update only.

One of the important is that it is not support IE6 any more. Actually when I design a site, I am not thinking about IE 6, not testing the layout on IE6. It is 2011 already. It is too hard to find a IE 6 test bed in my office.

The second one is Full Screen Editor, I am working on it right now.  This Full Screen is not the real full screen, but a full screen of the current Window, maybe call it Full Window is better.

The third one is Faster page load. This is very important for User and Search Engine. Fast site can get higher rank on Google. Then, more users will see your site on Google. On the other side, Faster site make users happy.

Full list of the release notes below:

Highlights

• Refreshed Administrative UI – Admin redesign
• New Default Theme “Twenty Eleven” – Uses the latest Theme Features
• Full Screen Editor – Distraction free writing experience
• Extended Admin Bar – More useful links to control the site

• Enhanced Browser Compatibility-
  • Drop Internet Explorer 6 support
  • Start End-of-life (EOL) cycle for Internet Explorer 7
  • Browse Happy notify users of out-of-date browser

• WordPress is Faster and Lighter-
  • Faster page loads — We’ve gone through the most commonly loaded pages in WP and done improvements to their load time
  • Faster Upgrades — The update system now support incremental upgrades so after 3.2 you’ll find upgrading faster than ever
  • Optimizations to WP_Filesystem — Updates over FTP are now much quicker and less error prone
  • Stream downloads to the filesystem — Improves update times and lowers the memory footprint
  • Performance improvements for wptexturize()
  • Remove PHP4 compatibility including timezone support
  • More efficient term intersection queries
  • Some optimizations in the HTML sanitizer (kses)
  • Speed optimizations for is_serialized_string()
  • Cache the Dashboard RSS Widgets HTML output to reduce unnecessary Ajax requests as well as the memory footprint
  • And many other improvements and tweaks

User Features

General

• Admin Bar: Add a Themes submenu under Appearance, for consistency
• Admin Bar: Add View Site/Dashboard links, ‘View X’ links in the admin, ‘View’ action link for terms, new custom taxonomy string: view_item, defaulting to ‘View Tag’ and View Category’
• Admin Bar: Support Edit link for Attachments
• Switch from “Panel/SubPanel” to “Screen” in inline documentation and Codex links
• Add collapse link to admin menu
• Help Tab text updates
• Favorites menu no longer exists
• New Freedoms (rights) and Credits links at bottom of admin screens
• Use monospaced font for HTML editor
• Validate the HTML in the admin area
• Make copying the PressThis bookmarklet code easier in WebKit browsers
• Move copyright notices to license.txt
• Refresh login form styles to match admin style

Dashboard

• Change View All Buttons into plain links
• Show full set of status links in recent comments box
• Drop “Change Theme” button
• Update core UI changes; “Update Automatically” changed to “Update Now”, first core update is now a primary button
• Core support for partial updates

Posts

• Change Menu Name from ‘Posts’ to ‘All Posts’
• Show the sticky posts checkbox (“Stick this post to the front page”) Only when author has ‘edit_others_posts‘ capability
• Updated styles for the Visual editor buttons
• Full screen editor experience called Distraction Free Writing – accessed via the Toggle Fullscreen mode tool in the Visual editor and fullscreen button in the HTML editor (Trac Ticket 17198)
• New sprite for the TinyMCE buttons
• Fix pagination when searching or filtering posts

Media

• Add ‘Add New’ button to edit media
• Update the blip.tv oEmbeds

Links

• Change Menu Name from ‘Links’ to ‘All Links’
• Add ‘Add New’ button to edit links

Pages

• Change Menu Name from ‘Pages’ to ‘All Pages’

Comments

• New comment bubble styling

Appearance

• New Default theme – TwentyEleven – based on Duster Theme (Trac Ticket 17198).
• Allow selecting previously uploader headers and randomly serving previously uploaded or default headers
• Denote images that are headers or backgrounds in the media ui
• Show hierarchy for pages and taxonomies in nav menus admin
• Introduce new is_multi_author() template tag to make it easier for themes to have different behaviour when a site has more than one author
• Be less specific about theme repo licenses (as they can vary in specifics). They are all compatible with the license WordPress uses

Plugins

• Allow plugins to disable screen options with filter
• Be less specific about plugin repo licenses (as they can vary in specifics). They are all compatible with the license WordPress uses

Tools

• Change Menu Name from ‘Tools’ to ‘Available Tools’
• Press This bookmarklet redesign
• UI refresh for Press This
• Export commentmeta

Users

• Change Menu Name from ‘Users’ to ‘All Users’
• Add ‘Add New’ button to edit users

Multisite

• Show access denied page and list a user’s sites if they visit an admin they don’t have permissions for rather than redirecting to the users’ primary blog
• Make “Space Used” gray instead of green in multisite Right Now box
• Make user validation when adding a user via network admin consistent with adding a user elsewhere and provide better feedback for validation problems
• Allow Pagination for Must-Use/Dropin plugins; respect WP_CONTENT_DIR & WPMU_PLUGIN_DIR for help text; move help text into WP_Plugins_List_Table
• Rename network admin submenus to not clash with top level menus

This post is brought  by Party Poker.

But, it did have many new features on it.

Post formats

Probably the most anticipated and most debated feature for 3.1, post formats allow an author to specify one of ten standard formats for a post to be displayed. The ten post formats to be supported by 3.1 are default (the post format we all know), aside, chat, gallery, link, image, quote, status, video, and audio.

The custom formats are really no more than taxonomies that get a special seat under the “publish” meta box of the post editor.  Originally the post format selection was going to be made within the publish meta box.  The big question to me is what features, or lack of, will each format be boxed with? A partial (and subject to change) description of how WordPress will handle the standard formats can be found in the new codex page on post formats.

The basis of the post format debate is whether theme authors should be allowed to extend post formats beyond the standard ones. Suggested examples for additional formats have been for things like code, lists, events, generic media, “blog” posts ( rather than default ), products and more.  Whether these ideas have merit or not, the point is the concept of extensibility.  It appears themes that extend non-standard formats with the post format markup will not be approved for the .org theme repository.  The main idea behind strict standardization is to encourage developers to broadly support a smaller set and to allow for portability from theme to theme.

It may also be worth noting that post formats are not the same as custom post types. However, formats will undoubtedly replace a tendency by many users to use custom post types in circumstances where a post format is more applicable.  On the other side of that coin, some of the non-standard format ideas listed above may be better suited as custom post types.

To get going on using post formats, try going here, here, here, here, and here just to start.

Custom post type archives

By default WordPress 3.0 does not index custom post types.  For instance, let’s say WPCandy created a ‘product’ post type (which is not the case) that can be accessed via wpcandy.com/sells/product-x.  Well that’s great, but if you just want to see all things WPCandy sells, WordPress doesn’t index wpcandy.com/sells unless the theme developer creates a specific page template for that query.  3.1 generates this type of “archive” for custom post types without a custom template.

Custom post type admin menu handling

One handy feature that’s going into 3.1 is the ability to customize the way admin menus are handled for custom post types.  In 3.0 a custom post type standardly gets a top level menu location, but 3.1 will allow you to customize where they go and how to handle them.  Andrew Nacin, a WordPress core contributor, used the example that a developer may want to create a custom post type called ‘Slideshow’ and include it under the already existing ‘Media’ menu rather than its own new one.  Read more about this feature in his blog post about it.

Query multiple taxonomies

Custom taxonimies are awesome. Now we can filter posts using them in an awesome way. Suppose we wanted to set up a query to allow users to see posts about Automattic that aren’t about Matt on WPCandy?  Because WPCandy has the ‘people’ taxonomy and the ‘company’ taxonomy, we can now query posts about ‘Automattic’ AND not about ‘Matt’.  Otto has put up a nice post to go into further detail on multiple taxonomy queries.  Are you imagining like I am all the fun ways you can now filter your content using this feature?

Sortable columns and admin ajaxification

This is a very nice enhancement of the interaction with the WordPress admin.  Columns are now sortable.  Search and admin pagination were going to be ajaxified, but got caught up and have been put off for 3.1.  This project was a GSoC project of Cristi Burca, who has even shared how to make our own columns sortable as well.

Super admin network dashboard

Multisite users will get a new super admin dashboard with its own menu.php and pages.  It declutters the regular admin dashboard for individual sites.

User admin dashboard

In the spirit of the super admin dedicated dashboard, it was suggested to create a user admin dedicated dashboard.  Ryan Boren described its purpose on the trac ticket:

Some of the same fixes are needed for both network and user admin. The user admin part of this is purposefully limited to offering a way to get rid of the dashboard blog stuff. If a user does belong to a blog, then all user related stuff happens there and not in the user admin.

Internal linking

Also know as: tab overload prevention.  Everyone should love this. There is now no need to open new tabs and search your own blog externally to link back to an old article.  The new internal linking system is integrated into the existing button.  The new display has the traditional linking methods on top and a search posts / list of posts on bottom for internal linking.

WordPress.com-style admin bar

The admin bar from WordPress.com is shifting to .org.  Some wanted to keep this functionality as a plugin, and some development delays almost got it pushed to 3.2.  However, everything seems in order and ready to go for a 3.1 release.  The bar comes standard with 5 parent menu items plus a search box on the right hand side.

PrettyPress

A few highlights for 3.1 are cleanup projects to make WordPress more user friendly or just better put together.  Tiny MCE is getting a facelift.  Theme searching will become more like the .com experience.  The admin css files were obliterated and redone by John O’Nolan and the WordPress UI group.

http://wordpress.org/development/2010/06/thelonious/

Arm your vuvuzelas: 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. (Twenty Ten theme shows all of that off.) Developers and network admins will appreciate the long-awaited merge of MU and WordPress, creating the new multi-site functionality which makes it possible to run one blog or ten million from the same installation. As a user, you will love the new lighter interface, the contextual help on every screen, the 1,217 bug fixes and feature enhancements, bulk updates so you can upgrade 15 plugins at once with a single click, and blah blah blah just watch the video. (In HD, if you can, so you can catch the Easter eggs.)

WordPress 2.8.2 fixes an XSS vulnerability. Comment author URLs were not fully sanitized when displayed in the admin. This could be exploited to redirect you away from the admin to another site.  Download 2.8.2 or automatically upgrade from the Tools->Upgrade page of your blog’s admin.

I use the automatically upgrade tools of WordPress to finish upgrade.

No risk, no error. Fast.

The most important is to upgrade AdSense Manager to Advertisement Manager.

Now this plugin can handle not only AdSense ads, but also AdBrite, Adify, AdGridWork, Adpinion, Adroll, Chitika, Commission Junction, CrispAds, OpenX, ShoppingAds, Yahoo!PN, and WidgetBucks.

So good to use these ad platform to make money from your posts.

I do rely on this anti-spam facility to protect my blog.

Less than 15 seconds. It is finished.

Don’t wait, just login and click it to protect your WordPress.