Trac Tickets for WordPress Developers

As mentioned in an earlier post here on, WordPress 3.3 is expected to arrive around November 15th and I’m sure you’re interested in what’s happening over at the development side of it, so today we’re publishing our top 6 WordPress Core Trac tickets worth following.

If you’re not familiar with Trac, you can read about it right here. Basically, it’s a project management and source code management system that is used in many open source projects including WordPress. Tickets are like issues or messages created and attached to versions so one can follow along.

Following a ticket is quite simple — you need to have a account and use it to log yourself in to the WordPress Core Trac. When viewing a ticket, scroll down to the very bottom and attach yourself to the CC field and submit changes. All the updates to the ticket will go to your e-mail. Make sure you visit the preferences section and set your e-mail for your Trac account too.

New Settings API & Workflow (#18285)

This ticket is interesting for those of you who’re constructing their admin options pages using the Settings API. It seems like WordPress 3.3 is getting an overhaul at that side and will probably be using the same API to construct their own settings screens. There’s a small debate going on, on whether the API should implement form field construction or should that totally be left up to the developer.

I’m only referring to field callbacks as they exist now. I strongly dislike form *field* construction. The best API for constructing fields is HTML.

Andrew Nacin

WP_Meta_Box (#18179)

An interesting new look at WordPress meta boxes. This object-oriented approach should eventually make it much easier to create and work with meta boxes on edit screens, the Dashboard and custom areas as well. At the time of writing we can already see some interesting code snippets attached which you can play around with to see where they’re heading.

Editor API Enhancement (#17144)

If you’re a premium themes developer you should definitely follow this ticket since it introduced a clean way of hooking to the editors (both HTML and the TinyMCE visual editor) in WordPress. This should make it much easier to provide custom buttons, shortcode generators and so on. Here’s also a related ticket with some code attached.

Responsive Admin (#18198)

Probably one of the most exciting features coming up in WordPress 3.3. There’s not much going on in the ticket itself though there seem to be some interesting discussions about it over at the UI blog so if you’re interested make sure you follow both.

Child Themes Support for Theme Installer (#13774)

Child themes have been opened up to the themes repository not so long ago, so this ticket will make sure that such themes can not only be downloaded from itself, but directly via the admin panel too. Quite an old ticket, but will hopefully be closed at 3.3.

Avoid Losing Widgets When Switching Themes (#17979)

Not that big of a deal but definitely a bad use experience that can be avoided. There was a chat about it during the dev meeting last week, mentioning some interesting ways this could be solved. One we liked was the extra registered sidebars hanging at the very bottom of the widgets section containing all the setup from the old theme, so by dragging them to the new sidebars, widgets settings are not lost. Anyways, this was only one of the suggestions, so follow the ticket to learn more.

So that’s about it for today. A list of all open tickets for 3.3 can currently be found in the Next Major Release report on Trac and if you’re really into it, make sure you’re following the development updates blog.

Let us know which of the tickets you’re most excited about, and whether we missed anything in our list. Use the reply section below to leave your comments. Thanks for reading and enjoy our Twitter feed too!