Jb Audras 8:09 am on June 5, 2021
Tags: , ,   

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

Héctor Prieto 9:27 pm on June 4, 2021
Tags: , ,   

What’s next in Gutenberg? (June 2021)

This monthly status update contains the high-level items that 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/ contributors are focusing on for June. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.

How to follow along with Gutenberg:

Here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project. There is also an index page of Gutenberg development-related posts and a Site Editing Milestone overview issue that breaks down the upcoming work into more concrete next steps.

WordPress 5.8 focuses

With WordPress 5.8 Beta 1 planned for June 8, the priorities for the month heavily focus on stabilizing, testing, 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. fixing, and documenting the features recently merged in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., which can be followed in the WordPress 5.8 project board. However, design and development in other Gutenberg areas continue as well, and contributions are welcome!

The remaining tasks for 5.8 include:

Widgets Editor

Work on the block-based Widgets Editor is a continued focus. The main efforts target stabilizing and documenting the editor and the customizerCustomizer 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. block editor, as well as deciding whether the Widgets Editor should be enabled by default.

If you want to help us test the block-based Widgets Editor, drop by the Widgets Editor Call for Testing and report on your experience!

Follow along:

You can find more information about the current work in progress in this tracking issue, as well as on this project board. Moreover, you can join #feature-widgets-block-editor in WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ 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/. for future 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-focused meetings.

Navigation Editor

Like the Widgets Editor, the Navigation Editor aims to help expand what’s possible with menus while bringing block functionality to yet another part of WordPress and offer a more modern experience. Current efforts include:

Follow along:

You can follow the progress of this project on this project board or review the new Navigation Editor tracking issue and join #feature-navigation-block-editor in WordPress.org Slack.

Full Site Editing

Work on this major focus for phase 2 is ongoing and is expected to continue as a big-picture goal for 2021. Apart from all the features making it into 5.8, this is the status of the different FSE areas and their upcoming work:

Milestone 1 – Site Editing Infrastructure and UI

  • As the Template Editing Mode is landing in 5.8, efforts focus on testing and stabilizing this feature. If you would like to help, check the current FSE Outreach Program round focused on Template Editing Mode!

Milestone 3 – Global Styles

  • The first version of Global Styles has been merged in core, and focuses need to be revisited. Any relevant update will be posted in this GitHub issue on demand.

Milestone 4 – Theme Blocks

Milestone 5 – Query Block

  • With great power comes great responsibility; because the Query Block is so powerful, contributors are making sure it lands in the best status possible in 5.8 as mentioned in the “WordPress 5.8 focuses” section above.

Further work on the Query block not limited to 5.8 includes:

Milestone 6 – Navigation Block

Follow along:

You can follow the progress of this project with this overview issue showing key milestones for site editing. For each major milestone, there are related issues you can follow if you want a more granular look at each next step.

If you’re interested in testing Full Site Editing, check out the FSE Outreach Program to learn more. If you have questions about Full Site Editing, check out this recent effort to offer answers.

Areas to be aware of

WCEU 2021

WordCamp Europe 2021 is scheduled for 7 to 9 June 2021 as an online event and will include several sessions related to Gutenberg, such as:

  • Full Site Editing (Discussion Panel)
  • A walkthrough of Full Site Editing (Workshop)
  • The Future of Themes in WordPress (Discussion Panel)
  • Blazing fast block development (Talk)

Make sure to register if you haven’t already!

Theme Developers

Calls for testing

Block Patterns

Ways to Get Involved

While the above items are our focuses, don’t forget that you can always help with triage, testing issues, good first issues, and reviewing PRs. In particular, if you’re interested in helping with triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. but don’t know where to start, there’s a course on Learn WordPress for how to do triage in GitHub! Check it out and join us.

If there’s anything we can do to make contributing easier, let us know in the comments or in #core-editor chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers.

Meetings to join:

While you can view all meetings here, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate:

  • Core Editor weekly Wednesdays @ 14:00 UTC in #core-editor focused on all things Gutenberg.
  • Block Themes meeting twice monthly on Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.

Thanks @andreamiddleton and @cbringmann for reviewing this post.

#core-editor #gutenberg-next #gutenberg

Dan Farrow 9:05 am on June 4, 2021
Tags: ,   

CSS Chat Summary: 03 June 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

  • @danfarrow offered to run the next 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. scrub (01 July @ 20:00UTC) – thanks me!

Project updates

Color Scheming (#49999)

HSL works but it would force us to have an APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. based on HSL colors, we want to have a more generic API where users just define a single variable.

CSSCSS Cascading Style Sheets. Audit (#49582)

  • @danfarrow reported having made progress on the 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/ actions to autogenerate the report. There are now two actions, one to merge updates to trunk into the report branch (which appears to be working), and the Build Report action which now generates the report once a day from the report 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".. TBC if it now works as expected…
  • @colorful-tones offered to add a link to the CSS Audit report into the CSS Coding Standards docs [UPDATE] Now done, thanks @colorful-tones!

CSS deprecation path (#53070)

  • The next step is a Make post from @tellthemachines, probably on hold until after the upcoming 5.8 release

Open floor / CSS link share

Thanks everyone!

#core-css, #summary

Francesca Marano 9:01 pm on June 3, 2021
Tags: make.wordpress.org/project,   

X-post: Welcome to make.wordpress.org/project

X-comment from +make.wordpress.org/project: Comment on Welcome to make.wordpress.org/project

Lara Schenck 7:34 pm on June 3, 2021
Tags: ,   

CSS Chat Agenda: June 3, 2021

Note: 1 hour before the meeting this week, @sabernhardt will lead a CSSCSS Cascading Style Sheets. 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. scrub looking at 5.8 tickets.

This is the agenda for the upcoming CSS meeting scheduled for Thursday, June 3, at 5:00 PM EDT. This meeting will be held in the #core-css channel in the Making WordPress 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • Housekeeping
  • Project Updates
    • Color Scheming (#49999)
    • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS deprecation path (#53070)
    • CSS Audit (#49582)
  • Open Floor + CSS Link Share

#agenda, #core-css

#agenda, #core-css

annezazu 2:42 pm on June 3, 2021  

Editor chat summary: 2 June, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on 2021-06-2 14:00 UTC in Slack. Moderated by @annezazu.

Announcements

WordPress 5.8 project board update

The link to the Project Board can be found here. @youknowriad shared both that progress is continuing with the number of issues going down and that there are a number of important 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. to write. He asked for ideas around how best to coordinate this work. @mkaz chimed in to share that he added the Dev Notes to a tracking spreadsheet for the docs team and that he can help wrangle people for this work. Both @annezazu and @daisyo raised their hands to help with this effort.

In terms of next steps, triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. needs to be done before confirming what needs docs and creating individual tickets to then 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.” volunteers about.

Monthly Priorities & Key Project Updates

The June edition of the “What’s Next” post hasn’t been shipped yet but efforts are clearly planned to focus around 5.8. Outside of that, folks still shared some updates in line with last month’s priorities:

Full Site Editing

@youknowriad shared two things on his mind that likely need some help:

  • An interesting proposal to change a bit how we tie templates to themes.
  • Potential iterations on 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. to add a bit of friction to editing posts.

Navigation Block

@mkaz shared that the Navigation block is stalling a little with a big next step revolving around a larger decision around the markup. A few minor updates for design and performance improvements over the last week.

Mobile

@hypest shared the following:

  • Shipped the Inserter tooltip + Audio block fixes
  • In Progress: Editor onboarding, Block picker search, Embeds block 
  • ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native 0.64.x upgrade around the corner, including upgrade to React v17!

Block Based Widgets Editor

After the meeting, @andraganescu shared that the focus is currently on shipping as many 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 as possible!

Task Coordination

@youknowriad

  • Update packages on trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.
  • Reviewing PRs that are targeted for 5.8
  • Small fixes (Patterns, Template Mode)
  • Coordination work

@joen

  • Landed a navigation block refactor to enable global-styles-controlled padding and more theme control.
  • Keeping an eye out for any followups on that, as well as on the hamburger menu.
  • My focus remains on enabling patterns (which means also refining social links and search). At the moment that means exploring what it means for the setup state to enable a crazy pattern like this one.
  • List view as a user experience improvement is also on my radar.

@annezazu

  • Solely focused on FSE Outreach Program work mainly in the form of triaging feedback, sharing summaries, and coordinating with others. I have some time off this week/next so trying to stay as focused as possible.
  • There is a proposal around having profile badges as part of the program which would be great to get more thoughts on.

@toro_unit

@aristath

  • This past week mostly 5.8-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/ tasks and lots of PR reviews to move things forward.
  • Highlights: backporting the site-logo block to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. & landed a PR to allow using non-latin characters in slugs 

@daisyo

  • Running a three hour workshop on creating block themes tomorrow for WordSesh.

Open Floor

Can someone take a look at a PR to make templates more extendable? From @janwoostendorp.

Last week, the same PR was shared and it was suggested to add a use case to make it clearer what the PR is attempting to accomplish. This week, @janwoostendorp was hoping to get a review of the same PR now that the use case has been elaborated upon. @youknowriad chimed in say that the use case seems legit and the proposed solution for it seems sane. However, he was concerned about introducing filters that are low level at this stage in development.

Next Step: @youknowriad pinged folks on the PR who have experience with backend filters to give a more informed opinion and perhaps move this forward.

Is anyone willing to take on leading the 10.8 RC release today? From @youknowriad.

To help ease concerns a few folks had, Riad shared a link to the release wrangling documentation. For anyone interested, check it out and know this is a highly valued way to contribute back to WordPress!

Next step: Sandip Mondal volunteered after the meeting was over and will help with the stable release next week while other folks took care of the RC due to timezones.

Jb Audras 10:34 pm on June 1, 2021
Tags: ,   

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

Francesca Marano 7:49 pm on June 1, 2021
Tags: , ,   

Upgrade/Install component meeting notes from June 1st, 2021

On Tuesday June 1, I did a scrub in the #core-auto-updates 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/. channel about tickets related to Outcome 1 of the Updaters initiative, “Make sure the zips upload and unpacking are safe”. You can read the monologue on Slack 🙂

  • #35217, #36373 – Closed since they contradict the best practices laid out in the plugin handbook.
  • #33571 – Asked for more information to confirm that the issue persists
  • #34676 – I will test it and if it needs a refresh I will leave a comment on it
  • #38084 – Pinged @desrosj for review since there is 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. uploaded
  • #44118 – Patch has been refreshed by @pbiron recently, added needs-testing keyword
  • #50849 – Pinged @desrosj and @hellofromtonya for a status update.
  • #51823 – Asked the reporter if more information can be provided since the issue can not be reproduced

See you next week!

#core-auto-updates, #updater, #upgrade-install

Jeffrey Paul 5:04 pm on June 1, 2021
Tags: , ,   

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

Paal Joachim Romdahl 3:29 pm on June 1, 2021
Tags: , , ,   

Editor Chat Agenda: 2 June 2021

Facilitator and notetaker: @annezazu

This is the agenda for the weekly editor chat scheduled for Wednesday, June 2, 2021, 04:00 PM GMT+1.

This meeting is held in the #core-editor channel in the Making WordPress 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/..

  • Gutenberg 10.7 final release for WordPress 5.8.
  • WordPress 5.8 project board
  • Help Test the Widgets Editor for WordPress 5.8
  • Monthly Plan for May 2021 and key project updates:
    • Global Styles.
    • 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. 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
  • Task Coordination.
  • Open Floor.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meetings