A Week in Core – June 14, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between June 7 and June 14, 2021.

  • 63 commits
  • 105 contributors
  • 57 tickets created
  • 6 tickets reopened
  • 65 tickets closed

Please note that the WordPress Core team released WordPress 5.8 beta 1 last week. Everyone is welcome to help testing the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. of WordPress 🌟

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Administration

  • Adjust Internet Explorer message to be a bit more clear – #48743
  • Escape the values of data-colname – #40401
  • Introduce dashboard notice to discourage use of out of date browser – #48743

Application Passwords

  • Allow enter key to submit profile form – #52849

BlockBlock 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

  • Add a type property to allow Core to identify the source of the editor styles – #53175
  • Add the Site Logo block’s server implementation – #53247
  • Allow themes to add inline styles for all blocks when using lazy styles loading – #53358
  • Fix typo in the typography block support – #52991
  • Ignore generated CSSCSS Cascading Style Sheets. files in Page List and Post Template blocks – #52991, #53309
  • Include the page list block server-side code – #53309
  • Package updates for 5.8 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 – #52991
  • Package updates for WordPress 5.8 beta 1 (batch2) – #52991
  • Prevent duplicate queries – #53280, #53176
  • Ensure that the block editor can be used on the page post type – #45537

Boostrap/Load

  • Add filterFilter 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. to allow disabling of object cache – #53322

Build/Test Tools

  • Ensure that we are using https:// urls – #39589
  • Silence jQuery Migrate console warnings when running E2E tests – #52860
  • Update devDependencies for bundled themes – #52624
  • Update several devDependencies#52624

Bundled Themes

  • Introduce block patterns for Twenty Eleven – #51106
  • Introduce block patterns for Twenty Ten – #51107
  • Twenty Nineteen: Fix pullquote styling in editor when block has alignment – #53112
  • Twenty Nineteen: Set a default color for button links in the editor – #52555
  • Twenty Thirteen: Add “No Shadow” style to button block – #51223
  • Twenty Twenty: Ensure custom primary color is applied to text in the editor – #50120
  • Twenty Twenty: Regenerate the RTL editor stylesheet – #50120
  • Apply an alignment fix – #53246
  • Extraneous white space at end of line – #51189
  • Use single quotes when there are no variables withi/n the string – #48743

Comments

  • Return valid comment reply link if comments are paginated – #51189

Documentation

  • Correct DocBlockdocblock (phpdoc, xref, inline docs) formatting for some revision tests – #52628
  • Document the usage of $wp_widget_factory global in WP_Customize_Widgets::sanitize_widget_instance()#53394
  • Update documentation for some WP_Customize_Widgets methods per the documentation standards – #52628

Emoji

  • Update the Twemoji library to version 13.1.0 – #52852

Feeds

  • Avoid notices in get_post_comments_feed_link()#52814

Login and Registration

  • Improve the unknown username error message – #52915
  • Wrap long site titles to a new line – #52776

Media

  • Add new functions to return the previous/next attachment links – #45708
  • Allow multi-uploads in Galleries – #53169
  • Ensure that post_id variable is initiated ahead of usage – #39589
  • Restore AJAX response data shape in media library – #50105

Permalinks

  • Limit pagination for posts with comments – #50233
  • Revert the changes stemming from pagination limits – #50233

Privacy

  • Improve naming of user confimed action email filters – #44314

RevisionsRevisions 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.

  • Check and return errors for insertions to revisions – #30009

Script Loader

  • Fix 404 errors for the jquery-masonry script when SCRIPT_DEBUG is true#47353

Site Health

  • Display a list of file formats supported by the GD library – #53022

Tests

  • Fix typo in a get_bookmarks() test name – #52625
  • Fix typo in a retrieve_widgets() test name – #52625
  • Ignore EOL differences in some tests using multiline string assertions – #52625
  • Introduce some E2E tests for the Quick Draft dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. – #523905
  • Use assertSameSets() in some newly introduced tests – #52625

Themes

  • Fix accessibilityAccessibility 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) issues with controls in themes screen – #52649

TinyMCE

TinyMCE

  • Fix initialization when the editor is in a postbox by delaying it until document.readyState === 'complete'#52133, #52050

Upgrade/Install

  • Built files should not be included in the $_old_files list – #53367
  • Remove parsing of readme.txt files for pluginPlugin 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 or theme requirements – #48520, #48515, #meta2952, #meta4514, #meta4621
  • Update the $_old_files list for 5.8 – #52991, #52846, #53246, #53367

Widgets

  • Don’t decode HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. entities ahead of the widget constructor – #53138
  • Make new WordPress installations use blocks in widget areas instead of widgets – #53324
  • Ensure that HTML entities are converted in widget descriptions – #53138
  • Improve unit tests for RSS Widget – #53278
  • Prevent infinite loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. in PHP8+ if the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for the widget instance is incorrectly defined – #53278

Props

Thanks to the 105 (!) people who contributed to WordPress Core on Trac last week:

@audrasjb (10), @SergeyBiryukov (8), @desrosj (8), @hellofromTonya (7), @sabernhardt (5), @isabel_brison (4), @whyisjake (4), @dd32 (3), @johnbillion (3), @alexstine (3), @adamsilverstein (3), @kjellr (3), @melchoyce (3), @antpb (2), @jorbin (2), @jorgefilipecosta (2), @peterwilsoncc (2), @beafialho (2), @jeffpaul (2), @aristath (2), @davidbaumwald (2), @mukesh27 (2), @chanthaboune (2), @youknowriad (2), @poena (2), @ocean90 (2), @azaozz (2), @DrewAPicture (2), @nosolosw (2), @boniu91 (1), @geekpress (1), @mikejolley (1), @ntsekouras (1), @scruffian (1), @mcsf (1), @sumitsingh (1), @Chouby (1), @onemaggie (1), @danieldudzic (1), @devnel (1), @timothyblynjacobs (1), @notlaura (1), @metalandcoffee (1), @paaggeli (1), @MrPauloEn (1), @mkdgs (1), @dway (1), @spikeuk1 (1), @herrvigg (1), @patkemper (1), @promz (1), @pondermatic (1), @andraganescu (1), @hellofromtonya (1), @noisysocks (1), @Boniu91 (1), @williampatton (1), @joyously (1), @Otto42 (1), @afragen (1), @wpgurudev (1), @hannahmalcolm (1), @achbed (1), @coffee2code (1), @coreymckrill (1), @rmccue (1), @marybaum (1), @dlh (1), @lukecarbis (1), @xkon (1), @helen (1), @TZ-Media (1), @pento (1), @Mista-Flo (1), @pbiron (1), @lifeforceinst (1), @birgire (1), @garrett-eclipse (1), @kapilpaul (1), @jontyravi (1), @david.binda (1), @joedolson (1), @glendaviesnz (1), @flixos90 (1), @gitlost (1), @spacedmonkey (1), @kraftbj (1), @justinahinon (1), @hareesh-pillai (1), @rellect (1), @knutsp (1), @grantmkin (1), @ArnaudBan (1), @Fantasy1125 (1), @swissspidy (1), @mor10 (1), @cameronjonesweb (1), @jeherve (1), @netweb (1), @afercia (1), @chaion07 (1), @sumanm (1), @carike (1), @devrekli (1), and @engahmeds3ed (1).

Congrats and welcome to our 6 new contributors of the week! @pondermatic, @lifeforceinst, @Fantasy1125, @cameronjonesweb, @sumanm, and @devrekli ♥️

Core committers: @desrosj (16), @whyisjake (10), @sergeybiryukov (8), @ryelle (8), @youknowriad (7), @joedolson (5), @antpb (4), @jorbin (3), @azaozz (2), @peterwilsoncc (1), and @noisysocks (1).

#5-8, #meta2952, #meta4514, #meta4621, #week-in-core

Dev Chat Summary: June 09, 2021

@peterwilsoncc and @desrosj led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Blogblog (versus network, site) Post Highlights

@audrasjb shared the weekly recap of code changes and contributors in the latest issue of A Week In Core: 07 June 2021. Thanks to the 72 (!) people who contributed, the 12 (!!) new contributors, and the 11 💖 core committers who helped land these changes last week.

@annezazu shared Editor team updates on Full Site Editing, Navigation BlockBlock 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., Mobile Editor, and Block Based Widgets Editor from their last meeting: Editor Chat Summary: 02 June 2021.

@danfarrow shared CSSCSS Cascading Style Sheets. team updates on Color Scheming, CSS Audit, and CSS Deprecation Path, but click through to the meeting notes for a CSS Trick that you won’t believe! For more information, see CSS chat summary: 03 June 2021.

@priethor shared details on what’s coming up in Gutenberg including final polishes for WordPress 5.8, Widgets Editor, Navigation Editor, Full Site Editing various milestones.

Kudos to @adamsilverstein for publishing the first dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. of the release covering the addition of WebP support. Click through to learn how WebP helps you, how to create and use WebP images, plans for the future, and some FAQ items.

@chanthaboune announced a new Make/Project site for all-project communications and cross-team collaboration, so drop your email in that subscribe form and stay up-to-date on all the important topics across the WordPress project.

@jorbin shared the dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. on Bootstrap/Load Changes in 5.8.

@chanthaboune also shared initial designs on a forthcoming News blog design update, its so lovely go check it out.

Blog posts that need feedback

@annezazu has a reminder for us that the current FSE call for testing has one week left until June 16th, so please try crafting a Polished Portfolio.

WordPress 5.8 update

A ‘Big Thank You’ to everyone that helped get everything in order so that BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 could be packaged on time this week! The 5.8 Beta 1 post does not itself need feedback so much as testing from anyone and everyone able to in order to help ensure as smooth a release as possible next month.

Please check the post for details on highlights from the release and links to get you on your way to testing. As it’s still in development, it’s not recommended to run on a production siteProduction Site A production site is a live site online meant to be viewed by your visitors, as opposed to a site that is staged for development or testing. but testing on development and staging servers would be most helpful. The simplest way of testing is to use the beta tester plugin. In terms of ongoing development, WordPress 5.8 now focuses on tasks in the milestone and on regressions (bugs) found during the beta testing cycle.

Our next milestone will be Beta 2 in SIX days on this coming Tuesday, June 15th.

@chaion07 led the final 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. scrubs this past week. The next bug scrub is due to be run on Monday, June 14, 2021, 20:00 UTC.

Components check-in and status updates

  • Plugins: The Requires PHP and Requires at least pluginPlugin 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 headers could previously be specified either in the plugin’s main PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher file or in readme.txt as a fallback. This has now changed for WordPress 5.8, only placing them in the plugin’s main PHP file will be supported from now on. Same goes for themes, the Requires PHP and Requires at least headers should be placed in the theme’s style.css file instead of readme.txt. The reason for this change is that any data in readme.txt is meant for the Plugin or Theme Directory only, and not for WordPress core. Core should retrieve all the necessary data from the plugin’s main PHP file or the theme’s style.css file instead. See changeset [51092] and ticketticket Created for both bug reports and feature development on the bug tracker. #48520 for more details. Thanks @afragen for working on this!
  • Help/About: Work will begin this week on the 5.8 About page. Join in on the discussion over on #52775.
  • All other components: No major updates to report.

Open Floor

@webcommsat pointed out on the video content in Matt’s talk at WCEU which would be valuable to re-highlight when those features land too. Additoionally, Abha thanked everyone for the Contribute to WP resources, workshops and discussion areas at WCEU. The content will continue to be available on the site and we are adding new resources submitted. It will help bridge and encourage people to discover Make WordPress materials and the Learn Project.

Props @desrosj for peer review prior to publishing.

#5-8, #dev-chat, #summary

Bootstrap/Load Changes in 5.8

WordPress 5.8 brings some small changes to the Boostrap/Load component.

  • timer_float is a new function that can be used to reliably determine the total time from the start of php execution. See #39163
  • Inline comments were updated to make it clearer in wp-config-sample.php where custom configuration variables should go and wp-load.php to help improve the understanding of error level reporting. See #37199 and #41902
  • Fatal error recovery was updated to not say an email was sent when it was impossible to send the email. See #52560
  • enable_loading_object_cache_dropin is a new filterFilter 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. to allow disabling of the object cache dropin. See #53322

Thank you to all of the people who contributed to the Bootstrap/Load component in 5.8.

Props to @desrosj for review and edits.

#5-8, #bootstrap-load, #dev-notes

Dev Chat Agenda for June 9, 2021

Here is the agenda for this week’s developer meetings to occur at the following times: June 9, 2021 at 5:00 UTC and June 9, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Schedule Review

  • BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 released yesterday, so now in Beta window with Beta 2 in 6 days on Tuesday, June 15th
  • Focus now fully on tasks in the milestone and regressions found in Beta releases
  • Next Beta Scrub before Beta 2 is Monday, June 14th 20:00 UTC
  • RC 1 in 20 days on Tuesday, June 29th
  • 5.8 release in 41 days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items 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.

#5-8, #agenda, #dev-chat

A Week in Core – June 7, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between May 31 and June 7, 2021.

  • 40 commits
  • 72 contributors
  • 53 tickets created
  • 5 tickets reopened
  • 77 tickets closed

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Administration

  • List Tables: Update spacing in action items on small screens – #48546, #47895

Application Passwords

  • Allow enter key to submit profile form – #52849

BlockBlock 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

  • Add a type property to allow Core to identify the source of the editor styles – #53175
  • Add the Site Logo block’s server implementation – #53247
  • Load the WP_Theme_JSON_Resolver class in wp-admin/load-styles.php#53175
  • Package updates for 5.8 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 – #52991
  • Update script versions – #52991
  • Correct some docblocks added in [50836]#50328, #52620
  • Fix failing block editor test – #53301

Boostrap/Load

  • Add filterFilter 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. to allow disabling of object cache – #53322
  • Only reference recovery mode email when it can be sent – #52560

Build/Test tools

  • Remove the ::append_to_selector() method from Tests_Theme_wpThemeJson#52991
  • Use assertSame() in some newly introduced tests – #52482

Bundled Themes

  • Twenty Twenty-One: Check for navigation element before using it – #52773

Coding Standards

  • Extraneous white space at end of line – #51189
  • Simplify a condition in wp-admin/admin-footer.php#53306
  • Simplify the logic in WP_Widget::get_field_name() and ::get_field_id()#16773, #52627
  • Use strict comparison in wp-admin/options-media.php#52627

Comments

  • Escape comment author’s email in the Edit Comment form – #53349
  • Return valid comment reply link if comments are paginated – #51189

Documentation

  • Add a @since note to wp_parse_id_list() and wp_parse_slug_list() about using wp_parse_list()#52628
  • Correct type for the $widget parameter of the widget_block_content filter – #51566

External Libraries

  • Update the Requests library to version 1.8.1 – #53334

Plugins

  • Make sure Hello Dolly translations are deleted when the pluginPlugin 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 is deleted – #52817

REST APIREST 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/.

  • Add ‘delete_widget’ action to delete widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. endpoint – #53289
  • Delete fresh_site option when updating widgets via REST API – #53317
  • Fix delete widget endpoint – #53313
  • Rename the $creating parameter of rest_after_save_widget action to $update#53317
  • Restore the $creating parameter of rest_after_save_widget action – #53317

Site Health

  • Conditionally run Authorization headerHeader 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. test – #52642
  • Remove unnecessary function_exists() checks from WP_Site_Health::get_tests()#52642

Themes

  • Fix accessibilityAccessibility 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) issues with controls in themes screen – #52649

TinyMCE

  • Don’t attempt to initialize the same instance twice. Follow up to [51082]#52133, #52050
  • Fix initialization when the editor is in a postbox by delaying it until document.readyState === 'complete'#52133, #52050

Upgrade/Install

Users

  • Add user’s localeLocale A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English. to password reset link to ensure login screen matches the language of the email – #34281, #52605, #53321

Widgets

  • Add widget_block_content filter – #51566
  • Add missing actions to widgets block editor – #53288
  • Enable MetaMeta 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. and Nav Menu widgets in Legacy Widget block – #53301
  • Make new WordPress installations use blocks in widget areas instead of widgets – #53324

Props

Thanks to the 72 people who contributed to WordPress Core on Trac last week:

@TimothyBlynJacobs (4), @SergeyBiryukov (3), @nosolosw (3), @isabel_brison (3), @andraganescu (3), @alexstine (3), @costdev (3), @hellofromtonya (2), @sabernhardt (2), @joyously (2), @audrasjb (2), @jorgefilipecosta (2), @justinahinon (1), @jipmoors (1), @westonruter (1), @drebbits.web (1), @afragen (1), @stevenkword (1), @jorbin (1), @lukecarbis (1), @jdgrimes (1), @tamlyn (1), @solarissmoke (1), @5ubliminal (1), @helen (1), @celloexpressions (1), @Mte90 (1), @hellofromTonya (1), @kevin940726 (1), @garrett-eclipse (1), @y_kolev (1), @Clorith (1), @Otshelnik-Fm (1), @JeffPaul (1), @talldanwp (1), @WebDragon (1), @dlh (1), @pbiron (1), @jamil95 (1), @sushmak (1), @stevegrunwell (1), @aliveic (1), @mkdgs (1), @williampatton (1), @aristath (1), @timothyblynjacobs (1), @ocean90 (1), @noisysocks (1), @promz (1), @poena (1), @metalandcoffee (1), @desrosj (1), @patkemper (1), @herrvigg (1), @spikeuk1 (1), @dway (1), @azaozz (1), @notlaura (1), @MrPauloEn (1), @paaggeli (1), @engahmeds3ed (1), @utsav72640 (1), @kapilpaul (1), @jrf (1), @schlessera (1), @mbabker (1), @walbo (1), @reynhartono (1), @Otto42 (1), @arunsathiya (1), @danfarrow (1), and @mukesh27 (1).

Congrats and welcome to our 12 new contributors of the week! @costdev, @5ubliminal, @WebDragon, @sushmak, @mkdgs, @patkemper, @herrvigg, @spikeuk1, @dway, @MrPauloEn, @kapilpaul, and @reynhartono. ♥️

Core committers: @sergeybiryukov (15), @noisysocks (8), @joedolson (4), @youknowriad (3), @jorbin (2), @azaozz (2), @ryelle (2), @ocean90 (1), @johnbillion (1), @peterwilsoncc (1), and @clorith (1).

#5-8, #meta2952, #meta4514, #meta4621, #week-in-core

WordPress 5.8 adds WebP support

WebP is a modern image format that provides improved lossless and lossy compression for images on the web. WebP images are around 30% smaller on average than their JPEG or PNG equivalents, resulting in sites that are faster and use less bandwidth. WebP is supported in all modern browsers according to caniuse.

From WordPress version 5.8 forward, you can upload and use WebP images in WordPress like you would a JPEG or PNG image today (as long as your hosting service supports WebP). Switching to the WebP format for your images will improve your site’s performance and your site visitor’s experience. 

How WebP Helps You

WebP images are significantly smaller than their JPEG equivalents, so visitors to your site will see the complete page loaded more quickly. Smaller images take less bandwidth to transmit, and your images still get all of the responsive benefits of srcset and lazy loading by default. Finally, WebP is supported in all major browsers, so most sites can start using them today.

Creating WebP images

Image editing tools support exporting in WebP, or you can also use command line conversion tools or web based tools like Squoosh. Once you save your images as WebP, upload them to WordPress and use them like you would any other image. 

Using WebP images

WebP images work like any other image in WordPress with some small caveats. 

WebP images support lossy and lossless compression, as well as an animated format and support for transparent images. In WordPress, the lossless WebP format is only supported when the hosting server uses Imagick (the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher library) until LibGD adds support. In addition, animated and alpha formats are not yet supported for resized images (lossy images are created instead when you upload in these formats).

WebP support in the media library requires that your web server’s image processing library (WordPress supports both Imagick and LibGD) supports the WebP format. Fortunately these libraries have supported WebP for quite a while so support is widely available. If your web server does not support WebP, you will see an error message when you try to upload a WebP image.

If your audience includes a significant number of users on an unsupported browser (IE11 for example), either avoid using WebP images, or  enqueue a browser polyfill.

Plans for the future

The media component team is also exploring the option of having WordPress perform the image format conversion on uploaded images – using WebP as the default output format for sub-sized images. You can track progress and test this feature on the trac ticket. We are also keeping our eyes on even more modern formats like AVIF and JPEGXL that will both improve compression and further reduce resources required for compression.

FAQ

How can I fine tune the compression quality setting used for WebP images?

Developers or plugins can use the wp_editor_set_quality filterFilter 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. to set the quality setting. The passed mime type enables setting by type, for example:

// Use a quality setting of 75 for WebP images.
function filter_webp_quality( $quality, $mime_type ) {
  if ( 'image/webp' === $mime_type ) {
     return 75;
  }
  return $quality;
}
add_filter( 'wp_editor_set_quality', 'filter_webp_quality', 10, 2 );

What happens if I enable the filter to use WebP sub-sizes, but upload JPEG? Do the sub-sizes have to match the original?

By default, WordPres creates the sub-sized images of the same type as the uploaded file, so uploaded WebP files to get WebP files on your site. If you want to experiment with uploading JPEG and having WordPress auto-convert these to WebP for your sub-sized images, check out this plugin (related trac ticket).

If I use WordPress multisitemultisite 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, will all my sites work with WebP images?

No. Multisite stores the file types that users are allowed to upload when a site is created. We are working on improving this in #53167. In the meantime, to ensure all existing sites on a networknetwork (versus site, blog) allow WebP files, you can use the site_option filter in a network mu-pluginPlugin 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 to add webp to the allowed file types for all network sites:

// Ensure all network sites include WebP support.
add_filter(
  'site_option_upload_filetypes',
  function ( $filetypes ) {
    $filetypes = explode( ' ', $filetypes );
    if ( ! in_array( 'webp', $filetypes, true ) ) {
      $filetypes[] = 'webp';
      $filetypes   = implode( ' ', $filetypes );
    }

    return $filetypes;
  }
);

#5-8, #core-images, #dev-notes, #images

DevChat meeting Summary – June 2, 2021

@peterwilsoncc and @jeffpaul led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Blogblog (versus network, site) post hightlights

In the last “Week in Core” issue, @audrasjb featured 98 contributors, 13 new contributors to WordPress source code and 12 core committers.

@priethor shared details on Gutenberg 10.7 including new features like the persistent List View in the Post Editor, responsive navigation menus, many design tools for blocks, and enhancements to the top toolbar, as well as iterative performance improvements and a lot of 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.

@danfarrow shared CSSCSS Cascading Style Sheets. team updates on color scheming, CSS audit, and CSS deprecation path from their last two meetings. For more information, see CSS chat summaries for May 20th and May 27th.

Blog posts that need feedback

@annezazu extended the FSE Program Testing Call #7 from June 9th to June 16th, so please check the post to learn about the feature overview, how to set up your testing environment, and the desired testing flow to help out on this.

@webcommsat has a related ask ahead of Friday’s deadline for suggestions of external channels for the promotion/info share on FSE to various audiences. Everyone is welcome to review and add suggestions in the comments.

@meaghanthompson shared a call for testing the WordPress iOS 17.5 beta, so please check the post to learn about what’s new in the release, what’s most in need of testing, how to set up the test app, and how to report issues you find.

WordPress 5.8 update

@jeffpaul shared a 5.8 schedule reminder: we are now in the Feature Freeze period where focus shifts away from enhancements and feature requests to defects and tasks.

@chaion07 and @francina led different bug scrubs this past week. There’s a final bug scrub on Monday, June 7th at 20:00 UTC to work to clear the milestone before the BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 release the next day. Here is the full bug scrubs schedule.

The next milestone will be Beta 1 on Tuesday June 8, 2021 after which point the focus will shift to testing and fixing bugs discovered during the 3 weeks beta period.

There are two “big” remaining tasks and a call for help from @youknowriad:

  • The Query blockBlock 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. where the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ team had some feedback about it being too powerful (need to find better heuristics to disable editing there). Feel free to contribute to the discussion. There is also a subset of this issue.
  • A proposal to change in how edited block templates are linked to themes (using theme mod instead of taxonomies). The Gutenberg team would appreciate some thoughts here from Core folks familiar with these APIs (theme mods, performance, database).

Also, these are the dev notes that need to be written for the editor.

@youknowriad shared that he consider that the Core team is ready for Beta 1, ideally, we’d have some improvements for the Query block by then but not sure if it’s necessary for beta 1.

WP 5.8 Docs focus update

@milana_cap shared that out of 165 tickets, 35 (Gutenberg excluded) are marked for some sort of documentation:

  • 28 for dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.
  • 5 for updating DevHub
  • 12 for updating HelpHub

Gutenberg will have:

  • 10 dev notes (as per the list shared by @youknowriad)
  • 12 updates for dev docs
  • many updates for end user docs

Everything except block editor end user updates can be found in this spreadsheet. Block editor end user updates can be found in this Drive folder.

Docs needs the most help with end user documentation. For block editor in particular. Some changes from 5.6 and 5.7 are still not published and we had a significant drop in number of contributors due to pandemic situation. Anyone interested in getting involved please pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @milana_cap (zzap on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.). 

Components check-in and status updates

Build/Test Tools, Date/Time, I18Ni18n 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., Permalinks (@sergeybiryukov): No major news this week.

Upgrade/Install (@audrasjb): @francina hosted the weekly meeting and posted the meeting notes.

Menus, Widgets (@audrasjb): no major news this week.

Open floor

@poena has a request on the agenda post for anyone with knowledge on adminadmin (and super admin) pointers:

Theme Check is a pluginPlugin 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 used to analyze themes submitted to the theme directory. I’m looking for someone who knows about admin pointers and if this issue from 2016 is still valid. Does the core team want themes with wp_enqueue_script( ‘wp-pointer’ ); or wp_enqueue_style( ‘wp-pointer’ ); to be blocked from the theme directory? The theme would not be able to be uploaded.

If you’re experienced with admin pointers, please respond to the comment on the agenda post or respond in the linked GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ issue above.

@webcommsat pointed out that WordCamp Europe is Monday to Wednesday next week!

#5-8, #dev-chat, #summary

A Week in Core – May 31, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between May 24 and May 31, 2021.

  • 65 commits
  • 98 contributors
  • 48 tickets created
  • 11 tickets reopened
  • 83 tickets closed

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Administration

  • Improve the message about installing the Link Manager pluginPlugin 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 to use legacy Links screen – #52669

BlockBlock 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

  • Load the classic layout stylesheet conditionallty – #53175
  • Add the layout block support – #53175
  • Declare the wp_template post type as built-in – #53176
  • Only load the WP_Theme_JSON_Resolver class once – #53175, #51104
  • Add support for the pattern directory – #53246
  • Fix logic to enable custom colors, gradients, and font sizes – #53175
  • Update the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ branchbranch 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". used to launch Gutenberg e2e tests – #52991
  • Update packages and backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. the latest Gutenberg fixes – #52991
  • Introduce block templates for classic themes – #53176
  • Load theme resolver class in script loader – #53175

Build/Test Tools

  • Update the several dependencies – #52624
  • Minimize the chances of signature conflicts for assertEqualsWithDelta()#52625
  • Use deterministic module ids in webpack for media – #53192
  • Remove the ::append_to_selector() method from Tests_Theme_wpThemeJson#52991
  • Use the Composer-installed version of PHPUnit for Grunt tasks – #53015
  • Use hashed module IDs for minified files – #53192

Bundled Themes

  • Introduce block patterns for Twenty Fourteen – #51103
  • Introduce block patterns for Twenty Fifteen – #51102
  • Update the “Tested up to” value – #53276
  • Introduce block patterns for Twenty Twelve – #51105
  • Twenty Thirteen: Fix missing translations in block patterns, add image credits – #51104

Coding Standards

  • Move assignment out of condition in phpunit/includes/speed-trap-listener.php#52625
  • Further update the code for bulk menu items deletion to better follow WordPress coding standardsWordPress Coding Standards A collection of PHP_CodeSniffer rules (sniffs) to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, especially the official standards for WordPress Core.#21603
  • Apply some minor coding standards fixes – #21603
  • Simplify a condition in wp-admin/admin-footer.php#53306
  • Use strict comparison in wp-includes/class-wp-customize-nav-menus.php#52627
  • Apply some minor coding standards adjustments – #41683, #53156, #53175

Comments

  • Include a “View Post” link on the Comments screen for a single post – #52353

Documentation

  • Improve documentation for get_option(). Clean up, clarify the returned types and the exceptions, and add few
  • Improve documentation for the wp_resource_hints filterFilter 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.#52842
  • Document that has_block() does not check reusable blocks – #53140
  • Improve documentation for wp_list_filter() and wp_filter_object_list()#52808
  • Use a duplicate hook reference for widgets_admin_page in wp-admin/widgets-form-blocks.php#51506

External Libraries

  • Update two polyfill libraries to their latest versions – #52854
  • Update the phpass library to version 0.5#51549

Formatting

  • Add ‘main’ tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) to kses – #53156
  • Introduce the document_title filter – #51643

General

  • Correct the inline code examples for _wp_array_get() and _wp_array_set()#53264
  • Avoid a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher warning when checking the mbstring.func_overload PHP value – #53282
  • Pass the scheme to the *_url filters – #52813

Media

  • Replace basename() usage on media upload screen with wp_basename() for better multibyte filenames support – #51754
  • Add button in media upload page for copying the media url – #51754

Menus

  • Add bulk delete for menu items – #21603

Posts, Post Types

  • Improve post_exists() query – #34012
  • Speed cached get_pages() calls – #51469
  • Remove some unused strings from built-in post type declarations – #53176

Site Health, Privacy

  • Combine shared CSSCSS Cascading Style Sheets. for Site Health & Privacy Settings – #52429

Themes

  • Display the number of available theme updates in the adminadmin (and super admin) menu – #43697

Toolbar

  • Prevent username from wrapping when avatars are disabled – #26933

Upgrade/Install

  • Update sodium_compat to v1.16.1 – #53274

Users

  • Pass on the user data received by wp_insert_user() to related hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.#53110

REST APIREST 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/.

  • Update “object” strings to use the appropriate nouns – #40720
  • Add widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. endpoints – #41683
  • Revert widget endpoints – #41683
  • Add widget endpoints – #41683
  • Add support for modifying the term relation when querying posts – #41287
  • Remove WP_Test_REST_Widgets_Controller tests – #41683
  • Re-introduce WP_Test_REST_Widgets_Controller tests – #41683
  • Remove duplicates in the widget types endpoint – #53305

Widgets

  • Adds the widgets block editor to widgets.php and customize.php – #51506
  • Ignore CSS files in legacy widgets block – #51506
  • Perform ‘widgets_admin_page’ action in block widget editor – #51506
  • Remove unnecessary enqueue of ‘format-library’ assets – #51506

Props

Thanks to the 98 people who contributed to WordPress Core on Trac last week:

@SergeyBiryukov (7), @peterwilsoncc (7), @audrasjb (6), @melchoyce (6), @isabel_brison (5), @TimothyBlynJacobs (5), @onemaggie (4), @desrosj (4), @nosolosw (4), @kjellr (4), @johnbillion (3), @mukesh27 (3), @kevin940726 (3), @noisysocks (3), @youknowriad (2), @ayeshrajans (2), @jnylen0 (2), @gziolo (2), @francina (2), @lukecarbis (2), @talldanwp (2), @spacedmonkey (2), @beafialho (2), @andraganescu (2), @hareesh-pillai (1), @dd32 (1), @tw2113 (1), @joen (1), @ocean90 (1), @hellofromTonya (1), @david.binda (1), @jorgefilipecosta (1), @zieladam (1), @paaggeli (1), @jeremyfelt (1), @dragunoff (1), @timothyblynjacobs (1), @glendaviesnz (1), @otto42 (1), @maxpertici (1), @wphound (1), @paragoninitiativeenterprises (1), @chaion07 (1), @vladytimy (1), @trejder (1), @lephleg (1), @ryelle (1), @oxyrealm (1), @carlomanf (1), @welcher (1), @bernhard-reiter (1), @boniu91 (1), @sabernhardt (1), @5um17 (1), @bhwebworks (1), @paaljoachim (1), @iandunn (1), @jamil95 (1), @joyously (1), @jeffikus (1), @boonebgorges (1), @apokalyptik (1), @ntsekouras (1), @djbu (1), @thomasplevy (1), @akabarikalpesh (1), @ribaricplusplus (1), @jffng (1), @DrewAPicture (1), @poena (1), @vyskoczilova (1), @Rahmohn (1), @vanyukov (1), @imath (1), @azaozz (1), @ReneHermi (1), @brettshumaker (1), @MikeHansenMe (1), @sannevndrmeulen (1), @Mista-Flo (1), @Boniu91 (1), @pixolin (1), @zodiac1978 (1), @joedolson (1), @shaunandrews (1), @claytoncollie (1), @antpb (1), @ryokuhi (1), @whyisjake (1), @anotia (1), @clorith (1), @notlaura (1), @xkon (1), @sebbb (1), @Clorith (1), @earnjam (1), @dlh (1), and @jrf (1).

Congrats and welcome to our 13 new contributors of the week! @dragunoff, @wphound, @trejder, @lephleg, @oxyrealm, @carlomanf, @bhwebworks, @jamil95, @djbu, @brettshumaker, @sannevndrmeulen, @anotia, and @sebbb ♥️

Core committers: @sergeybiryukov (22), @ryelle (8), @desrosj (8), @noisysocks (7), @youknowriad (6), @peterwilsoncc (6), @timothyblynjacobs (2), @joedolson (2), @azaozz (1), @jorgefilipecosta (1), @antpb (1), and @jorbin (1).

#5-8, #week-in-core

Dev Chat Agenda for June 2, 2021

Here is the agenda for this week’s developer meetings to occur at the following times: June 2, 2021 at 5:00 UTC and June 2, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Schedule Review

  • Now in Feature Freeze leading up to BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 in 6 days on Tuesday, June 8th
  • Focus now fully on defects and tasks in the milestone
  • Final Bug Scrub before Beta 1 next week on Monday, June 7th 20:00 UTC
  • RC 1 in 27 days on Tuesday, June 29th
  • 5.8 release in 48 days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items 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.

#5-8, #agenda, #dev-chat

Dev chat summary for May 26, 2021

Happy birthday, WordPress!

Our favorite software is 18 years old today.

And now, devchat.

@peterwilsoncc led the 05:00 devchat, and @jeffpaul led the 20:00 chat. Both used this agenda.

Highlighted blogblog (versus network, site) posts

@audrasjb posted the latest Week In Code, highlighting the work of 120 contributors—11 new folx!—and 11 CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers who landed those changes.

@annezazu published Contextual Patterns for Easier Creation. That’s the idea that the blockBlock 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 should surface patterns based on the block you’re working on right now, to keep you in your flow and make your life easier.

Anne also published the latest FSE Program call for testing. It’s called “Polished Portfolios”, and your feedback is due June 9.

@danfarrow shared a CSSCSS Cascading Style Sheets. Chat summary that featured updates on the color scheming, CSS deprecation and CSS audit projects.

Finally, @paaljoachim and @andraganescu shared Editor chat summaries that highlight monthly priorities on Global Styles, Block-based WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor, Navigation Block, Full Site Editing, Mobile, and the Refactored gallery block.

Please note:  *Navigation Block, Post Author Block, and refactored Gallery Block did NOT make it into WordPress 5.8 before the Feature Freeze*.

Details are here: https://make.wordpress.org/core/2021/05/25/editor-chat-summary-19-may-2021/ && https://make.wordpress.org/core/2021/05/26/core-editor-meeting-notes-26-may-2021/.

After this extensive list, @chanthaboune commented, “Gosh, but we are prolific writers here …” and added, “… I love it”.

The group reacted with a flurry of positive emojis.

Posts that need feedback

Are you a host? @javiercasares and the Hosting team recommend you offer the `PHP-intl` extension by default to all of your users.

The Tide team would like some help testing their refactor to Node.js on a local installLocal Install A local install of WordPress is a way to create a staging environment by installing a LAMP or LEMP stack on your local computer.. Specifically, where do their docs seem unclear? Where are they confusing? Please offer your help in their chat summary.

@chanthaboune shares that she’s ready to experiment with a public channel for Team Reps across the project to collaborate in public. She’d like your feedback in the comments through the end of the week.

Upcoming releases: WordPress 5.8

@jeffpaul reminded the group that 5.8 is in Feature Freeze, as of Monday, May 24. That means the work now shifts to fixing bugs, finding defects and finishing tasks. To that end, @boniu91 and @lukecarbishave scheduled a Test Scrub on Friday, May 28, and two 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. scrubs on Monday.

(Ed. note: No word on how the scrubs will affect mosquito activity in the US over the holiday weekend, which traditionally involves eating meals outdoors. 😜 )

The next milestone is BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1, on Tuesday, June 8. At that point the work shifts again: to testing every change that made it in, and to fixing the bugs that come out of that testing.

(Ed. note: Most betas, release candidates and launches happen on Tuesdays, in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., and you’re invited to join the group that gathers there and helps test the brand-new software packages. You don’t need any special skills, and it’s a great way to start contributing. So mark your calendar for every Tuesday between June 8 and final release in July!)

After that announcement of the impending milestones, @jeffpaul asked for calls for help.

@chanthaboune brought up ticketticket Created for both bug reports and feature development on the bug tracker. #31935 as a high priority, and @clorith surfaced #30910 which also needs a push.

@francina said she’s changed #51809 to future-release from the current milestone, because it needs to start with a lot of discovery. Component maintainer @marybaum (disclosure: your faithful reporter) suggested a more specific discussion, around starting with a message strategy, when interested parties have the time.

Components check-in

@sergeybiryukov reported on Comments and Themes.

The Comments screen for a single post has acquired a link to View Post, per #52353. And in Themes, in the Adminadmin (and super admin) menu next to the Themes item, there’s an update button with the number of updates — just as there has long been for Plugins — per #43697.

He reported no major news on the other components he helps maintain.

@clorith reported on Site Health: it has a good first bug up for grabs in #52642, if you’d like to jumpstart your code contributions. He says he’s available to help show you how to make a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing..

@audrasjb had no major news on Widgets (Classic) or Upgrade/Install, but announced that #21603 made it in before Feature Freeze. He gave props to @maxpertici and @joedolson.

Open floor

@chanthaboune, on the 18th birthday of WordPress:

Tomorrow is WordPress’ 18th birthday :tada: and a post will go up on /news tomorrow with a little celebration page. also, props to the polyglots who have been working on that page this week.

@marybaum noted she’d been looking for 3D-content plugins in the PluginPlugin 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 Directory. It was no surprise to her that the best one (for her) has a familiar author: @sergeybiryukov!

#5-8, #dev-chat, #summary