The WordPress core development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
WordPress 5.4 is shaping up to be the best WordPress 2020 has seen!
As a user, you’ll see new blocks and enhancements in the block editor, new embeds, and improvements in the WordPress Admin experience.
As a developer, you’ll see 122 enhancements and feature requests, 210 bug fixes, and more! Of course, all those improvements mean code changes, which could in turn require you to make updates to your site, plugin, or theme.
So take a look through this Field Guide, and see what’s relevant to you and your users, among the many improvements coming in 5.4…
Accessibility
On the 14 updates related to Accessibility in 5.4, you’ll want to particularly note changes to the WordPress Admin Bar, to the calendar and recent comments widgets, on the Menu screen, and bugs reported by the WPCampus accessibility report.
Block Editor
The block editor has continued its rapid iteration since WordPress 5.0. Now it has Gutenberg version 7.5 bundled with WordPress 5.4; that’s ten releases all bundled into WordPress 5.4 (versions 6.6, 6.7, 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4 and 7.5)! Bug fixes and performance improvements from Gutenberg versions 7.6 will also be part of 5.4.
The WordPress 5.4 Beta 1 post highlights a lot of new features and improvements across these releases, though you’ll also want to note the impressive achievement of 14% loading-time reduction and 51% time-to-type reduction (for a particularly long post of ~36,000 words, ~1,000 blocks) since WordPress 5.3.
Below you’ll find details on two new blocks, button component updates, block collections, default fullscreen mode for new installs/devices, custom keyboard shortcuts, general block editor API updates, new block variations API, a new gradient theme API, markup and style-related changes, and a new @wordpress/create-block package for block scaffolding.
On the 14 updates of the Customizer component, WordPress 5.4 improves accessibility of focused elements as a follow-up to WordPress 5.3 Admin CSS changes, adds documentation of existing Customizer functions and hooks, removes apple-touch-icon-precomposed deprecated meta tags, and improves Menu items selection logic.
Please note that some unused Customizer classes are now formally deprecated:
On the 5 updates in the Menus component, WordPress 5.4 improves keyboard accessibility of the Menu items selection tab panel and streamlines the user interface.
If your plugins add custom fields to menu items, you’ll want to update your code to use the new wp_nav_menu_item_custom_fields hook:
On the 22 updates related to the REST API, WordPress 5.4 now supports “OR” taxonomy relation parameter in Post Controller, adds selective link embedding and introduces some changes in the WP_REST_Server method. Read below for more details on these updates:
On the 3 updates to the Shortcodes component, WordPress 5.4 introduces documentation improvements and a new function: apply_shortcodes. This function is an alias of do_shortcode, which is still supported.
On the 9 updates to the Widgets component, WordPress 5.4 introduces accessibility and user interface enhancements on the Widgets Admin screen and changes in the Recent Comments and Calendar Widgets HTML markup.
There are even more goodies in 5.4, like the new wp-env (a zero config tool for painless local WordPress environments), enhancements to favicon handling, better information about errors in wp_login_failed, a new site ID in multisite’s newblog_notify_siteadmin filter, a new TikTok video embed and removal of the CollegeHumor embed, storing the original URL of media attachments in _source_url post meta, improved accessibility by loading the Admin Bar with wp_body_open, avoiding duplicate IDs in the Recent Comments widget, a new parameter in the lostpassword_post action in retrieve_password(), theme headers supporting “Requires at least” and “Requires PHP” declarations, and the delete_posts capability won’t trigger PHP notices for custom post types. Read through the dev notes below to see details on all these changes coming in 5.4.
Over 198 bugs, 121 enhancements and feature requests, and 8 blessed tasks have been marked as fixed in WordPress 5.4. Some additional ones to highlight include:
Bootstrap/Load: Enhancement to favicon handling (#47398)
Bundled Theme: Twenty Twenty: Add social icon for WhatsApp (#49098)
Comments: Add “In response to …” before threaded comments in comment feed (#43429)
In order to prepare a retrospective post, I would like to ask everyone to leave some comments below with things they would like to bring up. To help, here are some questions to ask yourself:
What should WordPress start doing as a part of the development process?
What should WordPress stop doing as a part of the development process?
What should WordPress continue doing as a part of the development process?
Please note that I am looking for feedback specifically on the development and release process.
Please share your thoughts in the comments below!
If you rather not give your feedback in a public space, please reach out to me (@francina) or @davidbaumwald, in Slack. We are available to collect your feedback in a safe space, with no judgement and use it in the retrospective in an anonymous form.
Remember when commenting to keep the discussion professional and focused on ways the process of creating WordPress is either already working great or can be improved.
The a11y team had a look at the audit tickets at their weekly meeting and had a few recommendations.
Based on a11y team feedback, we agreed to add notes to the audit on any CSS properties we find that are unhelpful for accessibility.
Open Floor
@joyously requested we add a channel topic to #core-css, with the time of our weekly meeting, which we did.
@joyously asked if the audit would include editor CSS, or only wp-admin pages. The current audit includes only wp-admin pages, but there was agreement on auditing both the editor and the default themes CSS at a later stage.
That was all for this week!
Next week @notlaura will be taking over the running of this meeting, due to daylight savings changes.
At the moment, those events don’t show up in the News & Events widget on the dashboard, because they don’t have a physical location. The widget was originally designed to show the user local events, because cultivating local, in-person bonds is an essential element of our community’s success.
Online events aren’t being intentionally kept out of the widget; it’s just an unforeseen side-effect of the temporary shift to online events. Online meetup events still appear in the widget, because in the absence of an explicit event location, the Meetup.com API falls back to the location of the group.
Questions
Should online WordCamps show up in the widget?
If so, who should they be shown to? Here are a few potential criteria:
The same people who would have seen the in-person event. i.e., anyone within a 400km radius of the venue.
Everyone within the same country. Would this apply equally to countries that host a small number of camps, and those that host a large number? Would it apply equally to countries that often see people from neighboring countries traveling to attend the event, and to countries where that is not common?
Everyone within an increased radius, e.g., 600km. If so, what would be the best distance?
Everyone within the same timezone, plus-or-minus a few hours.
Everyone who speaks the same language— or locale? — as the host city.
A combination of the above? Some other criteria entirely?
Should the timezone and/or language of the event be displayed in the dashboard?
@audrasjb shared the stats for contributors to the release. There was a total of 552 contributors from 48 countries, 32% of them being new contributors. For more accurate release contributors statistics, please fill in your WordPress profile (if you want).
Highlighted Blog Posts
@davidbaumwald shared the posts of Core Privacy team about the WP Consent API feature plugin proposal and the Guidelines for Internet Explorer 11 support in WordPress.
Upcoming Releases
@davidbaumwald reminded that 5.5 has been in Alpha phase for a while now.
Components Check-in
@audrasjb announced the release of version 0.4 of Auto-updates plugin which contains all features initially planned fot the project; as well as Themes updates and email notifications. Design, copy and accessibility reviews and feedback are welcome from plugin authors and WordPress developers.
@azaozz shared the link of WordPress 5.4 master list in support forums. Please, go through this before posting a topic in the forums.
@ipstenu and @azaozz called for attention on respectively these two tickets #49753 and #4975, related to 5.4.
@howdy_mcgee pointed to #24780 and said he has made a document to track the supression operators in Core codebase.
@jeffpaul asked we should start taking a look at the 5.5 early tickets to review patches and look to get some of those in sooner. Here’s for reference the Trac query for 5.5 tickets.
@jeffpaul also suggested to schedule an early-specific bug scrub in the next couple of weeks to help move those tickets along. A few people voluntereed to lead these scrubs.
@bph reminded that the WPBlockTalk is happening on April 2, and everyone is welcome to register here.
Full Site Editing: Continue improving the Edit Site screen and blocks
Global Styles: This will be a big one this month (support in blocks and UI)
Updated Inserter UI to support patterns and blocks
Updated Navigation/Menus screen
Continue G2 iterations
Release of 7.9 will be pushed one week to account for additional work on Global Styles project that can have some impact on themes. The extra week would be useful to polish the global styles support across different blocks and document the potential impacts properly.
Release of 5.4.1 is not scheduled. Please mark PR’s/issues with `Backport to WP Core` and keep an eye for potential high impact issues that we may want to include in it.
Besides the release, last Friday, we also did a WordPress 5.4 RC 5 that included some fixes to problems discovered with the editor. More details of the fixes can be found here and here.
The Good news is WordPress 5.4 is out with no incidents reported during the release and It already has 2.6 million downloads. The situation in the world was far from normal, but we managed to take the release to the finish line and solve the critical issues as soon as they were discovered/reported, so thank you a lot to all that made this possible
Making font-size an implicit attribute of the block.
For next week, carry on with those and revive this exploration for Global Styles that uses general variables while allowing for targeting specific blocks.
Starting last week I am focusing back on Navigation block and nav-menus.php
Work from the past two weeks is blocked by lack of reviewers. There are several PRs open and waiting for reviews / comments with new features for the Latest Posts block.
Continue adding/improving style attributes to blocks to enable better customization
PRs Needing Review
Refactor ReusableBlockEditPanel to use hooks (and add type info) 21181 Navigation block: show color controls in toolbar only. 20884 [Latest Posts] adds author option to latest posts block 20595 Refactor ReusableBlockEditPanel to use hooks (and add type info) 21181 Add tags in latest posts block 20785 Table of Contents block 21234 Insert post title instead of URL, when adding a link to an existing post 21240 This issue needs review for a possible PR: Bug: Link sometimes embeds other times not. 21029
Open Floor
@julescole PR 21240 Insert post title instead of URL, when adding a link to an existing post
@paaljoachim I am very hyped on @shaunandrewsPR 21121 as I believe it would make going in and out of full screen a lot easier. But we can wait and see what kind of feedback shows up in regards to the full screen mode that is included in 5.4. (edited)
@zebulan For fun, I made a PR to refactor ReusableBlockEditPanel to use hooks. I have no idea if it runs faster (or how to even test that), but the code feels cleaner to me. Also, the PR adds JSDoc type information. Reviews/feedback are welcome as always. Also can use some eyes on a Table of Contents PR.
Having an issue with not being able to grab unpublished permalinks. You can read more about it in core-js but the gist of it is that I’m not sure where the change should occur.
When we actually click to preview it, it can’t use the future permalink because it isn’t live yet. That won’t route and will return a 404. So we have to use the ?p=123 type link for the href on scheduled posts. But we could generate what it would look like using the permalink template and placeholders
Got something to propose for the agenda, or a specific item relevant to our standard list above?
Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly.
This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.
We welcome all thoughts on this proposal, which you are welcome to leave as comments on this post, or share with us directly in the #core-privacy channel on Making WordPress Slack. We host weekly office hours on Wednesdays at 19:00 UTC, see the meetings page for times in your timezone.
Introduction
A standard way for WordPress core, plugins, and themes to obtain consent from users should be established to provide a consistent and stable experience for administrators, developers, and users of all kinds.
Currently it is possible for a consent management plugin to block third party services like Facebook, Google Maps, Twitter, if a user does not give consent. But if a WordPress plugin places a PHP cookie, a consent management plugin cannot prevent this.
There are also WordPress plugins that integrate tracking code on the client side in javascript files that, when blocked by a consent management plugin, break the site. Or, if such a plugin’s javascript is minified, causing the URL to be unrecognizable, it won’t get detected by an automatic blocking script.
Lastly, the blocking approach requires a list of all types of URL’s that place cookies or use other means of tracking. A generic API which plugins adhere to can greatly help a webmaster in getting a site compliant.
Does usage of this API prevent third party services from tracking user data?
Primarily this API is aimed at helping to achieve a compliant use of cookies or other means of tracking by WordPress websites. If a plugin or custom code triggers for example Facebook, usage of this API will be of help to ensure consent. If a user manually embeds a facebook iframe, a cookie blocker is needed that initially disables the iframe and or scripts.
Third-party scripts have to be blocked by a blocking functionality in a consent management plugin. To do this in core would be too intrusive, and is also not applicable to all users: only users with visitors from opt in regions such as the European Union require such a feature. Such a feature also has a risk of breaking things. Additionally, blocking these and showing a nice placeholder, requires even more sophisticated code, all of which should not be part of WordPress core, for the same reasons.
That said, the consent API can be used to decide if an iframe or script should be blocked.
How does it work?
There are two indicators that together tell if consent is given for a certain consent category, e.g. “marketing”:
The region based consent_type, which can be optin, opt out, or other possible consent_types;
The visitor’s choice: not set, allow or deny.
The consent_type is a function that wraps a filter, wp_get_consent_type. If there’s no consent management plugin to set it, it will return false. This will cause all consent categories to return true, allowing cookies and other types of tracking for all categories.
If optin is set using this filter, a category will only return true if the value of the visitor’s choice is allow.
If the region based consent_type is opt out, it will return true if the visitor’s choice is not set or is allow.
Clientside, a consent management plugin can dynamically manipulate the consent type, and set the applicable categories.
A plugin can use a hook to listen for changes, or check the value of a given category.
Categories, and most other stuff can be extended with a filter.
