{"id":4535,"date":"2016-10-28T04:30:27","date_gmt":"2016-10-28T04:30:27","guid":{"rendered":"https:\/\/wordpress.org\/news\/?p=4535"},"modified":"2021-06-04T12:00:55","modified_gmt":"2021-06-04T12:00:55","slug":"wordpress-4-7-beta-1","status":"publish","type":"post","link":"https:\/\/wordpress.org\/news\/2016\/10\/wordpress-4-7-beta-1\/","title":{"rendered":"WordPress 4.7 Beta 1"},"content":{"rendered":"
WordPress 4.7 Beta 1 is now available!<\/p>\n
This software is still in development,<\/strong> so we don\u2019t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.7, try the WordPress Beta Tester<\/a> plugin (you\u2019ll want \u201cbleeding edge nightlies\u201d). Or you can download the beta here<\/a> (zip).<\/p>\n WordPress 4.7 is slated for release on December 6<\/a>, but we need your help to get there. We’ve been working on a lot of things, many of them to make getting your site set up the way you want it much easier. Here are some of the bigger items to test and help us find as many bugs as possible in the coming weeks:<\/p>\n As always, there have been exciting changes for developers to explore as well, such as:<\/p>\n If you want a more in-depth view of what major changes have made it into 4.7, check out posts tagged with 4.7 on the main development blog<\/a>, or look at a\u00a0list of everything<\/a>\u00a0that\u2019s changed. There will be more developer notes to come, so keep an eye out for those as well.<\/p>\n If you think you\u2019ve found a bug<\/strong>, you can post to the Alpha\/Beta area<\/a> in the support forums. We\u2019d love to hear from you! If you\u2019re comfortable writing a reproducible bug report, file one on WordPress Trac<\/a>, where you can also find a list of known bugs<\/a>.<\/p>\n\n
\n
WP_Hook<\/code><\/strong> – The code that lies beneath actions and filters has been overhauled. You likely aren’t affected, but if you’ve done things to the
$wp_filter<\/code> global or experienced funky recursion bugs in the past, please take a moment to read the dev note<\/a> and test your code.<\/li>\n
register_setting()<\/code>.<\/li>\n