Week in Test: December 1, 2025

Hello and welcome to another edition of Week in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Table of Contents

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Test Handbook 📘

Merging of Test Handbook in GithubGitHub GitHub is a website that offers online implementation of git repositories that 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/

For the last few weeks, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

  • We want to inform that the Test Handbook is officially synced. There might be a couple of bugs and things that are not looking good pending to be fixed.
  • Feel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.
    • You can send a PR with the fix, or simply send the issue, and we will check it

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions. Did you know that contributions to the Test Team are also a fantastic way to level up your WordPress knowledge and skills? Dive in to contribute, and gain coveted props 😎 for a coming release.

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Testing

a. Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment. Why?
It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

b. Bug Reproduction

It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.

The following tickets have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, the provide a bug reproduction report:

The following 6.9 tickets need testing, those are having patches:

d. Handbook Review

Here are the current activities being discussed in the Test Handbook:

  1. We need to review https://github.com/WordPress/test-handbook/pull/98

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

👋 Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets (13) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

b. Gutenberg Patch Testing

All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed, and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

  • Nothing to test yet this week

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉
@fakhriaz
– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held in 2025.

2025 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

Props to @sirlouen @oglekler for helping review this article and offering feedback

#core-test, #fse-outreach-program, #full-site-editing, #gutenberg, #make-wordpress-orgupdates

Week in Test: November 24, 2025

Hello and welcome to another edition of Week in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Table of Contents

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Test Handbook 📘

Merging of Test Handbook in GithubGitHub GitHub is a website that offers online implementation of git repositories that 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/

For the last few weeks, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

  • We want to inform that the Test Handbook is officially synced. There might be a couple of bugs and things that are not looking good pending to be fixed.
  • Feel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.
    • You can send a PR with the fix, or simply send the issue, and we will check it

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions. Did you know that contributions to the Test Team are also a fantastic way to level up your WordPress knowledge and skills? Dive in to contribute, and gain coveted props 😎 for a coming release.

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Testing

a. Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment. Why?
It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

b. Bug Reproduction

It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.

The following tickets have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, the provide a bug reproduction report:

The following 6.9 tickets need testing, those are having patches:

  • Nothing for this week

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

👋 Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

b. Gutenberg Patch Testing

All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed, and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

  • Nothing to test yet this week

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉
None this week. Please keep contributing.
– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held in 2025.

2025 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

#core-test, #fse-outreach-program, #full-site-editing, #gutenberg, #make-wordpress-orgupdates

Week in Test: October 27, 2025

Hello and welcome to another edition of Week in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Jump to: Calls for Testing |Test Handbook | Weekly Testing Roundup | WordPress Core Testing | Gutenberg Testing | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

  • Collaboration: add 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.-level comments:

Test Handbook 📘

We are in the Final Review of the Test Handbook in GithubGitHub GitHub is a website that offers online implementation of git repositories that 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/

For the last few weeks, a good amount of test contributors have embarked on the journey of reviewing our new Test Handbook based on Github. Reviews are underway and the final process set to start. The handbook is awaiting one meeting and will be fully replaced with the new GitHub based content.

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions. Did you know that contributions to the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Testing

a. Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment. Why?
It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

b. PHPUnit Tests 🛟

Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. developer contributors who can (or are interested in learning how to) build automated PHPUnit tests. Why? Automated tests improve the software development feedback 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. for quality and backward compatibility.

The following tickets need PHPUnit tests built to accompany their respective patches:

c. 6.9 Related issues need testing

The following 6.9 tickets need testing, those are having patches:

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

👋 Want to contribute to WordPress/gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

b. Gutenberg Patch Testing

All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

  • Nothing to test yet this week

Profile Badge Awards 🎉

No Badges Issues this Week.
Badge awarding has been paused until the Test Handbook migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. is complete. Keep contributing and we will get to you

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2025.

2025 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

#core-test, #gutenberg, #core

Props to @sirlouen @nikunj8866 for helping review this article and offering feedback

#core-test, #fse-outreach-program, #full-site-editing, #gutenberg, #make-wordpress-org-mobile, #make-wordpress-orgupdates, #web

Test Chat Summary: October 22nd, 2025

On Thursday, October 22nd, 2025 at 05:00 PM GMT+3, <test-chat> started in #core-test facilitated by @mosescursor The agenda can be found here.

1. Attendance

In attendance was:
@sirlouen @nikunj8866 @rakib03029 @mobarak @r1k0 @rollybueno @fakhriaz @passoniate @shsajalchowdhury @harshalkadu @narenin

2. Volunteer

This week’s Note-taker was @mosescursor
Meet next week’s note taker @nikunj8866 

3. Test Team Discussions

  1. Time to Review the Test Handbook Overhaul:
    •  We are in the last lap for the test handbook completion!
      • @sirlouen reported that he had already contacted the 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. team to schedule a date to start syncing and also mentioned that the project is 99.99% complete, and once a date is confirmed, they will complete the final administrative tasks and proceed. @sirlouen also noted that @dd32 was copied in on the communication.
      • @sirlouen also shared that he is going to edit all current documentation pages to add a GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ link and indicate that the pages are outdated. Once the sync is complete, those pages will be removed and replaced with new content. He also mentioned that work can begin on one or two GitHub pages now, starting with the badges page.
      • @nikunj8866 emphasized that the slugs needs to be observed as same before removing and archiving old pages
    • A few Tickets were pending Reviews and volunteers were assigned. We are almost there. All tickets were reviewed by meetings end and merge ready. @sirlouen will proceed to merge
  2. Proposal for creating an Archive Section in the Handbook.
    The archive section was supported in the last meeting and these two pages are among those to be first archived.
  3. We need to build a new page for 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/ testing
    @sirlouen is moving to Gutenberg tests and will do build the page

4. Open Floor

No additional topics were brought up during the open floor section of the meeting.

5. WordPress Ecosystem Announcements

Please receive the ECO system announcements

  1. Test Team Announcements
  2. Call for Testing
    Several Issues are available for testing ahead of the 6.9 release. Let’s help collaborate on these as well. Here is  a short list but more will surely be found especially after 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. release last night

6. Other Meetings

We usually have 2 meetings held every week and the times have been listed bellow for next week. an adjustment has been made to include the WordPress 6.9 Test Scrub and will soon be listed

Props to @nikunj8866, @sirlouen for helping review these notes and offering feedback.

#core, #core-test, #fse-outreach-program, #gutenberg, #make-wordpress-org-mobile, #make-wordpress-orgupdates

Team Chat Agenda: 22nd October 2025 

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, October 22, 2025, 5:00 pm GMT+3 , which is held in the #core-test Slack channel. Well wishers are all welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test
Last Updated Wednesday, 22 October 2025 at 16:00 GMT+3

Props to @nikunj8866 for helping review this article and offering feedback

#core, #core-test, #fse-outreach-program, #make-wordpress-org-mobile, #make-wordpress-orgupdates

Week in Test: February 5 2024

Hello and welcome to another edition of Week in Testthe place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Jump to: Calls for Testing | Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

  • Did you get a chance to look at the Design Share: Jan 15 – Jan 26 post? All features are already available in Gutenberg 17.6 and it would be great if site builders could test them before they land in WordPress 6.5
    • Improved Lightbox UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. – The lightbox toggle is now part of the link settings for the images, as it’s somewhat a link to the resized view and links and lightbox a mutually exclusive.
    • Cover Aspect Ratio – Applied to the Cover 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. in various forms.
    • Drag & Drop Displacement for moving blocks in the List view
    • Scrolling Top Toolbar is an interesting solution to the problem that we run out of real estate for everything to be placed in the Toolbar when tagged to the top.
  • What’s new in Gutenberg 17.6? (31 January) is available to download, if you get chance download and test upcoming features for WP 6.5

Weekly Testing Roundup 🤠

Here is the Weekly update: Test Team Update: 5 February 2024

Here’s a roundup of active tickets that are ready for testing contributions.

Did you know that contributions with the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

Reproduction Testing 🔁

Who? Any contributor.
Why? It is helpful to show an issue exists for other users in order to move a ticket forward for patching.

The following new tickets are awaiting review, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:

Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

PHPUnit Tests 🛟

Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback 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. for quality and backward compatibility.

The following 6.5 tickets need PHPUnit tests built to accompany their respective patches:

6.5 Related issues need testing

The following 6.5 tickets need testing those are having patches:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2024.

February 2024 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

#fse-outreach-program

Week in Test: 29 January 2024

Hello and welcome to another edition of Week in Testthe place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Jump to: Calls for Testing | Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Weekly Testing Roundup 🤠

Here is the Weekly update: Test Team Update: 29 January 2024

Here’s a roundup of active tickets that are ready for testing contributions.

Did you know that contributions with the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

Reproduction Testing 🔁

Who? Any contributor.
Why? It is helpful to show an issue exists for other users in order to move a ticket forward for patching.

The following new tickets are awaiting review, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:

Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

PHPUnit Tests 🛟

Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback 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. for quality and backward compatibility.

The following 6.5 tickets need PHPUnit tests built to accompany their respective patches:

6.5 Related issues need testing

The following 6.5 tickets need testing those are having patches:

  • Pattern overrides: work is ready to test starting with making paragraph blocks overrideable. Up next, headings, buttons and images are expected to be added soon as blocks that can have overrides.

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2024.

2024 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

#fse-outreach-program

FSE Program Final Touches Summary

This post is a summary of the Final Touches call for testing for the FSE outreach program, the twenty-sixth and final effort. As always, I want to highlight those who helped to bring others along with them in this latest effort: 

  • InstaWP for allowing the outreach program to use their tooling for free, enabling more folks to jump into this call for testing and for more creativity in what we are able to test. 

As mentioned on the Evolving the FSE Outreach Program post, thank you to everyone who has helped from the start with these feedback efforts.

High level summary 

This testing call spanned numerous planned WordPress 6.4 features, including a focus on the Font Library (which is no longer planned for 6.4). Most feedback pertained to feature requests and usability concerns, highlighting the following common themes:

  • A desire for improved visibility of current and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. categories in pattern creation.
  • Requesting additional controls, similar to the Cover 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., for adding background images to a Group block.
  • A need for more informative error messages in the Font Library, especially when deleting fonts.
  • Enhancing the discoverability of the Font Library.

Instead of breaking down feedback into bugs, feature requests, and general usability feedback, everything is broken down into groupings of features with extra quotes. This decision was driven by the limited volume of feedback received (only three responses) and the evident recurring themes within the feedback itself. 

Command Palette 

The Command Palette was featured throughout this call for testing, including to navigate to a page with a similar name to a pattern. This quickly reinforced a need for more context when searching for items and running commands:

Using the Command Palette. I write Portfolio and get up two Portfolios that have two different icons. One that looks like a post/page and the other as if it is a template part. Hovering over both it would be nice if it said something like: Portfolio page and the other Portfolio template part. To strengthen the meaning of the icons I see.
@paaljoachim in this comment.

It would be awesome to have more information about the current state of a toggle, “Disable distraction free mode” instead of “Toggle distraction free mode.” Or maybe make the icon of the active toggle reflect its state by adding a black background like the Settings or Styles buttons do.
@josvelasco in this comment.

I like that the command palette now includes site editor navigation like list view toggle, distraction free toggle, and code view toggle. However, I agree with you and the folks here that suggest that the command name having a clearer context of what each will do.
@franz00 in this comment.

Patterns 

While adding categories to patterns works, the ability to see current categories, core provided or otherwise, would make it much easier to stay organized:

When creating synced patterns, it is great that now we can put them into categories. However, I’ve also learned that WordPress has its own default categories for patterns from this URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org https://github.com/WordPress/gutenberg/blob/c20350c1d246163201375f090b0b7b4ab49b1dad/packages/block-editor/src/components/inserter/block-patterns-tab.js#L35 (‘custom’, ‘featured’, ‘posts’, ‘text’, ‘gallery’, ‘call-to-action’, ‘banner’, ‘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’). Personally, I want my patterns organization to be as much closer to WP default categories as possible, but I can’t find those predefined categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. names being listed somewhere in the Site Editor interface. Perhaps we could have categories checkbox for those, like the post page have?
@franz00 in this comment.

Since there was a pattern called “Portfolio,” it was kind of confusing to find where to edit the page with the same name. The command palette would be more verbose and say “Edit template Portfolio” instead of just “Portfolio.”
@josvelasco in this comment.

I see that I can add a category, but I can not see which categories already exist. As I might want to place this into a pre existing category.
@paaljoachim in this comment.

Font Library 

The following specific items were raised with a particular note around the need for better error messaging both when uploading and deleting fonts:

I clicked the “Aa” icon to open up font management just because I followed your instructions, but I couldn’t have found the font management easily without them. I love icons, but this is only visible with a label.
@josvelasco in this comment.

I tried to upload a .zip on purpose but got no errors. It may be nice to have or suggest allowed font formats and a confirmation notification when one gets uploaded.
@josvelasco in this comment.

However, I found that the activation/deactivation and deletion of fonts somewhat confusing. Why would fonts deletion be offered on active, check marked, fonts? Would it make more sense to only offer fonts deletion to the inactive (unused) ones? Because deleting an active font directly impact the pages that use them, which will cause the page to automatically fall back to the default font. Besides, this is done without any warnings.
@franz00 in this comment.

I see the Fuggles uploaded above the Theme Fonts. There is a heading for Theme fonts but no heading for the fonts above it. It would be nice to have an “External Fonts” etc heading for the ones that are not Theme fonts.
@paaljoachim in this comment.

Other

Of the following items, the desire for more controls in adding a background image to the Group block was mentioned by all three responses. In particular, folks wanted to see the ability to change focal point. 

I find the rename feature taking too many steps and feels cumbersome. I would like to double click it just as if I was on a Mac to rename. I am happy the feature is in even if it kinda feels half baked.
@paaljoachim in this comment.

Color adjustments are fine, but having the same background adjustments available as the cover block would be great. Focus point, at least.
@josvelasco in this comment.

I also noticed that when navigating blocks in list view, the up arrow key sometimes cannot traverse back up when it encounters synced patterns, or a footer template part.
@franz00 in this comment.

#fse-outreach-program, #fse-testing-summary

Help Test WordPress 6.4

Get ready for the next big release in the WordPress world! WordPress 6.4 is set to launch on November 7, 2023, and we need your help to make sure it’s the best it can be. With exciting new features and improvements, this release promises to be a game-changer for WordPress users everywhere.

Stay up to date with the latest pre-release builds by checking the WordPress 6.4 Release Schedule for availability. For real-time updates and discussions, join the #core-test Slack channel. Engage in the testing community by participating in weekly scheduled team meetings and test scrubs.

Table of Contents:

Testing Environment 💻

Please only test on a development siteDevelopment Site You can keep a copy of your live site in a separate environment. Maintaining a development site is a good practice that can let you make any changes and test them without affecting the live/production environment. and not on a production/live site. You can follow these instructions to set up a local installLocal Install A local install of WordPress is a way to create a staging environment by installing a LAMP or LEMP stack on your local computer. or use a tool like this to set up a development site.

Once your development site is set up, please install and activate the WordPress Beta Tester Plugin. After activation:

  • Navigate to Tools > 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. Testing.
  • Set the update channel to “Bleeding Edge” and click Save Changes.
  • Set the stream option to “Beta/RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. only” and click Save Changes again.
  • Navigate to Dashboard > Updates and click the Update to latest… button.

For more detailed steps, click this link for complete instructions.

Testing Tips 💡

At a high level, here are a few tips to keep in mind to get the most out of helping to test:

  • Test across different browsers.
  • Test in different languages.
  • Compare features on different screen sizes, including tablets and mobile.
  • Use just your keyboard to navigate, or use a screen reader.
  • Test with both 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 classic themes.

Key Features to Test 🔑

Style

Global Styles 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.

This release introduced a handy feature that allows you to reset global styles back to their default settings with ease (52965). With this enhancement, you can effortlessly reset any changes made to global styles back to their original state. To try out this feature, simply make a few revisions to the global style and then open the revision panel. You’ll see a list of all the revisions, and at the bottom, there’s an option called “Reset to Default.” Click on it to return to the original settings.  Now, you only need to go through one revision check instead of two (53281). Previously, the revision panel was only available after two styles of revisions were saved in the database.

Please help test global style revisions with this video to guide you:

Twenty Twenty-Four Default Block Theme

Twenty Twenty-Four default theme is set to launch in 6.4. The theme for the year 2024 will use new design tools to make websites look better and be easier to edit. It will have special designs for three groups of people: entrepreneurs and small businesses, photographers and artists, and writers and bloggers. Here, you can find Related Gutenberg Issues and PRs.

Please help test the default Twenty Twenty-Four theme, this is the demo video:

Interface

Write with Ease

In this release, ongoing efforts are being made to ensure a smooth and enjoyable writing experience in WordPress(#53305). These enhancements include the addition of new keyboard shortcuts and improvements in copying and pasting text from other sources. The Link preview feature (53566) now includes a convenient “Open in new tab” control, making it simpler to enable or disable this option. Additionally, toolbars for List, Quote, and Navigation blocks have been enhanced to make your writing and editing process more efficient.(#53699, #53697). Please help test using keyboard shortcuts and copying and testing text from other sources.

Please help test the improved writing experience for list items with this video to guide you:

Please help test the capture toolbar in the quote block with this video to guide you:

Please help test the ‘Open in New Tab’ feature with this video to guide you:

Improvements to List View

The List View in WordPress has undergone some great enhancements. Now, managing your content is even more straightforward and user-friendly. You can easily rename Group blocks using a handy options menu that pops up. When dealing with gallery and image blocks, you can now see previews of your media to make sure everything looks just right. Additionally, resizing and duplicating blocks have become much more efficient, with keyboard shortcuts available for quick actions. The List View now allows the escape key to deselect blocks if blocks are selected(48708). These improvements in the List View make organizing and editing your content in WordPress a breeze.

This video is showcasing the use Escape to deselect blocks feature:

Please help test by renaming group blocks in the list view with this video guide:

This image showcases a media preview for the gallery and image blocks:

An image showcasing media preview for gallery and image blocks


Please help test by using keyboard shortcuts for duplicating blocks with this video to guide you:

 Improvements to the Command Palette 

The Command Palette has undergone several changes and improvements since its first introduction in WordPress 6.3. For example, you can now do more with blocks using new commands, including block transforms and the options to duplicate, copy, remove, and insert after/before. The Command Palette also looks different with a fresh design. Plus, it now supports adding commands without icons. If you’re using WordPress on a small screen, like a mobile phone, the Command Palette will work better for you. It also uses more consistent language and actions, making it easier to use. Lastly, there are improvements in snackbar motion, making your experience smoother. These changes make managing your WordPress site even easier and more user-friendly.

Please help test adding blocks by commands and registering commands without icons with this video to guide you:

This image shows you registering commands without icons.

This video is showing some improvement for the command palette on smaller screens:

Test with tweak and add more consistent commands:

This video displays snackbar motion, and you can test this feature by similarly giving commands.

Please check out more improvements to the recent updates made to the Command Palette.

Blocks

Block 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. (Previously Auto-inserting Blocks)

Introducing the Block Hooks feature, a reimagined approach to the earlier concept of Auto-inserting Blocks. Basically, Block Hooks is 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. that developers can use to make websites more flexible. It allows one block to attach itself to another block and show its content before or after that block. You can also attach a block to a parent block and make it appear at the beginning or end of the list of child blocks inside it. (53987

Even though Block Hooks is mainly for developers, it also gives a nice experience to the end users by automatically inserting a block into a specific location. It lets developers place blocks where they want them to be and gives room for customization. The goal is to make block themes more adaptable with the help of plugins.

One thing to keep in mind is that the block using this API will only be auto-inserted if the original template or part hasn’t been changed by the user. This is done to respect the user’s choice. This API can only be applied with block patterns, template parts, and templates that come from the block theme files. It doesn’t alter anything the user has already created or changed on a website. 

Note: This feature is a more technical item to test. Check out this for a more detailed guide.

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. Block Pagination Enhancements 

Now, you no longer need a full page reload when you navigate between pages in a Query Loop block. There’s a new setting that prevents full page reloads. This improved way of moving between pages is made possible by a special version of the Interactivity API, and it makes browsing smoother. Plus, you can also decide how many pages you want to show using the Query Page Numbers block for even more control. Query block: Client-side pagination (53812), make mid-size parameter settable for Query Pagination block. (#51216).

Please help test adding pagination in your query block. This video guides you through the pagination in the query block.

Client Side Pagination

List Block Enhancement 

In the List Block, a new feature has been introduced that allows you to merge consecutive lists instead of keeping them as individual blocks. This enhancement streamlines your editing experience by combining lists that appear one after another, making it easier to manage and format your content seamlessly. (52995)

Group Block Enhancements

Now, you can easily rename Group blocks to organize your content better (53735). This feature makes it simpler to identify and manage different sections of your page, streamlining your editing experience. Additionally, the introduction of background images for Group blocks brings more creativity and customization to your layouts. These enhancements empower you to create more organized and visually appealing content in WordPress. (53934)

Background image support to the Group block

Please help test by renaming the group blocks using this video guide.

Add Aspect Ratio to the Image Block’s placeholder

Aspect ratio controls to the Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. block were introduced in the 6.3 version, and now, these helpful controls have been extended to the placeholder of the Image block. This enhancement offers greater flexibility, particularly when designing wireframe-style patterns that establish a layout for users to fill in with their content.

You can select the default coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./navigation-link variant within the core/navigation block, offering more flexibility and customization options for your navigation menus (50982)

Please test by adding navigation block and start customizing it with this video to guide you.

Add Lightbox Functionality for your Images

WordPress 6.4 introduces an improvement to the image experience with the new Image Lightbox feature. Recognizing the need for clarity in the user interface (UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.), a dedicated Settings panel has been instituted for the image block. Within this panel, users can easily locate the Lightbox toggle, available both in Global Styles and Block settings.Display your pictures in an engaging way using the brand-new lightbox functionality. This cool feature will work with image blocks, so you can click on an image and see it in a bigger size right on top of your existing content. (51132)

General Block Improvements

  • Preformatted: Add margin and padding support. (45196)
  • Social Links: Add Threads Icon. (52685)
  • Verse: Enable line breaks. (52928)
  • Details: Add block gap support. (53282)
  • File: Add margin and padding support. (45107)
  • Column: Add stretch alignment (53325).
  • Image: Keep image size upon replacing an image (49982).
  • Buttons: Allow using a button element for button blocks (54206).
  • Post Content: Add block gap support (54282).
  • Post Content: Add color control support (51326).
  • Footnotes: Add link, background, and text color support (52897).
  • Footnotes: Add typography, dimensions, and border block supports (53044).

Patterns

Create your own Pattern Categories

Now, you can neatly group your patterns by categories when you create them. These categories are handy because you can use them to organize and find your patterns easily. You can also edit these categories in the 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. when you’re editing a pattern.

To ensure this feature functions smoothly, here are the steps to follow: Begin by adding various user patterns, both synced and unsynced, assigning categories to each (remember to hit ‘enter’ or add a ‘,’ after each categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.). Then, navigate to the site editor patterns page and verify that the categories appear in the left navigation panel. Confirm that selecting a category displays the corresponding patterns accurately and that theme patterns continue to appear as expected. Check that all patterns are accessible under ‘All Patterns’ and that the search function operates seamlessly. Lastly, duplicate a theme pattern and ensure that the new pattern inherits the same category. Additionally, when adding a user pattern with the ‘Footer’ category, make sure it displays alongside the theme Footer patterns, taking into account the category slug distinction (theme patterns use ‘footer’ while the user category name should match this).
To make things even simpler, all patterns, whether they’re synced or not, are listed together in one place. There’s no need to look in different tabs for synced patterns; they’re all in the same section. (53837)

Please help test creating categories, adding synced and unsynced patterns, and assign them categories with this video to guide you:

Import/Export Patterns as 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. files.

To maintain compatibility with Reusable blocks, you can now import and export patterns as JSON files, providing a straightforward way to transfer custom patterns between websites. (54337

Please help test import and export patterns with this video to guide you:

Where to Report Feedback 🗣

If you find any issues, it’s best to share them on the WordPress.org alpha/beta forums, or, if you are more technically savvy and comfortable, on Core Trac. For helpful reporting guidelines, refer to the Test Reports section of the Test Handbook.

Please share feedback as soon as you can before the release on November 7, 2023.

A big thank you to @annezazu,@annebovelett @coachbirgit, @ironprogrammer, and @rashiguptaa for reviewing and contributing to this post.

Changelog 🪵

2023-11-01

  • Changed Query loop enhanced pagination name to Force Page Load.

2023-10-06

  • Removed Font Library feature as it is punted(moved) to the WP 6.5 release.

2023-10-03

  • Update on Font library and link added to individual Help Test font library post.

2023-09-26

  • Initial post.

#6-4, #call-for-testing, #fse-outreach-program, #full-site-editing

Hallway Hangout: Let’s chat about the WordPress 6.4 & Evolving the FSE Outreach Program

This is a summary of a Hallway Hangout that was wrangled in the #fse-outreach-experiment channel as part of the FSE Outreach Program.

Video Recording:

Notes/Links:

When I was the only one in attendance, I decided to still record an update on both WordPress 6.4 and the FSE Outreach Program. To do so, I went through the Evolving the FSE Outreach Program post and went through various top 6.4 related items. Anything starred is not yet merged:

From there, I went through the Roadmap to 6.4 post in more detail, explaining what isn’t going to make it and has been punted.

#fse-hallway-hangout, #fse-outreach-program