WordPress 4.3 beta 1 was put into the hands of testers last week. Those who have been following 4.3 developments are already familiar with the major features headlining this release, ie. the new site icons, menu management in the customizer, and more secure passwords. However, there are also a couple lesser-known improvements that will have a positive impact on millions of WordPress users.
Improved User Search
Searching for users in the admin is about to get much easier, thanks to work on a ticket opened by John Blackbourn 16 months ago. He notes that “only the user_login (username) and user_nicename (sanitized username) fields are searched,” excluding the following more likely fields:
- First name
- Last name
- Display name
This issue was especially problematic in large, multi-thousand member multisite installations where finding a user in the admin often meant knowing exactly what to query and then paging through results. WordPress 4.3 contributions from Pippin Williamson and Scott Taylor make it possible to search by the user’s email, URL, and display name.
Comments Turned Off on Pages by Default
WordPress 4.3 will also bring a welcome change to turn off comments on pages by default. In the future when you create pages, you won’t have to remember to go into the discussion settings to disable comments. One might think this would be a simple little thing to change, but quite a bit of discussion has gone into crafting the best solution to the ticket opened five months ago.
This change also applies to all custom post types. Mel Choyce outlined the new behavior in a post on the make.wordpress.org/core blog:
Post registrations that don’t explicitly add support for comments will now default to comments being off on new posts of that type (before, they defaulted to on). Up until now, post type support for comments has only affected admin UI; a developer could omit comment support on registration but still allow comments to be posted. This is a change in behavior, and we will be closely monitoring its effects during beta. Moving to explicit support will allow core behavior to be more predictable and robust in the future, but we will always consider real-world usage.
The change also comes with a new function and a filter that you can use to restore the current behavior of comments to your post type, if necessary. More details and an example on how to use the filter are available on the make.wordpress.org/core announcement post.