WordPress 4.9.6 Release Candidate 2

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

A second release candidate package for 4.9.6 has been released and is now available for testing. Please help test this release candidate version to ensure everything works as expected.

This package contains 20 bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes since the first release candidate. This brings the total number of bug fixes in 4.9.6 to 60 while the number of enhancements/feature requests remains at 34.

Note: With the introduction of #44091, any existing data export requests will need to be removed by an adminadmin (and super admin) and resubmitted.

Even more than usual, we need testers to help polish this release. This version (4.9.6) introduces the first round of tools that help WordPress site owners and admins meet the new requirements for user privacy regulations.

The official 4.9.6 release is scheduled for Thursday, May 17th.

Bug Fixes

A full list of bugs fixed in the 4.9.6 Release Candidaterelease 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). can be found on Trac. The tickets listed below are only those committed since RC1 was released.

Privacy

#44064 – Define $title and $parent_file in privacy.php
#44045 – GDPR WP Pointer dismiss link can be unreachable
#44050 – Privacy: Abandoned heading in WP_Privacy_Policy_Content::get_default_content()
#44048 – Privacy: exclude the wrapper from the default policy content
#44075 – GDPR inline documentation improvements
#44062 – Don’t show privacy feature pointer to new users
#44065 – Remove is-dismissible class from notice when privacy info has changed
#44057 – It’s not obvious what to do if menu bubble for policy update appears
#44056 – Fix markup for table of contents on privacy policy guide
#44076 – Add wp_page_for_privacy_policy to populate_options()
#44026 – Export and Erase Personal Data tables misaligned under 782px
#43491 – Automatically create a Privacy Policy page when installing WordPress
#44063 – Privacy policy guide: do not remove the “Suggested text has changed” bubble on saving the policy page
#44046 – GDPR Privacy Policy Link in wp-login.php page can overflow other links
#44055 – Don’t show notice to the privacy policy guide when user cannot view the guide
#44054 – Escape the comment link output in the wp_comments_personal_data_exporter() function.
#44093 – Proposed Adjustment to Privacy Settings buttons
#44092 – Export/Erase tools: CSSCSS Cascading Style Sheets. issues with next_steps buttons with some locales
#44091 – Rename exports folder to avoid deleting other files
#44079 – Require `manage_privacy_options` capability to edit the privacy policy page

A full list of all changes in 4.9.6 can also be found on Trac.

#4-9-6 #maintenance #release

Welcome!

Communication

Bug Fixes

Privacy

Share this: