By Gary Pendergast The second release candidate for WordPress 5.0 is now available!
This is an important milestone, as we near the release of WordPress 5.0. A final release date will be announced soon, based on feedback from this release candidate. Things are appearing very stable and we hope to announce a date soon. This is a big release and needs your help—if you haven’t tried 5.0 yet, now is the time!
To test WordPress 5.0, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).
For details about what to expect in WordPress 5.0, please see the previous release candidate post.
We stopped rendering AdminNotices compatibility component, as this previous attempt at backward compatibility was bringing in numerous incompatible banners and notices from plugins.An update to the parser to better deal with malformed HTML that could cause a loop. We’re only aware of this in the wild being triggered once in the over a million posts made with Gutenberg, but it caused a loop so we wanted to fix for RC2.Cosmetic and minor changes in RC2
Accessibility: Simplify sidebar tabs aria-labels.Make the Image Link URL field readonly.Internationalization: Merge similar text strings that differed only in capitalization.CSS: Improve block preview styling.CSS: Fix visual issues with Button block text wrap.Fix getSelectedBlockClientId selector.Fix Classic block not showing galleries on a grid.Fix an issue where the block toolbar would cause an image to jump downwards when the wide or full alignments were activated.Move editor specific styles from style.scss to editor.scss in Cover block.Fix modals in Microsoft Edge browser.Fix Microsoft IE11 focus loss after TinyMCE init. Add IE check.Fix Microsoft IE11 input when mounting TinyMCE.Change @package names to WordPress.How to Help
Do you speak a language other than English? Help us translate WordPress into more than 100 languages!
If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
RC bittersweet.We welcome in Gutenberg,Vale Gutenbeard.
Via:: WordPress 5.0 RC2