The Test Team helps manage testing and triage across the WordPress ecosystem. They focus on user testing of the editing experience and WordPress dashboard, replicating and documenting bug reports, and supporting a culture of review and triage across the project.
Please drop by any time in SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. with questions or to help out.
We have identified that to join the Test Team, people should get some experience running these sessions. Something that is not hard as someone needs to know how to make a test Chat Agenda and Follow that for the meetings.
@sirlouen proposed that if a person ran a Test Chat Meeting, they would then be eligible for a Test Contributor Badge. This year, many people were nominated without any experience, and this is not acceptable
He also added that Test Scrubs is another activity that future Test Reps should do and hence Test Scrubs is also promoted for eligibility. For example: 2 test scrubs + 2 meetings will be enough for eligibility for Test Rep position with my proposal
Test scrubs can be initiated from today, but meetings will be initiated starting January 2026, and we will have a list when people sign up for it.
@oglekler added that a Team RepTeam RepA 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. must be experienced with all team activities before applying to become a Team Rep. This will save both the applicant and team any surprises.
@mosescursor suggested that Team Reps should come from the Test Team members. A position a person gets after cycling through the Test Team processes.
@oglekler said that Team reps and Team members will have to support the contributors to get to that level. This also calls for contributors interest.
A simple Q&A
How can a Person sign up for running a meeting? After January, during each meeting, the current Team Reps will be asking if anyone wants to run the meeting and we will also post the current “list” in case more than one user has proposed. When they ask, you can raise your hand and they will contact you, put you in the list, and explain all the steps on how to run the meeting. We are starting on January because we need the current reps to get a little more experience before starting to add new members to this
How can I run a Test Scrub? You can run one of these whenever you want. You can just contact @sirlouen or any of the current test reps, and we will make sure you learn the basics on how to run a good test scrub
@sirlouen will then be drafting the new page for reps.
Remember that now Forum discussions are happening in GitHub, and the discussions will be kept for a week before a decision is made. Feel free to write there whenever you want, send a new proposal, etc (remember that every proposal has to go first through a meeting like this and then 1 week to discuss in githubGitHubGitHub 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/)
Update on Test Handbook: New pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92) are available; contributors can update content via GitHub issues.
No progress in this regard.
Again, feel free to comment in any of these three, or if you are brave, send a PR with your proposal for any of the 3.
For anyone that could be interested in becoming a Test Rep, or Test Team Member(like @sirlouen), who is not a Test Team Rep, but a Test team member), it’s important to engage in these kinds of things and promote things in general. It’s impossible to join the team from a passive position
@muddassirnasim expressed interest and will join the mentorship cohort.
@sirlouen is working on developing a GutenbergGutenbergThe 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 protocol for the future. This is mainly driven by the many people struggling with testing in the previous scrubs. We have to understand that testing needs some technical skills, but many people have some skills but waste a lot of time trying to set up everything, and they never come back again after the setup.
@sirlouen is trying to lower the learning curve a little bit by introducing WordPress Playground Concepts. In these tests we will not be using wordpress-develop or wp-env anymore for testing, except for very complex tickets that need much more deep work.
These are going to first be tested in the 2 Testing Scrubs scheduled for Tomorrow.
Release Squad Testing scrub
and Regular testing scrub
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
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:
Collaboration: add blockBlockBlock 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:
Merging of Test Handbook in GithubGitHubGitHub 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
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 CoreCoreCore 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:
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:
2. GutenbergGutenbergThe 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
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.
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
WordPress 6.9 is planned for December 2, 2025, with RCRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 beginning November 11, 2025.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held in 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:
Collaboration: add blockBlockBlock 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:
Merging of Test Handbook in GithubGitHubGitHub 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.
We are currently under review of the home page and the PR is here for review.
We also need a new draft for the Team Reps for discussion in the next Test chat.
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 CoreCoreCore 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:
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:
2. GutenbergGutenbergThe 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
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.
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 🎉 @dhruval04
WordPress 6.9 is planned for December 2, 2025, with RCRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 beginning November 11, 2025.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held in 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.
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 blockBlockBlock 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:
Merging of Test Handbook in GithubGitHubGitHub 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 syncing. 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.
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 CoreCoreCore 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:
Who? Any QA or PHPPHPPHP (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 loopLoopThe 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.
2. GutenbergGutenbergThe 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
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.
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:
WordPress 6.9 is planned for December 2, 2025, with RCRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 beginning November 11, 2025
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held in 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.
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 blockBlockBlock 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:
We are in the Final Review of the Test Handbook in GithubGitHubGitHub 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.
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 CoreCoreCore 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:
Who? Any QA or PHPPHPPHP (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 loopLoopThe 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.
2. GutenbergGutenbergThe 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
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.
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 migrationMigrationMoving 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
WordPress 6.9 is planned for December 2, 2025, with BetaBetaA 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 beginning October 21
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
As part of the upcoming WordPress 6.9 release, we are introducing a brand-new blockBlockBlock 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., the Accordion block.
This block was first introduced in the Gutenberg 21.5 release as an experimental feature and is now being stabilised. More testing is needed to ensure its reliability and polish before it ships with the WordPress 6.9 release.
What is the Accordion block?
The Accordion block lets you display collapsible sections of content, which is ideal for FAQs, expandable information lists, etc.
The block acts as a container, i.e. Accordion that holds multiple child blocks, which we can consider as Accordion Items
By default, adding an Accordion block inserts two Accordion Items.
Each item contains a title and an expandable content area that can be toggled open or closed.
Note: In the latest specification, only one accordion item is inserted. This will the new behavior in GutenbergGutenbergThe 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/ 21.9 Release. Please check #72021 PR for more details.
Now, before we start testing, let’s understand the difference between the Accordion and the Details blocks.
While both blocks allow collapsible content, their structure and purpose differ:
Accordion block: Designed for multiple collapsible grouped sections, such as FAQ lists. It contains several Accordion Items inside a single parent block, as shown in the screenshot below.
Details block: Intended for a single collapsible section, for example, a single “Read more” toggle as shown in the screenshot below.
Test Steps
Please try out the Accordion block in the latest Gutenberg pluginPluginA 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 (v21.5 or later). Here are some testing scenarios:
Visit Gutenberg > Experiments and check the option to “Enable experimental blocks”
Navigate to Post/Page or template
Verify you can add an Accordion block now.
Confirm that the Accordion Item is added with an Accordion Heading and an Accordion Panel (ref the screenshot above)
Edit item placeholders and add content inside the Accordion Panel
Save and confirm that expand/collapse both function as expected in the front end and the editor
Verify Reordering
Move Accordion Items up or down
Confirm that the order updates correctly in both the editor and the frontend
Styling & Settings: This only applies to all items when you work through the global styles. If you change the style of an item in a block instance, the style will not be reflected in other items.
Confirm that styles are reflected in all items consistently.
Verify the duplicate of the accordion block
Remove an existing item and ensure the block continues to function as expected
Discover more scenarios based on the different use cases and see if that works as expected. Refer to the visual below to understand how you can play around with different settings.
Testing Instruction
Why Your Testing Matters
Your feedback helps ensure the Accordion block offers a consistent, stable, and intuitive experience for all users, including the AccessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) considerations. If you encounter any related issues, please report them here.
How to report an issue
Write down step-by-step instructions on how an issue can be reproduced. Also, attach a screenshot/screencap for better clarity.
Use the Test report plugin to collect all essential metaMetaMeta 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. information.
Before creating a new issue, check if there is a related issue has already been reported in the Guutenberg repo. If not, create a new one here.
A new feature is introduced in Gutenberg 21.8RC: the ability to hide blocks from the frontend.
This option provides more flexibility for working with content and layouts. Instead of deleting or moving a blockBlockBlock 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. you don’t want published, you can temporarily hide it. The block remains in the editor, but it will not appear on the live site until the visibility is switched back on.
Why this matters
Makes it easier to experiment with different layouts without losing content.
Allows draft or placeholder content to stay visible in the editor but hidden from site visitors.
Encourages non-destructive editing and smoother collaboration.
Creates a foundation for future enhancements
Key Changes to Observe
In the editor,
It adds a menu item to the block settings options to change the block’s visibility.
“Hide”: A “Hide” option appears on each block by default
“Show”: Clicking on “Hide”, the block setting toolbar should display the “Show” option.
In the List view, the visibility of multiple blocks can be changed simultaneously.
Select the block and click on the “Hide” control from the toolbar settings
Observe that the block is no longer visible in the editor, and the “Show” control should be toggled on for that block (Observe the List view)
Check the change in the front end, and the block should be hidden
Now, turn off the hide setting in the editor
The block should reappear in the editor and the front end
Nested blocks: Place a few blocks inside a Group/Columns block and hide the parent.
Confirm that all inner blocks are hidden
Multiple instances: Hide different blocks across the page and verify that only the chosen ones are excluded from the frontend.
Testing Instruction
Since this feature is newly introduced, it needs testing, and feedback is especially valuable.
Please share:
Did the toggle behave as expected?
Did you run into inconsistencies between the editor and the frontend?
Were there any issues with nested, synced, or reusable blocks?
Your input will help refine this feature as it moves toward the WordPress 6.9 release.
Follow #71203 PR for more details. If you observe any related issues, please feel free to report them here.
📈Performance / Asset Check
Hidden blocks should not appear on the frontend, and their related CSSCSSCSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site./JS should no longer be actively used. Optionally, you can verify this via the Network tab or CSS Coverage in DevTools. Visible blocks must continue loading normally. On small pages, coverage differences may be subtle; the key point is that hidden blocks do not add frontend markup or assets. Check #9213 PR for more details. If you would like to verify this, follow the steps in the comment.
If you’re unsure whether what you are experiencing is a bug, you can ask in the #outreach channel on the WordPress SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
Change Log
1.0.0 Initial Post
1.1.0 Add Performance check
Props to @wildworks@psykro for pre-publish review of this post.
A recent update to the Site Editor template management system has significantly enhanced WordPress template management by providing greater flexibility and control over the template editing experience. It is now possible to view created templates separately from theme templates, store more than one template per template type (or slug), edit templates and save them without making them active, manage template revisionsRevisionsThe 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. more effectively, and mark specific templates as active or inactive according to requirements.
For more context on the history behind this change, read through the following proposal on GitHub
Key Changes
Template Management: Allows multiple templates with the same target slug and introduces the ability to switch between them by setting one as “active.”
Theme templates remain the “source of truth”: To edit a theme template, one first needs to create a duplicate of it as a Created Template and edit that template.
Theme Template Control: Users can now disable theme templates (except the essential index template)
New UIUIUI 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.: Adds “Active templates” and “Created Templates” views in the Site Editor
APIAPIAn 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. Simplification: User templates now use standard Post Type REST APIREST APIThe 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/. endpoints
Enhanced Features: Enables revisions, duplication, and trashing through normal Post actions
Benefits
Created templates are retained when switching themes
Users can disable template edits when needed
New templates can be created without immediately publishing
Templates can be added for all slugs, not just missing ones
Improvements to template revisions, template duplication, and deleting templates
Install and activate the Gutenberg Nightly plugin from GutenbergGutenbergThe 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/ Times, or use this Playground link
Navigate to Site Editor > Templates and test the new template management features
Verify that you can see template categories for Active, Custom, and theme templates.
Test custom theme templates
Create, edit, and save a custom theme template, and confirm it only appears in the Created templates list.
Test active templates
Create multiple templates for the same target slug (ie, single-post) and ensure you can activate/deactivate different templates, and that the front-end rendering uses the correct template.
Confirm that when activating one template, the other templates for that slug are marked as inactive.
Test that you can activate a template in the template editing view.
Test default template fallback
Deactivate a theme template and ensure the correct fallback template (in line with the template hierarchy) is used instead.
Test switching themes
Once you’ve created a custom template, switch to a different blockBlockBlock 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. theme and ensure the custom template remains.
Test that template revisions, duplicating templates, and deleting templates work as expected.
Testing Steps
Breaking Changes
Changes to getEditedPostId and getCurrentPostId may impact plugins
Plugins should migrate to use getEditedPostSlug instead
Logging bugs and discussions
All existing bugs are being tracked in the following tracking issue in the Gutenberg GitHubGitHubGitHub 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/ repository: https://github.com/WordPress/gutenberg/issues/71735
If you encounter any new bugs related to this feature during testing, please log them as new issues and mention them in the above tracking issue.
If you’re unsure whether what you are experiencing is a bug, you can ask in the #outreach channel on the WordPress SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
+make.wordpress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., +make.wordpress.org/themes
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.
Please only test on a development siteDevelopment SiteYou 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 InstallA 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 > BetaBetaA 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 CandidateA 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.
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 blockBlockBlock 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 RevisionsRevisionsThe 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 theescape 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:
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 HooksHooksIn 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 APIAPIAn 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.
Query LoopLoopThe 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 imageA 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.
Navigation Block Enhancements
You can select the default coreCoreCore 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 (UIUIUI 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)
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 sidebarSidebarA 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 categoryCategoryThe '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 JSONJSONJSON, 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:
Get ready for the next big release in the WordPress world! WordPress 6.3 is set to launch on August 8, 2023. Every major releaseMajor ReleaseA set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. comes with exciting new features and improvements, and we need your help to make sure it’s the best it can be!
This is the first Call for Testing post for the 6.3 release. Be on the lookout 👀 for future posts that highlight additional enhancements in the release.
Please only test on a development siteDevelopment SiteYou 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 InstallA 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 > BetaBetaA 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 CandidateA 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.
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 blockBlockBlock 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 🔑
Interface
Command Palette
The new Command Palette (formerly “Command Center”) allows users to quickly navigate to specific pages, templates, or template parts, as well as offers an easy way to start to create new content in the site editor. From within the editor just use Cmd-k (macOS) or Ctrl-k (Windows) and start typing for a context-aware selection of commands and shortcuts. (49330)
Extenders can also find information on creating custom static, dynamic, and context-aware commands with this feature’s public API. (51169)
Improved Page Management
The site editor now allows site builders to manage pages, edit content, access page details, and even draft new pages to be published later. Look for the new Pages menu from Appearance > Editor. (50857, 50767, 50565, 47142)
Content Editing in Site Editor
This feature allows site authors to seamlessly switch between template and page content editing within the site editor. UIUIUI 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. improvements also highlight what’s being edited – template or content – and allow for a more efficient workflow when building out a site. (44461, 50857)
Distraction Free Mode in Site Editor
Distraction Free mode, previously available in only the post and page editor, now brings the calmness to the site editor, offering a 1:1 preview to site authors. (51173)
Block Theme Preview
Previews of block themes now launch in the site editor, providing efficient previews of locally-installed themes. To see this feature in action, navigate to Appearance > Themes and click “Live Preview” on any block-based theme.
This feature can also be accessed by appending the following to a site editor or frontend URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org: ?wp_theme_preview=theme-slug where theme-slug is a locally installed theme to preview (e.g. twentytwentytwo). (50030, Trac 58561)
Using the Style Book in the Styles’ Site View
The Style Book can now be activated while browsing global style options for easier visualization of effects on various page elements. (50566, 50393)
Styles RevisionsRevisionsThe 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 update introduces support for global style revisions in the site editor, providing the ability to review or roll back to a previous state. (50089)
Top Toolbar Improvements
The editor’s “Top toolbar” has been refined with better handling of the limited space in this area, and better accounts for browser viewport width limitations. (40450, 49634)
Blocks
Time to Read Block
This feature has been moved to a future version of WordPress so that it may undergo additional testing before release.
The new Time to Read block allows you to display the estimated time the average reader takes to read the current page or post. Letting readers know right off what their estimated reading time is helps them to decide if they should continue reading, or save the post for later.
Begin by adding the block from the block picker, or from an empty Paragraph block starting with the forward-slash (“/”) key, and start typing the block name: /time to read. (43403)
Details Block
WordPress now introduces the versatile Details block, offering a seamless way to toggle the visibility of content, such as very long text, code samples, or spoilers. This block comes with two new inner blocks: Details Summary and Details Content. The summary is always visible, and the content is collapsable to be shown or hidden when readers toggle it.
Add the Details block through the block picker, or from an empty Paragraph block starting with the forward-slash (“/”) key, and start typing the block name: /details. (45055)
Color and layout support for the Cover block
The Cover block now supports the text color design tool. The enhancement makes it easier for users and theme authors to customize the color for all inner blocks with a single setting. Along with this benefit, this change makes it easier to handle transforms from the Media & Text block. (41572)
Footnotes
The new Footnotes block is a powerful addition that automatically links and formats footnotes, allowing users to work efficiently while annotating content. Not an insertable block per se, Footnotes are activated by highlighting text in a block, and then in the context menu selecting More > Footnote. (51201)
Caption Styling
Theme authors can now create custom styles for Caption elements directly via theme.json. Once added, options become available in the Styles interface, and allow creators and users to customize captions without touching code. (49141)
Image Aspect Ratios
Adding a powerful feature to the Image Block that makes usage of this block much easier. Until now, to effectively replace one image with another, their size had to be the same. The image aspect ratio section solves this problem completely. New image size controller that comes with aspect ratio, scale, width, and height options. (51138, 51545)
Patterns
More Curated Patterns
The new “Curated” filter in the pattern directory helps users differentiate between CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.-bundled and community contributed patterns.
Easier Pattern Creation
Effortlessly design and save patterns, just like the convenient reusable blocks you’re familiar with. Now you can easily create and save your favorite patterns as synced or unsynced patterns, saving you time and effort when designing your projects. You can find your saved patterns under Custom Patterns. (46248)
You must be logged in to post a comment.