Welcome back the latest issue of Week in Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress., covering changes [39380-39529]. Here are the highlights:
- 150 commits
- 63 contributors
- 140 tickets created
- 17 tickets reopened
- 104 tickets closed
- WordPress 4.7 released 🎉
Ticket Created for both bug reports and feature development on the bug tracker. numbers based on trac timeline for the period above. The following is a summary of commits, organized by component.
Code Changes
Administration
- 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): Remove inappropriate content from the Themes screen heading. [39528] #26601
- Accessibility: Remove inappropriate content from the Add Themes screen heading. [39527] #26601
- Accessibility: Remove inappropriate content from the Media Library screens headings. [39526] #26601
Build/Test Tools
- Correctly set up the current screen during list table tests so that they don’t fail when run individually. [39481] #38761
- Specify exact node version in package.json JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.. [39480], [39478] #35105, #38657
- Remove PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 7.1 from allowed failures [39424-39425] #37625
Bundled Theme
- Default Themes: Update version numbers and readme files for 4.7 release [39496] #38858
- Twenty Seventeen: Fix CSS Cascading Style Sheets. specificity problem with CSS feature query for
object-fit
[39495] #39073
- Twenty Seventeen: Improve display of video header The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. and header image in modern browsers [39485], [39483] #39035
- Twenty Seventeen: Add specific font stack for Thai language [39484], [39482] #38937
- Twenty Seventeen: Improve ARIA for the nav menu. [39451-39452] #39029, #39026
- Twenty Seventeen: Ensure header text color updates in Customizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. preview when cleared [39447-39448] #38993
- Twenty Seventeen: Fix broken menu toggle in Customizer after menu items are added [39419], [39423] #38992
- Twenty Seventeen: Fix style issues with gallery image links [39418], [39422] #38969
- Twenty Seventeen: Hide front section panels on page load of Customizer. [39417], [39421] #38951
- Twenty Seventeen: Add
.has-header-video
styles for custom color schemes. [39416] #38995
- Twenty Seventeen: Better handling of custom headers when no image is set. [39413-39414] #38995
- Twenty Seventeen: Make spacing on pages without comments consistent [39404-39405] #38972
- Twenty Seventeen: Make sure header text color is applied when color schemes are active. [39397-39398] #38980
- Twenty Seventeen: Make fixed navigation apply at correct height on front page, without header video or image [39394], [39392] #38927
- Twenty Seventeen: Provide a background color fallback for non-webkit browsers on input styles [39388] #38939
- Twenty Seventeen: Allow child themes to easily extend custom color patterns [39386] #38949
- Twenty Seventeen: Make screen reader text on scroll arrow more meaningful [39384] #38970
- Twenty Seventeen: Keep header videos from extending past footer. [39380-39381] #38950
Comments
- Merge a similar string between comments.php, XML-RPC and the 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/. comments controller. [39508] #39013
Customize
- Prevent infinite full refresh from occurring when selective refresh falls back for a nav menu that has items excluded from rendering via filtering. [39510-39511] #38612
- Defer populating
post_name
for auto-draft
posts in customized state until posts are published. [39506-39507] #39078
- Ensure
changeset_uuid
query param is removed from the customize.php
window’s location once a changeset has been published (committed) with starter content. [39504-39505] #39081
- Prevent posts/pages imported via starter content from being dropped when adding post/page stubs via nav menus and the dropdown-pages control. [39502-39503] #38114, #34923, #39071
- Ensure
textarea
for Custom CSS displays as code (in LTR) when an RTL language is active. [39499-39500] #35395, #39085
- Ensure a
custom_css
post insertion gets an initial post revision. [39479], [39477] #30854, #38672, #35395, #39032
- Custom CSS: Change the help link to something better for users. [39467], [39466] #39015
- Fix posts limit query arg for
WP_Query
from incorrect number
to posts_per_page
. [39434-39435] #39022
- Reuse existing non-auto-draft posts and existing auto-draft posts in the customized state with matching slugs when applying starter content. [39411] #38114, #38928
- Reject a changeset update when a non-future date is provided and also ensure that a published changeset always gets set to the current date/time. [39409-39410] #30937, #38943
- Fix handling of the nav menu item labels (titles) that match defaults (original titles) and fix the display of item type labels. [39395], [39393] #38015, #38955
Feeds
General
- Remove 4.7 cruft from
$_old_files
. [39520-39521] #39113
- Readme: Update recommendations to PHP 7, and to include 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.. [39428-39429] #39024
Help/About
Media
- Accessibility: Improve keyboard accessibility avoiding confusing tab stops in the Media views. [39529] #30599
- Docs: Add inline documentation for
image-edit.js
. [39493] #38748
- Fix regression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. with display of small images in media library. [39399], [39396] #38965
- Docs: Document the usage of the global
$wpdb
in _filter_query_attachment_filenames()
. [39390] #38973
Misc
Options, 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. APIs
- REST API: Register the admin_email setting in single site only. [39470-39472] #38990
- REST API: Site URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org setting should not be present on multisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site installations. [39468] #39005
- REST API: Correct the
admin_email
setting description for single site installs. [39406] #38990
- Multisite: Display different descriptions for multisite or single site installations. [39407] #38990
- Options: Pass the
$passed_default
parameter to the 'default_option_{$option}
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. in add_option()
. [39382] #38176, #38930
Plugins
REST API
- Comments: Merge similar strings between comments.php and the REST API comments controller. [39490-39491] #39014
- Merge similar date strings in the revisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. and comments controllers. [39488-39489] #39016
- Treat any falsy value as
false
in ‘rest_allow_anonymous_comments’. [39487] #39010
- Docs: Add missing REST API-related args to
register_post_type()
and register_taxonomy()
. [39462-39463] #39023
- Merge similar strings in a comments endpoint parameter description. [39457] #39036
- Fix bug 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. where comment author and author email could be an empty string when creating a comment. [39446], [39444] #38971
- Fix handling of some orderby parameters for the Posts controller. [39440-39441] #38971
- Disable
DELETE
requests for users in multisite. [39438-39439] #38962
- Return a
WP_Error
if meta
property is not an array. [39436-39437] #38989
- Add test for creating a comment with an invalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. post ID. [39408] #38991
- Fix incorrect uses of
rest_sanitize_value_from_schema()
. [39400-39401] #38984
Role/Capability
- Don’t assign the
delete_site
capability to anyone on single site installs. [39494] #38326
- Multisite: Replace
is_super_admin()
with manage_network
for admin (and super admin) bar permissions. [39492] #39064, #37616
Taxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.
- Docs: Update an
@since
as there will not be a 4.6.2 before 4.7. [39475-39476] #37291
- REST API: Capability check for editing a single term should use the singular form. [39464] #35614, #39012
- REST API: Use the correct error message when editing a single term. [39460-39461] #39017
- REST API: Fix incorrect capability check on term create. [39402-39403] #35614, #38958
- Performance: Revert [38677] from the 4.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".. This avoids fatal errors caused with recursive calling of term functions within the
get_terms
filter. [39454] #21760
Themes
- Reuse existing non-auto-draft posts and existing auto-draft posts in the customized state with matching slugs when applying starter content. [39412] #38114, #38928
TinyMCE
- Fix the styling of notices generated by the editor UI User interface. [39501] #38917
Users
- Clarify the return value of
get_current_user_id()
for non-logged-in users. [39486] #39051
- REST API: Require the reassign parameter when deleting users. [39426-39427] #39000
Thanks to @andizer, @mor10, @adamsilverstein, @afercia, @azaozz, @boonebgorges, @celloexpressions, @ChopinBach, @clorith, @coffee2code, @davidakennedy, @dd32, @desrosj, @dlh, @flixos90, @georgestephanis, @helen, @helen, @hnle, @iaaxpage, @imnok, @jbpaul17, @jeremyfelt, @jnylen0, @joedolson, @joehoyle, @joemcgill, @johnbillion, @jorbin, @kadamwhite, @karmatosed, @ketuchetan, @laurelfulford, @littlebigthing, @lucasstark, @melchoyce, @michaelarestad, @mikeschroder, @mt8.biz, @nacin, @netweb, @ocean90, @ovenal, @pento, @peterwilsoncc, @presskopp, @rachelbaker, @rahulsprajapati, @ramiabraham, @ramiy, @rensw90, @rianrietveld, @rmccue, @samuelsidler, @sayedwp, @SergeyBiryukov, @sstoqnov, @The PHP tea, @timmydcrawford, @utkarshpatel, and @westonruter for their contributions!
#4-7, #week-in-core