WordPress 3.4 Green is Good to Go

WordPress 3.4 is out, named “Green” in honor of jazz guitarist and composer Grant Green. Green is a great nickname for this hot release of WordPress, bringing with it some excellent new features and improvements.

As with all WordPress upgrades, it is recommended you backup your full WordPress site, database and all files, before upgrading. Ipstenu has been keeping a Master List for Troubleshooting WordPress 3.4 upgrade issues and so far, the list is short. Most issues are with non-compatible and non-compliant WordPress Plugins and Themes, especially with those not using Child Themes to customize their WordPress Theme. Upgrade all of those before upgrading to the new version of WordPress.

Speed

WordPress continues to get faster with every release, but this one breaks the sound barrier. The improvements in WP_Query report a 2-3x speed improvement for post data queries.

For those who like digging under the hood of WordPress, queries are now broken up into two parts, one to select the list of IDs with the given query criteria, and the second to select the posts once the IDs are determined, reducing the amount of data requiring processing within the database. The smaller the dataset, the faster the results and the less impact on the database, rewarding especially for those with database hosting issues. According to the news on WordPress Trac, Andrew Nacin reported a 90% reduction on Database CPU burn, a dramatic drop rate.

WordPress Theme Testing Improved

WordPress 3.4 improves Theme testing. The new Theme Customizer allows you to play around with various customizations and looks for your site before committing them to public display. Improvements in the Theme panel also includes term verses keyword searching and better descriptions in Theme search results helping to narrow your options when searching for a Theme.

Updates to the default WordPress Themes, Twenty-Eleven and Twenty-Ten, are also included and recommended updates before upgrading.

The new Theme Customizer works with existing WordPress Themes using current features such as changing the site title and tagline, setting a static front page, custom menus, navigation menus, etc., and adds the ability to hook into these additional customization features to expand a Theme’s custom options. The old features have been migrated into the new Theme Customizer.

The ability to add Theme support has been around since WordPress 2.9 with the introduction of post thumbnails. The add_theme_support function now includes custom-background and custom-header features which are now accessed throught he Theme Customizer. Otto on WordPress has an extensive article on how these new features work. I also recommend a review of his WordPress Settings API Tutorial. Chip Bennett describes even more on how to update your WordPress Theme for custom backgrounds and headers.

Also check out the Page Template Handling feature that allows for custom organization of your Theme file structure. You can now put any page template into any subdirectory of a WordPress Theme, giving you more freedom in arranging the hierarchy and grouping the file structure of a WordPress Theme.

Custom Header Sizes

Included in the Theme Customization improvements is the ability to change the size of your Theme’s header. Previously, it needed to be set at a specific height and width. With WordPress 3.4, your header art can be dynamically resized to match whatever your design wishes may be. No more cropping.

Just remember that you need to start with something that will work in the first place. Stretching and distorting the header image cannot be helped by any header customizer.

Embed Those Tweets Easily

Simply paste the link to a tweet into your WordPress blog post and it will automatically embed the tweet in the content with a citation link. This is a brilliant addition for social media integration and citation references. The Twitter Embeds use oEmbed, one of many embeds that work automatically in WordPress.

The new mobile API also includes the jQuery UI Touch Punch library to give front-end designers and developers the ability to make their sites work better under mobile conditions. Due to limitations with Windows 7/7.5/IE9, support isn’t included.

The new API is not just limited to mobile. It also adds improvements for custom content types and taxonomies. Expect to see some awesome improvements to WordPress Themes and Plugins based upon the new API, especially as most of them need to be more mobile-friendly.

Internationalization and Localization Improvements

If you haven’t been paying close attention, you may have missed the fact that the internationalization and localization team of WordPress has been working overtime on making brilliant improvements to WordPress overall. In the research I’ve been doing on WordPress, approximately 40% of all WordPress sites are not in English.

The updates include faster translation handling, improvements in the WP_Theme API to increase speed and caching, comma translation, LTR fields now forced for passwords, logins, etc., spell checker language options, feed language options, single-double quote and primes translation, improvements in default time zones, and POT files now split into three different files for content, admin, and admin networks, simplifying localization files. Expect even more in future updates.

You can read more about the specific improvements on the WP Polyglots translation team site.

HTML in Captions

The ability to add HTML in captions from the caption feature in the WordPress Media Library has been long desired. You could add it manually through the HTML Editor, but now you can do it from within the native media handler. This is a better way to provide image citations and expand the content references in the captions.

Don’t stop with links. You can now add bold and italic to jazz up those captions.

Luckily, Eric Mann is a member of my local Portland WordPress User Group so we can take advantage of his WordPress expertise. After presenting a program recently on how to contribute to the WordPress core, he used this new feature to describe in detail the WordPress core contribution process, a must read for every WordPress enthusiast on how you, too, can help WordPress improve.

A few details he mentions include the deprecation of closing PHP tags at the very end of a template file. No longer is it necessary to close the closing tag with the requisite ?> because if there is any white space at the end of a file, PHP is likely to break. This does not mean that coders are to no longer close any PHP tag, just the closing tag within a template file.

He also mentions internal functions and classes now include RTL, ie7, ie8, and others for browser targeted design and development.

Auto-complete has been added to add user for WordPress Multisite to make it faster for adding existing users to the network. The upload limit has also been increased from 10MB to 100MB for Multisite, a huge improvement for Multisite administrators.

A sweet little shortcut has been added that will make some lives easier and save a few fingers. To log into WordPress, you’ve had to either click the login link on your site, or type in your site’s URL plus /wp-login to access the login screen. You can now just type in /login, /dashboard, or /admin and save a few keystrokes and be redirected to the login, Dashboard panel, or general Administration Screens.

For those into the latest and greatest technology, the WordPress Administration Panels (nicknamed the Dashboard) now features retina-ready capabilities for retina displays such as the Retina Macbook Pro which highlights navigation points when you look at them. It’s very Star Trek and I’m totally ready for that. Matthias Kretschmann has more information on adding retina support for WordPress Plugins and Themes.

That information is related to a specific WordPress Theme and Plugin and has nothing to do with the WordPress upgrade. I’ve seen it and researched it. It’s clearly Theme and Plugin specific. The update includes some security updates so delaying should not be an option. Update the Theme and Plugins and then run the update for the WordPress 3.4. All should be good. Backup if you have any fears.

So I updated all of my sites and two of them the feature slides just stopped working and both themes are from woo themes. it\’s completely frustrating and i have no idea how to fix this, just been google searching. do you know where i can find info on fixing this issues? thanks!

Hi Lorelle,
I really appreciate the comprehensive posts you publish like this one. WordPress.com is already running on 3.4 as you know. It seems to be a little known fact among WordPress.org bloggers that the 31 million WordPress.com bloggers experience these changes at least a month before the release of new versions to WordPress.org bloggers.

I thought I would make more use of the “live preview” for Theme Customization than I have so far and expect to be using it more in the future. It’s a very useful feature for me because I have a private test blog I use when I answer questions on the support forum. I like being able to select header images and background images from the ones in my Media Library and predict that this feature will be very popular.

I have another domain I’m not currently using and I have been considering self-hosting a blog again. I’m finding that the rate and pace of additonal feature releases at WordPress.com, all without prior notice, are annoying me. Rather than becoming negatively focused I’ve tried to remain positive and more flexible when it comes to announced changes, but we all have limits and I may be reaching mine. This summer I’ll mull that over before I make a decision.

With the three month delay in this release combined with the delays in releasing the 2012 WordPress Theme, I’ve heard from some that they thought development on WordPress had slowed down – interesting how the perspective changes depending upon your own place and commitment to the WordPress Community. Timethief, you have done so much for WordPress.com and the WordPress Community, you deserve a break. You don’t have to run away, just take a vacation. I did and it was the best thing I could have done for myself.

I’m so thrilled to be a part of the WordPress.com community and delighted to test out all the new goodness that keeps creeping in making WordPress and WordPress.com better and better all the time. While there are always clunks along the way, I have to say that the testing experience of WordPress.com has come a long way since those very early unsteady days. Everyone needs to be commended for that.

Thanks again for all that you do for so many with little or no thanks.

WordPress seems to release so many dang updates now-a-days, that it’s not even funny. The one I was really excited about was JetPack.

My tech blog really got a big speed benefit from it. However, we still try to keep the plugins as minimal as possible, and I personally sometimes even do not do the main updates, unless I KNOW it will mess anything up on my precious blog.

WordPress has actually been very slow on large updates. Mandatory updates for security happen when they happen, often without being on a schedule. The next update to WordPress 3.5 is due soon, but the next one is many months away. I’m glad you got the speed benefits of the new update though. Isn’t it exciting all the fantastic features WordPress brings with every update.