The second release candidate for WordPress 4.6 is now available.
We’ve made over 30 changes since the first release candidate. RC means we think we’re done, but with millions of users and thousands of plugins and themes, it’s possible we’ve missed something. We hope to ship WordPress 4.6 on Tuesday, August 16, but we need your help to get there.
If you haven’t tested 4.6 yet, now is the time!
Think you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.
To test WordPress 4.6, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).
For more information about what’s new in version 4.6, check out the Beta 1, Beta 2, Beta 3, Beta 4, and RC 1 blog posts.
A few changes of note since the first release candidate:
- Support for custom HTTP methods and proxy authentication has been restored.
- Various fixes for the streamlined updates, including better failure messages and error handling, basic back-compat styling for custom update notifications, and additional and standardized JavaScript events.
- Unnecessary reference parameters have been removed from new multisite functions.
- A compatibility issue with PHP 7.0.9 (and PHP 7.1) has been fixed.
Developers, please test your plugins and themes against WordPress 4.6 and update your plugin’s Tested up to version in the readme to 4.6. If you find compatibility problems please be sure to post to the support forums so we can figure those out before the final release – we never want to break things.
Be sure to read the in-depth field guide, a post with all the developer-focused changes that take place under the hood.
Translators, strings are now frozen, including the About Page, so you are clear to translate! Help us translate WordPress into more than 100 languages!
Happy testing!
The verdict is in,
Can I haz all the features,
Your best WordPress yet.
🏳️🌈