Download and Test WordPress 4.4 Beta 2

By | November 2, 2015

According to the blog submitted by Scott Taylor, he has announced the beta 2 release of WordPress 4.4 on 28 October 2015 for download as well as testing. Since the software is still in the development phase so it is recommended not to run it on the production site. In order to test WordPress 4.2 one needs to install the WordPress Beta Tester Plugin (you’ll want “bleeding edge nightlies”) in your test environment.  Also one can download the beta for testing.

One can easily test and find bugs and post to Alpha/ Beta area in the support forum. One can easily find a list of known bugs and everything that have been fixed so far.

Some of the changes in WordPress 4.4 Beta 2:

Embeds not working for non-WP sites:

While testing it has been noticed that the new embeds feature doesn’t work for non-WordPress sites. It is shared between the iframe and the host side is added via PHP by WordPress. This should be done in the JavaScript part to ensure that it works for any website.

random_bytes() preventing to log in if PHP is 5.3.5:

When one tries to log in WordPress on a local WAMP stack using PhP 5.3.3 then one gets the fatal error for this as:

Fatal error: Maximum execution time of 60 seconds exceeded in D:\path_to_wp\wp-includes\random_compat\random_bytes_openssl.php on line 64

The information that is given by xdebug is as given below:

Call Stack
#	Time	Memory	Function	Location
1	0.0072	689848	{main}( )	..\wp-login.php:0
2	0.3460	25607752	wp_signon( )	..\wp-login.php:776
3	0.3611	25695560	wp_set_auth_cookie( )	..\user-functions.php:94
4	0.3611	25696040	WP_Session_Tokens->create( )	..\pluggable.php:921
5	0.3611	25696648	wp_generate_password( )	..\session.php:147
6	59.2952	25697008	wp_rand( )	..\pluggable.php:2138
7	59.2952	25697168	random_int( )	..\pluggable.php:2185
8	59.2953	25697392	random_bytes( )	..\random_int.php:148

Attaching metadata to shared terms results in data corruption:

Shared taxonomy terms on a cron job is split in WordPress 4.3. So there may be sites where the shared terms will still exist after upgrading to 4.4. If a term $term_id is shared between two or more taxonomies then one will get the unexpected results if you add_term_meta( $term_id, ‘foo’, ‘bar’). So based on this discussion the correct approach is to bail out of add_term_meta() or update_term_meta() if one detects that the $term_id is shared. 

meta_form performing a potentially expensive query:

The query in meta_form can be incredibly slow on the sites with a lot of post meta. According to the solution that is suggested by one of the WordPress lover is to cache the query and update the cache of meta to use every time a new piece of post_meta is saved. It will prevent the query from needing to be run on sites with a persistent cache.

insert_with_markers() is not automatic:

insert_with_markers() is not automatic that leads to corrupted .htaccess updates under race conditions. This happens when two different processes simultaneously calls the WordPress insert_with_markers() function in “wp-admin/includes/misc.php” . The function does not automatically rewrite the file and second process can see a half-rewritten copy of the first one.

These are some of the known bugs that have been fixed and some of them which will be fixed with future releases. The above listed bugs are just a few of them! The main idea behind this release is to make the WordPress 4.4 which is scheduled to be released on December as bug free. More people should get involved in the testing of these beta releases and put forth the bugs that they find.  This contribution from the WordPress lovers will definitely be a great help to fix the bugs for WordPress 4.4 release.

Related Post