WordPress 5.4 Beta 1 is now available for testing!<\/p>\n\n\n\n
This software is still in development,<\/strong> so we don\u2019t recommend running it on a production site. Consider setting up a test site to play with the new version.<\/p>\n\n\n\n You can test the WordPress 5.4 beta in two ways:<\/p>\n\n\n\n WordPress 5.4 is slated for release on March 31, 2020<\/a>, and we need your help to get there<\/strong>!<\/p>\n\n\n\n While the primary goal for 2020 is full-site editing with blocks<\/strong>, contributors to WordPress are working across every area of the project to ensure the software continues moving forward.<\/p>\n\n\n\n Testing for bugs is an important part of polishing the release during the beta stage and a great way to contribute. Here are some of the big changes and features to pay close attention to while testing.<\/p>\n\n\n\n WordPress 5.4 Core will merge ten releases of the Gutenberg plugin. This means there\u2019s a long list of exciting new features. Here are just a few:<\/p>\n\n\n\n Some additional changes to make note of:<\/p>\n\n\n\n To see all of the features for each release in detail check out the release posts: 6.6<\/a>, 6.7<\/a>, 6.8<\/a>, 6.9<\/a>, 7.0<\/a>, 7.1<\/a>, 7.2<\/a>, 7.3<\/a>, 7.4<\/a> and 7.5.<\/p>\n\n\n\n The block editor team has achieved a 14% loading time reduction and 51% time-to-type reduction, for a particularly sizable post (~ 36,000 words, ~1,000 blocks) since WordPress 5.3.<\/p>\n\n\n\n When a project powers 34% of the world’s websites, there must be a focus on security. This is why contributors continue working so hard on the Site Health Project.<\/p>\n\n\n\n WordPress 5.4 adds a widget on the dashboard that warns administrators of potential issues that could affect their site’s performance or security. A call-to-action button directs them to the Site Health screen for details and suggested fixes.<\/p>\n\n\n\n WordPress strives to improve accessibility with every release, and this release is no different. Version 5.4 will contain the following accessibility enhancements:<\/p>\n\n\n\n 5.4 also contains a bunch of developer focused changes.<\/p>\n\n\n\n The HTML 5.1 specification mandates that a Instead of using Now favicon requests can be managed with more flexibility. Administrators can choose a favicon in the Customizer, or upload a Keep your eyes on the Make WordPress Core blog<\/a> for 5.4-related developer notes<\/a> in the coming weeks, breaking down these and other changes in greater detail.<\/p>\n\n\n\n So far, contributors have fixed more than 255 tickets in WordPress 5.4<\/a> with more to come.<\/p>\n\n\n\n Do you speak a language other than English? Help us translate WordPress into more than 100 languages<\/a>!<\/p>\n\n\n\n If you think you\u2019ve found a bug, 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","protected":false},"excerpt":{"rendered":" WordPress 5.4 Beta 1 is now available for testing! This software is still in development, so we don\u2019t recommend running it on a production site. Consider setting up a test site to play with the new version. You can test the WordPress 5.4 beta in two ways: Try the WordPress Beta Tester plugin (choose the \u201cbleeding edge nightlies\u201d […]<\/p>\n","protected":false},"author":7230939,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"episode_type":"","audio_file":"","cover_image":"","cover_image_id":"","duration":"","filesize":"","date_recorded":"","explicit":"","block":"","filesize_raw":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[5,14],"tags":[],"class_list":["post-8322","post","type-post","status-publish","format-standard","hentry","category-development","category-releases"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pZhYe-2ae","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/8322","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/users\/7230939"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/comments?post=8322"}],"version-history":[{"count":16,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/8322\/revisions"}],"predecessor-version":[{"id":10694,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/8322\/revisions\/10694"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/media?parent=8322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/categories?post=8322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/tags?post=8322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Block Editor: features and improvements<\/h2>\n\n\n\n
Accessibility improvements<\/h3>\n\n\n\n
Continuing efforts to improve performance<\/h3>\n\n\n\n
Wait! There’s more<\/h2>\n\n\n\n
Site Health <\/h3>\n\n\n\n
Accessibility improvements<\/h3>\n\n\n\n
For Developers<\/h2>\n\n\n\n
Calendar Widget <\/h3>\n\n\n\n
<tfoot><\/code> tag must follow <tbody><\/code> tag (which was not the case in the calendar widget). WordPress 5.4 moves the navigation links to a <nav><\/code> HTML element immediately following the <table><\/code> element in order to produce valid HTML.<\/p>\n\n\n\napply_shortcodes() as an alias for do_shortcode()<\/h3>\n\n\n\n
do_shortcode()<\/code>, apply_shortcodes()<\/code> should be utilized instead. While do_shortcode()<\/code> is not being deprecated, the new function delivers better semantics.<\/p>\n\n\n\nBetter favicon handling<\/h3>\n\n\n\n
\/favicon.ico<\/code> file. The WordPress logo will always load as a fallback.<\/p>\n\n\n\nOther changes for developers<\/h3>\n\n\n\n
wp_login_failed<\/code>.<\/li>newblog_notify_siteadmin<\/code> filter for multisite installs.<\/li>How You Can Help<\/h2>\n\n\n\n