It’s been only a week since the beta 1 was released, and the second beta version of WordPress version 4.2 has been now made available for testing. Since WordPress 4.2 doesn’t seem to release before mid April, it would be better for users to test their code against new beta releases. This will help them get an idea of how the new version will work once it’s released.
Note: Remember that Beta 2 is still not ready for production, and so make sure to avoid upgrading your existing site to the new beta release. Rather, you can create a test site for testing your code.
If you’re interested in WordPress web development, then reading this article will provide you useful insight on things to consider when testing your site against the new release.
When updating a plugin, you’ll probably have been prompted time and again to enter FTP login credentials. But, not all of the WordPress sites will have this functionality. Moreover, a user need to fill in credential details before a plugin update is in-place. However, beta 2 will make you enter not only FTP information but also SSH when a plugin update is in progress.
Cross-browser Support for Emoji is Optimized
Over the last few years, Emoji characters have become quite popular among users. To meet the growing demand for such characters, support for Emoji was added to WordPress 4.2 beta 1 release. But, beta 2 supports Emoji in a better manner, by making it available across different browsers.
Press This” Feature Has Improved
Beta 1 release introduced a redesign of the “Press This” feature, which helped in making publishing via special web browsers a hassle-free task. This feature has further refined, with the release of the WordPress 4.2 beta 2, which incorporates auto-embedded media. What’s more, content scanning has been optimized.
Compared to beta 1 release, 70 more bug fixes have been introduced with the new beta release.
Queries Have Been Optimized
If you’re a post author, then you’ll most likely be aware of the usefulness of WP_Comment_Query class, which helps to fetch users comments from the database. However, the beta 2 release helps in making this class even more useful by adding constructor to it. Let’s consider an example to understand how constructor helps prove beneficial when added to the WP_Comment_Query class:
// Current way
$comments_query = new WP_Comment_Query; [here we are creating the object of WP_Comment_Query class ]
$comments = $comments_query->query( $args ); [here we are executing wp_comment query using the query funtion ]
// Change Proposed for 4.2 beta 2
$args = array(
‘author_email’ => ‘firstname.lastname@example.org’
$comments_query = new WP_Comment_Query($args);
Even though, the result produced by both sample codes will be same, however the second one will work in a faster manner. That’s because, it helps to initialize the query argument when an object is created. This happens because of adding constructor to the class.
Hope that reading this article will help you become familiar with things, you can test against the new beta 2 release. When testing the second beta release, you can either use the WordPress Beta Tester plugin or else simply download zip file from the WordPress 4.2 beta 2 announcement post.