WordPress 5.7.1 Release Candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1 (RC1) is available for testing!
Here are two ways to test WordPress 5.7.1 RC1:
- Use the WordPress Beta Tester plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (select the point release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. nightlies option)
- Download the release candidate here (zip)
What’s in this release candidate?
5.7.1 Release Candidate 1 features 23 bug fixes on Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress., as well as 8 bug fixes for the Block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor.
Fixed Core tickets from Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:
- #52787 – Empty array for non-single post meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. breaks post save through REST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.
- #52822 – PHPMailer change in WordPress 5.7 breaks working sites
- #52670 – Admin (and super admin) pointer arrow border color darker than pointer content
- #52713 – Reverse logic in
wp_robots
function and filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. - #52743 – Hardcoded SVG image URLs on WP 5.7 About screen
- #52750 – WP 5.7 colors inconsistent in
get_option( 'admin_color' )
since color contrast changes - #52751 – UI User interface issue on Privacy Policy Guide page
- #52756 – Duplicate video URLs on WP 5.7 About screen
- #52758 – 5.7 About Page: Image comparison doesn’t work on first load on some browsers
- #52760 – Color not accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) for AA
- #52764 – Classic editor adding empty tags in some media embed situations
- #52768 – WordPress post URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org oEmbed rendering blocked by iframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. lazy-loading
- #52783 – Health Check mis-reports https HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. functionality in certain situations
- #52789 – Gallery layout block adds all media items when changing an image
- #52816 – Post metabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. style Twenty Seventeen has a border
- #52826 – New
wp_getimagesize()
causing unexpected failures - #52834 – Reset password screen: improve buttons layout for better i18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.
- #52891 – Privacy: print screen reader text message
- #52894 – The
wp_sanitize_script_attributes
function added in version 5.7 does not escape attributes in some cases - #52932 – Rest Api enum validation does not work correctly WordPress 5.7
- #52961 – Add ‘object-position’ as an allowed CSS Cascading Style Sheets. attribute
- #52981 – Twenty Twenty-One: Update IE specific editor stylesheet
Fixed Block editor issues from GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/:
- PR30218 – Core Data: Use
getAuthors
for showCombobox
- PR30524 – Editor: Revert (#27717) save editors value on change
- PR30122 – Gallery: Set
addToGallery
prop to false when images don’t have IDs - PR29809 – Revert: Show empty paragraphs on fronted
- PR29860 – Try: Fix gallery item clicking
- PR29920 – Fix sibling block inserter displaying at end of block list
- PR30125 – Block Editor: Ensure that uncategorized block types are properly handled
- PR30243 – Add
object-position
to allowed inline style attributes list
What’s next?
The dev-reviewed
workflow (double committer A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) is now in effect when making any changes to the 5.7 branch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..
As per the proposed WordPress 5.7.1 schedule, the final release is expected on Wednesday April 14, 2021 around 23:00 UTC. Please note that this date/time can change depending on possible issues after RC1 is released.
The 5.7.1 release is being lead by @peterwilsoncc and @audrasjb.
#5-7, #5-7-1, #minor-releases, #releases