WordPress 5.5 Beta 4 is now available!<\/p>\n\n\n\n
This software is still in development,<\/strong> so it\u2019s not recommended to run this version on a production site. Consider setting up a test site to play with the new version.<\/p>\n\n\n\n You can test WordPress 5.5 Beta 4 in two ways:<\/p>\n\n\n\n WordPress 5.5 is slated for release on August 11th, 2020<\/a>, and we need your help to get there<\/strong>!<\/p>\n\n\n\n Thank you to all of the contributors who tested the beta 3<\/a> development release and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress. <\/p>\n\n\n\n Since beta 3<\/a>, 43 bugs<\/a> have been fixed. Here are a few changes in beta 4:<\/p>\n\n\n\n WordPress 5.5 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog<\/a> and pay special attention to the developers\u2019 notes<\/a> for updates on those and other changes that could affect your products.<\/p>\n\n\n\n Do you speak a language other than English? Help 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!<\/p>\n\n\n\n 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.5 Beta 4 is now available! This software is still in development, so it\u2019s not recommended to run this version on a production site. Consider setting up a test site to play with the new version. You can test WordPress 5.5 Beta 4 in two ways: Try the WordPress Beta Tester plugin (choose the […]<\/p>\n","protected":false},"author":15049054,"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":[286],"class_list":["post-8719","post","type-post","status-publish","format-standard","hentry","category-development","category-releases","tag-5-5"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pZhYe-2gD","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/8719","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\/15049054"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/comments?post=8719"}],"version-history":[{"count":6,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/8719\/revisions"}],"predecessor-version":[{"id":8730,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/8719\/revisions\/8730"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/media?parent=8719"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/categories?post=8719"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/tags?post=8719"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Some highlights<\/h2>\n\n\n\n
\"loading\"<\/code> as an allowed kses image attribute (see #50731<\/a>).<\/li>$_SERVER['SERVER_NAME']<\/code> not a reliable when generating email host names (see #25239<\/a>)<\/li>Developer notes<\/h2>\n\n\n\n
How to Help<\/h2>\n\n\n\n