Bug Scrub Schedule for 6.2

With 6.2 well underway, it’s time to schedule the 6.2 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 sessions. These 6.2 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Bug Scrubs

Hosted by @costdev

Hosted by @mukesh27 (APAC-Friendly)

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. Bug Scrubs
Focus: issues reported from the previous beta.

Hosted by @costdev

Hosted by @mukesh27 (APAC-friendly)

Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). Bug Scrubs (if needed)
Focus: issues reported from the previous RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta)..

Hosted by @costdev

Hosted by @mukesh27 (APAC-Friendly)

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

For your reference, here are some of the recurring sessions:

Have a recurring component scrub or triage session?
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.” @costdev or @mukesh27 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/. to have it added to this page.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at any time? Yes, you can!

How? Ping @costdev or @mukesh27 on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 6.2-focused? Awesome! It can be added it to the schedule here. You’ll get well deserved props in Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 6.2 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 6.2 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @costdev or @mukesh27 on Slack.

Props to @hellofromtonya for reviewing the post.

#6-2, #bug-scrub, #core

X-post: Apply to Attend the 2023 Community Summit

X-comment from +make.wordpress.org/community: Comment on Apply to Attend the 2023 Community Summit

Developer Hours is returning

After a successful trial, a new series of events, entitled “Developer Hours” will be available. These sessions are free to join and participate in. They will take place on Zoom video-conferencing, and will variously consist of discussion sessions and question and answer sessions aimed at developers working with WordPress.


It’s said that “no-one is an island”, and that is as true for developers as it is for anyone. While documentation and tutorials can take you so far, sometimes there’s just no substitute for talking to other developers who are facing the same struggles as you, or getting advice from those who are more experienced than you and who are able to help you overcome your problems – or at the very least point you in the right direction.

The pilot

In early 2022 a set of four trial events was scheduled to provide developers with a forum for such interactions. These events were held under the moniker “Developer Hours”.

These initial events proved to be enormously successful. Links to the videos from these trial events can be found at the bottom of this post. Given this success the decision has been taken to iterate on this trial in 2023 and make Developer Hours a fixture in the calendar for WordPress developers.

Developer Hours will henceforth be held regularly. They are discussion and question and answer events aimed at developers working with WordPress. Anyone is welcome to attend, whether you are a freelancer or work in an agency, and whether your special area of interest is coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. or themes or plugins, or indeed any combination thereof. 

The initial four trial events were purposely unstructured, although attendees were able to send questions in advance so the panelists could prepare meaningful answers. The facilitators and moderators could structure the session on the fly, thereby lending each event an air of spontaneity. 

Feedback provided by attendees and panelists at those initial sessions resulted in the following insight. Rather than the sessions being open-ended and having a broad range of questions covering a variety of development topics, each scheduled Developer Hours session should instead center around a particular topic or theme. This will ensure that each session has a clear focus, it will set expectations, and it will help ensure both that the event is well structured and that it provides value for each of the participants involved. 

Future events

The newly re-launched Developer Hours events will provide you with the opportunity to connect with other WordPress developers, to have a platform to air your concerns or relate your experiences, and to ask a panel of peers and experts about best approaches, tooling, coding and implementation problems, and a variety of other topics related to WordPress development. There’s sure to be someone in each session who can help you or who can address any concerns you may raise.

If you’re starting out and seeking help and advice, an experienced developer who is willing to share their knowledge and expertise to help others, or if you just want to voice your thoughts and opinions to anyone willing to listen, or even vent your frustrations, then Developer hours are for you.

The first three Developer Hours have already been scheduled. The focus for these will be 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 development and they will have a special emphasis on migrating a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher based plugin, e.g. migrating one that renders content using a shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. or 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. to blocks. So, if you are a plugin developer who is planning, or has already tried, to modify your plugin to also implement a 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., then one of these sessions is for you. 

The following events have been scheduled and are available for you to sign-up: 

DateTimeEventHosts
Mon, February, 6, 202314:00 UTCDeveloper Hours: Migrate a plugin to blocks
(EMEA)
Michael Burridge
Ryan Welcher
Mon, February 27, 202317:00 UTCDeveloper Hours: Migrate a plugin to blocks
(Americas)
Justin Tadlock
Ryan Welcher
Mon, March 27, 202308:00 UTCDeveloper Hours: Migrate a plugin to blocks
(EMEA / Asia-Pacific)
Jonathan Bossenger
Michael Burridge

These sessions will be held on Zoom and each has been scheduled for different times to cover as many timezones as possible. Click the link for the event scheduled for your region and RSVP on Meetup to join the event. You will see the correct time adjusted for your timezone in MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area.. We look forward to seeing you there.

If your interests lie elsewhere then keep a lookout for more upcoming events covering different topics. These are sure to be scheduled soon. 

Get involved

Do you have a particular topic that you want to see discussed? Please suggest it in the comments below or head over to the #core-editor channel in 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/. and suggest it there. If you’re willing to host a Developer Hours session, new volunteers are very welcome.


Please note that all Developer Hours events will be recorded and the recording will be uploaded to WordPress.tv and to YouTube. Participation in a Developer Hours event implies agreement to, and acceptance of, this – though remember that there are no “stupid questions” and no-one is expected to know everything. We are all learning all the time. The hope is that these recordings will be a useful and valuable learning resource for developers working with WordPress who were not able to attend.


Project background and recordings from 2022


Props to: @mburridge, @juanmaguitar, @bph, @webcommsat, @hellofromtonya for contributions to this post.

#developer-hours

Dev Chat agenda, February 8, 2023

The WordPress Developers Chat meeting will take place on February 8, 2023 at 20:00 UTC in the core channel of the Make WordPress Slack.

Welcome and housekeeping notices

Summary from last week’s meeting, February 1, 2023@webcommsat

Announcements

WordPress 6.2 Beta 1 is out and available for testing – released February 7, 2023

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/ 15.1 release expected.

Highlighted posts

A Week in Core@audrasjb. In this week, 22 new contributors were recorded!

Proposal for automated performance monitoring in WordPress Core@adamsilverstein

Developer Hours returns@mburridge

Roadmap to 6.2@annezazu

Releases update

a) 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.: 6.2
6.2 development cycle
6.2 bug scrub schedule

Updates from the release squad.

Release coordinators @francina will not be available between February 9 and February 21, and @priethor has limited availability during WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia. Francesca will be available to run the Dev Chat meeting and release parties after February 21. Below are dates needing cover for facilitators of the live meetings:

  • 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. 2, February 14
  • Dev Chat, February 15
  • Beta 3, February 21
  • Potentially, Dev Chat, February 22

If release squad members can cover, please reply in this Slack thread.

Requests for help/ any blockers relating to components or tickets

The priority will be given to items relating to 6.2. Please add to comments any tickets or blockers.

Open floor

Please add your requests for items in the comments below. The below updates have been received so far.

#agenda, #dev-chat

Performance Chat Summary: 7 February 2023

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Reminder: Performance team roadmap for 2023 https://github.com/WordPress/performance/issues/631 If you’re actively contributing to the WordPress Performance Team or plan to do so this year, please share your priorities for 2023 as a comment on this issue before end of day Wednesday February 15, 2023
  • Team rep nomination reminder, please add your nominations for Performance Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. by Friday, February 24 2023

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Measurement

N/A

GitHub project

  • @joegrainger making good progress on 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 Checker. We’re starting to finalise the infrastructure and should have a working plugin running some initial checks by end of the month. You can track progress on the GitHub repo and leave any thoughts/ideas you may have. The repo will be moved to the WordPress organisation when ready
  • @mukesh27 I would like to share an update for Automated Performance Testing that @adamsilverstein already share blog post on WordPress core.
    • Issues that completed and merged in feature/automated-performance-testing-mvp 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"..
    • AC ready for review.
    • We will open a PR against the WordPress 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. once the initial version is complete. Feel free to take a look at the issues and leave any thoughts or ideas you may have.
  • @joemcgill Additionally, I’ve been starting to work on an experimental implementation of XHProf with wp-env to help make it easier for folks to do general performance profiling tasks. See: https://github.com/joemcgill/gutenberg/pull/1 as a starting point.
  • @10upsimon updates on Enhancing the Scripts 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. with a loading strategy
    • Documentation approved, although there was a comment added post approval that I have addressed. It does not change the work, but it does result in the need to confirm that the blocking strategy is not to be confused with the blocking  script attribute itself.
    • GitHub issues have been finalized and broken down into 4x milestones in a separate sheet, estimates are present for all issues in the sheet, although not all issues are in GH yet.
    • GH Issues and AC’s have been added to the project board for Milestones 1, 2 and 3 and have been assigned to @joemcgill for review. It looks like all except for one have been approved (at the time of writing) as they’ve been moved to the backlog
    • I’m in the process of breaking down issues for Milestone 4
    • TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. to be posted by Friday, I see no risks thereto.
    • Engineering will commence next week on Milestones 1, 2 and 3

Feedback requested

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

@aristath @sergiomdgomes

GitHub project

  • No updates

Feedback requested

Database

@olliejones

GitHub project

  • @olliejones I’ve been hammering on the low end persistent object cache, looks good.
  • @aristath These past couple of weeks I continued working on the SQLite database implementation. There’s a lot of work to do, but things are looking good. Started collaborating with @zieladam as well in an effort to improve some things and make the implementation more stable.

Feedback requested

Infrastructure

@flixos90

GitHub project

Feedback requested

Open Floor

  • @flixos90 Just sharing here that I discovered (probably?) a major performance regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in 6.2 for classic themes: https://core.trac.wordpress.org/ticket/57648
    • I’m going to follow up on that ticket shortly to collaborate with @oandregal as he is seeing slightly different results. Of course there is a chance that something specifically in my analysis went wrong, but we will have to validate that data

Our next chat will be held on Tuesday, February 14, 2023 at 16:00 UTC in the #core-performance channel in Slack.

#core-js, #core-media, #performance, #performance-chat, #summary, #hosting-community

#core-performance, #meta

A Week in Core – February 6, 2023

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 January 30 and February 6, 2023.

  • 86 commits
  • 137 contributors
  • 66 tickets created
  • 14 tickets reopened
  • 91 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

Build/Test Tools

  • Add unit tests for wp_set_password hook – #57436
  • Update json2php package – #57535
  • Update npm dependencies – #57535
  • Update npm dependencies for bundled themes – #57535

Bundled Themes

  • Twenty Fourteen: Correctly reflect text color changes in Pullquote 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.#56006
  • Twenty Sixteen: Fix Gallery block images alignement – #56412
  • Twenty Twenty-Two: Improve spacing for the legacy Post Comments block – #57560

Code Modernization

  • Allow some parameters with reserved keywords in wp-includes/class-wp-text-diff-renderer-*.php#56788
  • Rename parameters that use reserved keywords in wp-includes/formatting.php#56788
  • Fix a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 deprecation warning in category-template.php uasort() helper – #57358, #56790

Coding Standards

  • Add missing escaping function in Custom_Image_Header::show_header_selector()#57638
  • Rename the $cat_ID variable to $cat_id in wp_update_category()#56754

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

  • Improve the docs for some cron event and cron schedule related functions – #56792

Docs

  • Capitalize X-Pingback in discover_pingback_server_uri() DocBlockdocblock (phpdoc, xref, inline docs)#54225
  • Document directory support in FTP/SSH2 filesystem ::move() methods – #57604
  • Document the inserter property in WP_Block_Patterns_Registry::register()#56792
  • Fix couple of typos in inline docsinline docs (phpdoc, docblock, xref)#57575
  • Fix typo in the send_auth_cookies 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. DocBlock – #56971, #39367
  • Improve documentation for block pattern properties – #56792
  • Improve the DocBlock for get_attached_file()#51780, #56792
  • Remove a duplicate line in the send_auth_cookies filter DocBlock – #56971, #39367
  • Use consistent format for the @return tags in _wp_object_name_sort_cb() and _wp_object_count_sort_cb()#57358, #56792

Editor

  • Add ID support to block wrapper attributes – #56852
  • Update WP_Theme_JSON_Resolver and improve its performance – #57545
  • Add ‘wp-polyfill’ to _wp_get_iframed_editor_assets() for inert attribute in Firefox – #57552
  • Add Template types to the patterns API
  • Add missing WP_Theme_JSON::process_blocks_custom_css() method – #57621
  • Add missing controls to flex layouts in wp_get_layout_style()#57602
  • Add support for custom CSSCSS Cascading Style Sheets. in global styles – #57536
  • Add support for editing block style variations in global styles – #57583
  • 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. site editor intialization changes from 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/ 15.1 – #57480
  • Improve performance of gutenberg_render_layout_support_flag
  • Introduce minimum height dimensions block support – #57582
  • Remove need for template prefix in get_template_hierarchy – #57614
  • Remove unnecessary CSS comments from compiled styles – #56388
  • Separate content styles for iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. in __wp_get_iframed_editor_assets() and wp_default_styles() – #57550
  • Support the block_types and viewport_width props for remote patterns fetched from Pattern Directory – #57611
  • Updated the WordPress packages to include Gutenberg 15.1.0 changes – #57471
  • Use WP_HTML_Tag_Processor in wp_render_elements_support()#57642
  • Use a non-persistent object cache instead of transient in wp_get_global_stylesheet()#57568
  • Introduce HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API with HTML Tag Processor – #57575

Embeds

  • Add oEmbed support for crowdsignal.net surveys – #57543
  • Update YouTube provider for live URLs – #57632
  • Use documented mixcloud.com oembed endpoint – #57376

Emoji

  • Always skip nodes with the wp-exclude-emoji CSS class – #52219
  • Fix emoji feature detection – #57301

External Libraries

  • Update jQuery Migrate to version 3.4.0 – #56743

Filesystem API

  • Add directory support to WP_Filesystem_Direct::move()#57375
  • Add test for uncovered WP_Error in move_dir()#57375
  • Prevent fatal error in move_dir()#57375
  • Simplify two conditionals in move_dir()#57375
  • Update move_dir() to better handle the differences in the WP_Filesystem::move() methods – #57375

Formatting

  • Guard wp_strip_all_tags() against fatal errors – #56434

HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. API

  • Fix a unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. failure found after [55210]#54225
  • Fix request 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. inconsistencies – #54225
  • Restore one instance of the X-Pingback header capitalization – #54225

Help/About

  • Update help tab texts to consistently describe button labels – #57608

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.

  • Improve method names in WP_Locale_Switcher()#57123
  • I18N: Pass $locale parameter to override_load_textdomain filter – #57056

KSES

  • Allow position-related CSS properties – #57504

Media

  • Add a Download row action to the Media List Table – #57574
  • Add argument to get_attached_file() for subsizes – #51780
  • Allow to omit decoding="async" on tags from wp_get_attachment_image()#57086
  • Ensure media IDs are type int in bulk editing – #56170
  • Fix inconsistent font weight in media detail views – #54509
  • Fix upload not visible if added after deleting media – #49178
  • Hide ‘view’ link if empty string passed to attachment_link – #54824
  • Maintain the functionnality of the deprecated WP_Media_List_Table::column_desc() method – #39710
  • Pass $size argument to get_attached_file filter – #51780
  • Properly escape Download row action link in Media List Table – #57574
  • Remove 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. data after restoring w/IMAGE_EDIT_OVERWRITE – #55150
  • Remove unwanted quotation marks for playlist template – #50865
  • Replace consecutive periods in sanitize_file_name()#57242

Plugins

  • Rephrase Add Plugins screen description for better clarity – #57155

Posts, Post Types

  • Add test coverage for _truncate_post_slug()#56868, #56793
  • Deprecate get_page_by_title() in favour of WP_Query#57041

Query

  • Add a search_columns argument to control which fields are searched in a search query – #43867
  • Revert [55169]#56689
  • Use WP_Query in get_page_by_path#56689

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

  • Declare ‘edit_css’ capability in links within WP_REST_Global_Styles_Controller#57526

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.

  • Add a way to filter the revisions considered for deletion – #57320

TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.

  • Implement wp_cache_get_multiple in wp_queue_posts_for_term_meta_lazyload#57150

Themes

  • Add caching to WP_Theme::is_block_theme()#57114
  • Add shadow presets support for theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.#57559
  • Increase HTTP timeout for Theme API requests – #57315

Upgrade/Install

  • Send language pack updates to copy_dir()#57557
  • Silence Requests deprecations before preloading – #54504
  • Use move_dir() instead of copy_dir() in WP_Upgrader::install_package() when possible – #57557

Users

  • Add context to the send_auth_cookies filter – #56971, #39367
  • Add support for RoboHash GravatarGravatar Is an acronym for Globally Recognized Avatar. It is the avatar system managed by WordPress.com, and used within the WordPress software. https://gravatar.com/. images in default user profile pics – #57493
  • Change parameters order in send_auth_cookies filter – #56971
  • Update get_avatar_url() and get_avatar() to include RoboHash support – #57493

Widgets

  • Preserve classic sidebars when switching to a block theme – #57531

Props

Thanks to the 137 (!) people who contributed to WordPress Core on Trac last week: @costdev (36), @mukesh27 (22), @audrasjb (20), @sergeybiryukov (15), @peterwilsoncc (13), @flixos90 (13), @ntsekouras (9), @afragen (7), @spacedmonkey (7), @mamaduka (7), @oandregal (6), @hellofromtonya (6), @azaozz (6), @adamsilverstein (5), @desrosj (5), @joedolson (5), @robinwpdeveloper (5), @andrewserong (5), @aristath (5), @youknowriad (5), @swissspidy (4), @dd32 (4), @jrf (4), @ironprogrammer (4), @sabernhardt (4), @poena (4), @hellofromTonya (4), @scruffian (3), @joen (3), @ocean90 (3), @Mista-Flo (3), @Mamaduka (3), @joemcgill (3), @isabel_brison (3), @pbiron (3), @aaronrobertshaw (3), @bgoewert (2), @glendaviesnz (2), @jorgefilipecosta (2), @davidbaumwald (2), @kebbet (2), @felixarntz (2), @gziolo (2), @onemaggie (2), @jameskoster (2), @petitphp (2), @noisysocks (2), @johnjamesjacoby (2), @dmsnell (2), @matveb (1), @ryokuhi (1), @paulschreiber (1), @cadic (1), @ndiego (1), @naeemhaque (1), @amin7 (1), @tahmidulkarim (1), @krupalpanchal (1), @jhned (1), @hilayt24 (1), @ellatrix (1), @tellthemachines (1), @maximej (1), @ramonopoly (1), @paaljoachim (1), @madhudollu (1), @timothyblynjacobs (1), @talldanwp (1), @mmtr86 (1), @dsas (1), @antpb (1), @zebaafiashama (1), @rnitinb (1), @iapial (1), @viralsampat (1), @jeawhanlee (1), @mitogh (1), @wildworks (1), @donncha (1), @cbirdsong (1), @eherman24 (1), @ajlende (1), @szaqal21 (1), @ahortin (1), @miguelaxcar (1), @patelhitesh (1), @tanazmasaba (1), @revgeorge (1), @Webrocker (1), @soean (1), @matclayton (1), @Soean (1), @mahbubshovan (1), @adeltahri (1), @stalukder03 (1), @a4jpcom (1), @juliobox (1), @chintan1896 (1), @sergiomdgomes (1), @slieschke (1), @jeherve (1), @ruchirj (1), @chocofc1 (1), @birgire (1), @johnbillion (1), @abidhasan112 (1), @arrasel403 (1), @james-roberts (1), @Presskopp (1), @hvar (1), @10upsimon (1), @umesh84 (1), @amitbarai013 (1), @dlh (1), @arthurshlain (1), @andraganescu (1), @justlevine (1), @get_dave (1), @zieladam (1), @bernhard-reiter (1), @antonvlasenko (1), @bronsonquick (1), @TimothyBlynJacobs (1), @xknown (1), @ArtZ91 (1), @shamayel007 (1), @mhkuu (1), @jigar-bhanushali (1), @otto42 (1), @iandunn (1), @iqbalrony (1), @oh_hello (1), @tahminar27 (1), @ira2910 (1), @zoonini (1), @silicium23 (1), and @justinahinon (1).

Congrats and welcome to our 21 (!!) new contributors of the week: @zebaafiashama, @rnitinb, @iapial, @patelhitesh, @tanazmasaba, @mahbubshovan, @adeltahri, @stalukder03, @slieschke, @ruchirj, @chocofc1, @abidhasan112, @james-roberts, @amitbarai013, @ArtZ91, @shamayel007, @iqbalrony, @oh_hello, @tahminar27, @ira2910, @silicium23 ♥️

Core committers: @audrasjb (24), @sergeybiryukov (13), @flixos90 (9), @hellofromtonya (9), @peterwilsoncc (7), @azaozz (7), @joedolson (7), @jorgefilipecosta (5), @spacedmonkey (3), @desrosj (3), @youknowriad (2), @swissspidy (1), and @johnbillion (1).

#6-2, #core, #meta6545, #week-in-core

Performance Chat Agenda: 7 February 2023

Here is the agenda for this week’s performance team meeting scheduled for February 7, 2023 at 16:00 UTC.

  • Announcements
    • Reminder: Performance team roadmap for 2023 https://github.com/WordPress/performance/issues/631 If you’re actively contributing to the WordPress Performance Team or plan to do so this year, please share your priorities for 2023 as a comment on this issue before end of day Wednesday February 15, 2023
    • Team rep nomination reminder, please add your nominations for Performance Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. by Friday, February 24 2023
  • Focus area updates
  • Infrastructure
  • Open floor

    This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

    #agenda, #meeting, #performance, #performance-chat

    Roadmap to 6.2

    WordPress 6.2 is set to be released on March 28th with an exciting list of features to look forward to. The main focus of this release is refinement and ease, with significant improvements in the site editing experience. This includes a revamped approach to navigating between templates and template parts, an additional way to manage menus with the 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., and the ability to import widgets to block themes. As always, the base block experience is also improved with various features like a new distraction free writing mode and a scaled block settings experience. 

    The result is the start of wrapping on Phase 2 of the Gutenberg roadmap, marked in part by the planned removal of the beta label from the Site Editor. With a strong foundation with this release, sights will be set on breaking ground on Phase 3 more concretely alongside continual improvements for the now broadened site experience. 

    What follows are the key sections of work, including items from the broader CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. side of work. 

    Elevating the block editing experience

    The Site Editor experience has been transformed into one that centers the entire structure of your site starting with your homepage. Rather than being dropped into a single template, various features come together to both ease navigating across your site and add necessary friction to take the actions you want. Alongside this broader shift, you can: 

    • Use a reimagined Site Editor experience with Browse mode (36667). 
    • See template parts and reusable blocks at a glance with added colorization (32163).
    • Write without distraction with a new editing mode designed to do just that (41740). 
    • Add Media from your Media Library directly from the Inserter (44918). 
    • Pull images in from Openverse in the Inserter with the option to disable (46222). 
    • Note an updated Block Settings icon that paves the way for future changes (46851). 
    • Migrate widgets to block themes (39270).
    • Access the list view and document information all from one panel (44788).

    Video of distraction free mode:

    Video showing an early look at the reimagined site editor experience:

    Refining and expanding block capabilities

    Individual blocks, particularly the Navigation block, continue to expand in capabilities and experience while the overall block settings have been iterated upon with more complex blocks in mind with a split between Styles and Settings tabs. 

    • Enjoy an additional way to edit the Navigation block with a new list view baked into the block settings sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.
    • Restrict the ability to edit the content on the Navigation block’s inner blocks (links and submenus) to further curate the experience (44739).
    • Rely on various fallbacks for the Navigation block out of the box (45976) (46286).
    • Customize blocks with a new split Styles and Settings to better scale with the growing set of design tools (40204).
    • Use the new “Sticky” block position option in the inspector to ensure a block at the root level remains on screen regardless of where someone scrolls (46142).
    • Set the width of blocks within a Row block (44467).
    • Choose a row or stacked layout right from the Group block setup state (43433). 
    • Surface aspect-ratio tool for custom image dimensions (38990). 
    • Add/remove captions for various blocks (Audio, Video, Image) directly from the block toolbar.  
    Three images of the split settings as part of the navigation block on an orange background.

    Building with patterns

    Patterns continue to be an integral paradigm to empower everyone. A redesign of the Inserter offers an easier way to pick and choose between patterns, including newly bundled 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. & Footer options. Developers and Site Builders who provide patterns for clients can expand where patterns can be used with an option to register patterns specifically for templates. The result of advancing patterns allows you to: 

    • Find patterns with greater ease thanks to a redesign of the Pattern Inserter (41379) along with improved categorization (44501). 
    • Switch between Header and Footer patterns bundled into Core (46017).  
    • Register patterns for specific template types, limiting where the patterns appear. For example, an Error 404 pattern would only make sense when used with the 404 template (45814).
    • Pick from a growing collection of Query 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. patterns from the block itself (44140), with an improved setup state (47366). 

    Video of the redesign of the Pattern Inserter featuring the new footer patterns

    Designing with WordPress

    With the strong styling foundation provided by theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. and the Styles Engine, new functionality is slated for inclusion to unlock more styling possibilities and to make it easier than ever to design what you want within the Site Editor. 

    • Design blocks globally with the new Style Book that allows you to see all blocks on your site as you style them (44420). 
    • Use an inline preview of blocks when working with Styles to better understand the impact of changes (42919). 
    • See a broader view of your template when selecting a style variation (44987).
    • Apply local changes from a single block globally across your entire site, with a new “Apply globally” control within the Advanced block settings (44361, 46965). 
    • Copy and paste block styles to create consistent designs faster than ever (44418). 
    • Add custom CSSCSS Cascading Style Sheets. for your entire site (30142), or individual blocks (44412). 
    • Edit block style variations from Styles (46343).
    • Add the ability to set minimum fluid font size in theme.json for fluid typography (45536). 
    • Add shadow preset support with theme.json (46813).

    Video of the Stylebook

    Read more about style related options coming to 6.2 in the Strengthening style options post.

    Moving performance forward

    Work continues to iterate on performance improvements for theme.json thanks in part to using object cache. A hallway hangout is set for February 13th, 2023 to discuss the cluster of improvements going into this release for anyone keen to hear more details. To get involved with performance work, join the performance meetings and the #core-performance channel.

    Iterating on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.2/8.x items

    Work has mainly revolved around the following items:

    To get involved with this work, please review the overarching tracking issue, the current open issues, and join #core-php.

    General 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 and enhancements 

    In TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., there are already 110+ tickets closed. Taken together, these bug fixes and enhancements continue to further the overall experience of using WordPress. 

    Thank you to @desrosj @hellofromtonya @matveb for input on this post and @kellychoffman @richtabor @priethor for helping edit it.

    X-post: Community Booth at WordCamp Asia 2023

    X-post from +make.wordpress.org/community: Community Booth at WordCamp Asia 2023

    Editor Chat Agenda: February 8, 2023

    Facilitator and notetaker: @bph

    This is the agenda for the weekly editor chat scheduled for Wednesday, February 8, 2023, 03:00 PM GMT+1This 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/..

    Announcements

    • The release 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 release, 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/ 15.1, is scheduled for Feb. 8th, WordPress 6.2 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 is schedule for Feb. 7th. The project board for WordPress 6.2 Editor tasks is available.
    • WordPress 6.2 Planning Roundup
    • “The end of Phase 2 of the Gutenberg project is approaching!” wrote @matveb in Phase 2, Finale
    • New Post on the Developer Blogblog (versus network, site): Creating custom block styles in WordPress themes by @greenshady
    • 6.2 Dev Notes tracking issue is a work in progress.

    Key project updates:

    Task Coordination.

    Open Floor – extended edition.

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

    • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
    • 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.

    Props to @paaljoachim for review

    #agenda, #core-editor, #core-editor-agenda, #meeting

    Editor chat summary: February 1st, 2023

    This post summarizes the weekly editor chat meeting (agenda for February 1st meeting) held on Wednesday, January 1 2023, 03:00 PM GMT+1 in Slack. Moderated by @fabiankaegy.

    Release of Gutenberg 15.1 RC

    A project board for WordPress 6.2 Editor tasks is available.

    Key project updates

    Phase 2 Overview Tracking Issue

    Task Coordination

    @jeffpaul

    Asked if anyone is aware of items ideally landing in WP 6.2 that are NOT in GB 15.1 and otherwise at risk for getting into the release.

    @ndiego

    Responded that we are actively tracking 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/ issues and PRs related to the release on the 6.2 Project Board. If you come across an issue or PR that you think is related to the release, please feel free to add it to the board and @annezazu and I will triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. from there.

    @hellofromtonya

    Gave a quick update on Fonts 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..

    It’s not ready for 6.2 due to a complete rewrite and renaming with first release in 15.1 1day after the 6.2 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. It’s essentially a brand new API. It needs several GB release cycles to stabilize. As the API is completely different, all issues need to reviewed as they may no longer be validate.

    @paaljoachim

    Created two new issues that will help improve the experience of using a 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 Theme:

    Open Floor

    @cbirdsong

    Is wondering if there is any movement on any of the issues surrounding layout panel/general concept. At the very least I’d really like to remove the ability for editors to set custom values in the panel, or be able to provide a list of presets instead of just an empty text field.

    Related issue: https://github.com/WordPress/gutenberg/issues/31980

    #core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary