Lifespan of a WordPress version

The new version 3.6 has been released much later than anticipated; the release has been estimated for the end of April and has finally been released in early August. Therefore v3.5.x stayed the freshest available version for 234 days. How does this compare to the previous versions?
wp_versions
On average a WordPress version was replaced by a new one after 198 days. Outstanding is the version 2.0 which stayed the newest version for over one year (Dec 2005 - Jan 2007). Starting with version 2.1 WordPress development took a faster pace and the release of new versions took about four to six months.

(Source: Wikipedia)

WordPress Pulse? – Heartbeat API

With WordPress 3.6, there will be a new API - Heartbeat. On Ticket 23216 in Trac all discussions and information be gathered together. Because Heartbeat may also have influences for users, here are some words and clues. Heartbeat is introduced to various activities, such as Autosave, locks of articles and to handle logon and logoff notifications. In parallel, the API can also be used for own developments.
Continue reading …

Disable Post Format UI

Currently is WordPress version 3.6 in Beta status. But new nice features are available and ready to test. One of this features is the new UI for the post formats. Post formats is a nice chance for more possibilities to declare a post to your readers. But sometimes we don’t need post formats. The default for hide the Post Format UI is user specific and is an option in the screen options, see the screenshot.
Continue reading …

the-customizer-wordpress-themes-gestalten-640x406

WordPress Theme Customizer Custom Controls

The Customizer is a relatively new way of WordPress Themes to provide you with options. Here is the visuality important, arrange the options directly in frontend for the Theme, play and save the settings.

We show you how to create your own classes to extend the controls, since not all fields and requests are in the core already. You can access existing solutions of the community or create your own classes. The first step is therefore a brief introduction for new classes and following an overview of some classes. Please extend this list via the comment form.
Continue reading …

Filename cache busting for WordPress styles and scripts

To embed custom CSS styles and scripts in WordPress you should use the wp_enqueue_script(), wp_enqueue_style(), wp_register_script() and/or wp_register_style() functions. Each of these functions allows you to define a version. By default it's the version of WordPress. The version identifier will be in the URL to the script as a query string.

The version identifier is used to expire the URL. Since the browser detects the new URL as a new resource, it will use the new instead of the cached resource.

Sadly not all endpoints respect the query string. From Google Developers:

Most proxies, most notably Squid up through version 3.0, do not cache resources with a "?" in their URL even if a Cache-control: public header is present in the response. To enable proxy caching for these resources, remove query strings from references to static resources, and instead encode the parameters into the file names themselves.

So the goal is to encode the version identifier into the filename without renaming the resource on the filesystem. This is where the following plugin comes in.
Continue reading …