{"id":4509,"date":"2018-02-11T14:46:17","date_gmt":"2018-02-11T13:46:17","guid":{"rendered":"https:\/\/florianbrinkmann.com\/en\/?p=4509"},"modified":"2020-02-09T10:59:36","modified_gmt":"2020-02-09T09:59:36","slug":"wordpress-weekly-recap-6-wordpress-4-9-3-and-4-9-4","status":"publish","type":"post","link":"https:\/\/florianbrinkmann.com\/en\/wordpress-weekly-recap-6-wordpress-4-9-3-and-4-9-4-4509\/","title":{"rendered":"WordPress weekly recap #6: WordPress 4.9.3, 4.9.4 and more"},"content":{"rendered":"\n

This week there were two new releases for WordPress \u2013 the planned 4.9.3 version and the unplanned 4.9.4.<\/p>\n\n\n\n\n\n\n\n

Core<\/h2>\n\n\n\n

WordPress 4.9.3 and 4.9.4<\/h3>\n\n\n\n

On February 5, the core team released WordPress 4.9.3, that contains 34 bug fixes for changesets, widgets, compatibility with PHP 7.2 and more. You can read more about it in the release post \u00bbWordPress 4.9.3 Maintenance Release<\/a>\u00ab by Sergey Biryukov.<\/p>\n\n\n\n

One day later, WordPress 4.9.4 went live. The reason for that is that 4.9.3 introduced a bug that prevents the auto-update feature to work. That is fixed with 4.9.4, but you have to start the update manually. Otherwise, you will not get future auto-updates. More about that in the post \u00bbWordPress 4.9.4 Maintenance Release<\/a>\u00ab by Dion Hulse.<\/p>\n\n\n\n

On the technical side, the bug caused a Fatal Error when WordPress tried to update itself because not all requirements for of find_core_auto_update()<\/code> were met. More on that can be found in Dion\u2019s post \u00bbWordPress 4.9.4 Release \u2013 The technical details<\/a>\u00ab.<\/p>\n\n\n\n

Misc<\/h3>\n\n\n\n