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.
Following this year’s nominations and voting period, we are pleased to announce our new Test Team Reps for the 2024-2025 term! 🎉 Join us in welcoming Olga Gleckler and Krupa Nanda to represent the Test team!
Olga is a full-stack developer with over 15 years of experience in software support, marketing, and web development. She is an active WordPress contributor, a Codeable expert, and a fantasy writer.
She has been contributing to WordPress in her spare time since 2019.
She was the Test co-lead for the WordPress 6.5 release and the triage co-lead for several other releases. She is actively participating in the Contributor Mentorship Program. She believes in open-source and is passionate about everything she does. She likes rock music and sharing knowledge.
Krupa is a QA Engineer with over 6+ years of experience who specializes in testing WordPress-based projects. Her career has also included roles as a Project Coordinator and Release Manager, where she oversaw the development of in-house plugins and add-ons.
Krupa attended her first WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. in October 2023 and has since tried to contribute to as many as possible. She also participated in the second batch of the Contributor Mentorship Program (CMP), where she learned how to contribute effectively. Krupa successfully completed the program and is now a mentor for the third batch of CMP. In addition to her mentorship role, Krupa is a Global Translation Editor (GTEGeneral Translation EditorGeneral Translation Editor – One of the polyglots team leads in a geographic region https://make.wordpress.org/polyglots/teams/. Further information at https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor.) for the Gujarati locale. She also volunteers and speaks at WordCamps and meetups.
Krupa is from Jamnagar, Gujarat, and she currently lives in Pune, Maharashtra. Beyond her professional pursuits, Krupa’s journey is characterized by the seamless integration of motherhood and a thriving career. As she continues to grow, Krupa is excited about the future opportunities that lie ahead.
We want to inform everyone about an important update regarding the ongoing 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. poll. On October 3, we noticed an unusual pattern of voting, with a large number of votes coming from the same IP address. After investigating, we discovered that some of the votes were generated by bots, which compromised the integrity of the poll.
To address this issue, we’ve taken immediate action by implementing new restrictions to prevent multiple votes from the same IP address. This will ensure that each person can cast vote only once, maintaining fairness for everyone involved.
As part of this process, we have also reset the poll, which means that all previous votes have been erased. If you’ve already voted, we kindly ask that you please resubmit your vote.
This election is closed, and I’m contacting the finishers for final steps before making the official announcement. Thank you, everyone who voted, as well as the nominees who stepped forward for this role!
Important Update: On October 3, we observed a high volume of votes coming from the same IP address in the 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. poll. Upon further investigation, we discovered that bots were involved. As a result, we implemented restrictions, and multiple votes from the same IP will no longer be accepted. We have reset the poll, clearing all previous results. If you voted before, please submit your vote again. Read our announcement post. Thanks
From August 13 to October 1, 2024, the Test team opened nominations for new reps to serve over the 2024-2025 term. The polls are now open and ready for your votes!
What Are Team Reps?
For a refresher on the Test Team Rep role, please see the most recent call for nominations. The Test team will elect two team reps for the next term, to collaborate and share responsibilities.
And because many of you are testers and like to break test things 😉, please note that attempting to vote for all three at once will lock out your vote 🙅. Please resist the temptation to test the voting platform!
👉🏻 The poll will remain open for two weeks, until October 11, 00:00 UTC. After that, votes will be tallied and reps selected based on votes received.
Get Ready to Test the Future! WordPress 6.7 is just around the corner, and we need your help to make this release the best yet! With the official launch set for November 12, 2024, now is the perfect time to start testing. By catching bugs early, you’ll be saving countless users from potential headaches when they upgrade. Whether you have a few minutes or a few hours to contribute, every bit of testing counts and is deeply appreciated. Your efforts directly contribute to ensuring a smooth and reliable release for millions of WordPress users. Let’s make WordPress 6.7 flawless together!
One of the highlights in this release is the new default theme, Twenty Twenty-Five, offering flexibility with a variety of patterns for categories like services, landing pages, and more. Focused on simplicity and adaptability, it includes stunning typography and global-ready color palettes.
WordPress doesn’t require you to be a certified software tester or professional QA to contribute to testing. Simply use WordPress as you normally would for your own needs. If you encounter any issues or feel that something isn’t working as expected, you can report.
Not sure what the expected behavior should be? No worries! Join the conversation on WordPress Slack, or create a ticket on Trac, where a helpful global WordPress community is always ready to assist.
Recommendations for Testing WordPress 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./RCRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. Versions:
Test CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Features that Matter to You: Use your site for the purpose it was created. For instance, if you’re a blogger, running a social platform, or managing an e-commerce store, set up a staging site (ask your hosting provider if you’re unfamiliar with staging site). Update WordPress in the staging environmentStaging EnvironmentA staging environment is a non-production copy of your site. This is a private place to build the site -- design, copy, and code -- until your client approves it for production or live. Sometimes used in addition to, or as a Development Environment., and continue using your site as you would daily. This will help you identify any issues that may affect your regular workflow. Take note of any issues or troubles you experience after the update. Do not test or update your live site with a beta version for testing purposes.
Use the ‘General Checklist’ provided in the post below to verify everything functions as expected after the update.
Ways to Test WordPress Beta Versions
There are multiple ways to test WordPress development or beta versions:
Playground
Playground is an easy and fast way to test beta or release candidateRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. versions of WordPress without setting up a full environment. You can quickly spin up a test environment using WordPress Playground.
Local Hosted Site
You can use software like Local or wp-env to create a local WordPress site. Once the site is ready, you can install the Beta Tester 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 to switch to the beta version of WordPress.
Once your site is up and running, switch it to the development or beta version of WordPress using the WordPress Beta Tester plugin. This plugin makes it easy to install pre-release versions of WordPress. To use the plugin:
Install and activate the WordPress Beta Tester plugin.
Navigate to Tools > Beta Testing.
Choose the “Bleeding edge” or “Point releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. nightlies” option, depending on what you want to test.
Click Save Changes and update your WordPress version.
For more detailed instructions, follow this guide.
Via WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/
If you prefer working with command-line tools, you can use WP-CLI to quickly install a WordPress beta version.
Steps:
Create a local WordPress site with your preferred method.
Once the site is set up, open your terminal and navigate to the root directory of your WordPress installation.
Run the following command to update to the latest beta version:
wp core update --version=6.7-beta3
Or
wp core update --version=6.7-RC1
(Replace the version number as needed, such as –version=6.7-beta2.)
This method allows you to switch between different versions quickly, making it easier to test specific builds.
Using a Staging Site
You can create a staging site for your production/live site and update it to the WordPress beta/RC version. This allows you to safely test the new version without affecting your live site. Ensure that everything works as expected before applying updates to your production/live environment.
Testing Patches
If you are planning to test patches, you can follow these instructions to set up a WordPress development version locally.
Using Playground – with Playground, you can also easily test individual Core tickets without installing any software in your system. If you have a particular PR in the `wordpress-develop` or `gutenberg` repo that you’d like to test in the browser? you can do so through the following links:
If you want to quickly test the updated WordPress version’s compatibility with your site, please verify the following checks:
First, update your WordPress to the Beta/RC version, enable debugging in wp-config.php, and update your theme and plugins.
Ensure plugins and themes didn’t deactivate automatically after the update.
Check the WordPress Site Health tool for any new warnings or issues.
Confirm there are no layout breaks or misaligned elements.
Test links and permalinks to ensure there are no 404 errors.
Verify that posts, images, and media are displayed correctly.
Ensure the sitemap and robots.txt files are functioning properly.
Ensure full access to the admin dashboard without errors.
If your site has custom blocks, create content in a 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. and edit existing content.
Create a new post: add content, copy-paste text, and manually add media files. Save the post and observe the console for any issues.
Create a new page, add content, and check its display in different browsers.
Open the browser’s developer console and check for any errors, warnings, or notices.
Open the error log file and check for notices, warnings, and fatal errors.
Review user roles and permissions to ensure they remain intact.
Verify that any scheduled posts or automated tasks (like backups) still function as intended.
Ensure all integrated services (like payment gateways or analytics) are operational.
Open your site in different browsers and verify that all functionalities work as expected.
Key Features to Test
New default theme – Twenty Twenty-Five
With WordPress 6.7, the Twenty Twenty-Five theme brings a perfect balance of simplicity and flexibility. Designed with inspiration from nature and history, the theme offers a wide array of patterns and templates to suit various use cases, from personal blogs to complex portfolios. It includes rich colour palettes, and a diverse range of blog templates, making it adaptable for global audiences, for more details about this new theme read the introduction post.
Patterns
The Twenty Twenty-Five theme introduces a wide range of pre-built patterns that help users create pages efficiently. These patterns cover various categories such as services, about pages, and calls to action and others. They are designed to offer flexibility and interoperability, allowing users to quickly build out intentional and cohesive page layouts.
Testing Steps:
Navigate to Appearance > Editor to open the Site Editor.
Open any template or create a new page.
Click the “+” icon to add a new block.
Go to the Patterns tab in the block inserter.
Select patterns from different categories such as Services, About, Calls to Action, or Gallery.
Insert the patterns and check if they are displayed correctly.
Test the interoperability of these patterns by combining multiple patterns on a single page.
Adjust and customize the patterns as needed and ensure that they are responsive across different devices.
Ensure that the layout in the Site Editor matches the layout on the Frontend.
Color Palettes & Styles
The theme offers a diverse range of colour palettes and style variations, allowing users to customize their site’s appearance with ease. The theme includes multiple color palettes and typography pairings designed for global use, ensuring high-quality support across various languages and regions. These options give users the flexibility to match their site’s aesthetic to their unique style while maintaining a cohesive and visually appealing look.
Testing Steps:
Navigate to Appearance > Editor to open the Site Editor.
Click on the Styles button (the half-moon icon) in the top-right corner.
Choose different color palettes and typography pairings to apply to your site.
Observe how the colors and fonts change across the site when a new palette or style is selected.
Save the changes and preview the site on the frontend to confirm that the new styles are applied correctly across all pages.
Templates
Twenty Twenty-Five offers a range of adaptable blog templates, including text-focused blogs with sidebars and visually-driven photo blogs. It fully integrates with the Site Editor and utilizes new design features like the Grid block and Pattern/Section Styles.
Alternative Template Designs
The theme includes four sets of alternative designs: a text-only blog, a photo blog, a news blog, and a blog with a vertical headerHeaderThe 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.. These designs are built as patterns that replace the content of the template.
To test the photo blog design, follow these steps:
Go to Appearance > Editor.
Select the menu option Templates.
Choose the template you want to test, such as Single Post, Page, Archive, or Blog Home.
In the editor, open the Settings 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..
Select the Template tab.
In the Template tab, locate and expand the Design panel.
The Design panel displays previews of the available designs:
Hover over a preview to see the design name.
Click on the preview to replace the content of the template with the chosen design.
Ensure that the layout in the Site Editor matches the layout on the front end
Section Styles
The Twenty Twenty-Five theme introduces four unique section styles, designed to change the colors of Group and Columns blocks. These styles offer flexibility in creating visually appealing layouts. Testing involves ensuring that the new styles are applied correctly in both the editor and the frontend, with a focus on usability and readability.
Testing Steps:
Create a new post or page in the dashboard.
Insert a Group block or Columns block.
Inside the Group or Columns block, add some blocks like heading, paragraph, etc.
Open the Settings Sidebar, and select the Block tab.
Open the Styles tab and find the Styles panel at the top.
Select one of the alternative styles. Repeat for each style to test them all.
Ensure the design looks the same in both the editor and on the frontend.
Verify the color combinations are readable, including the background, text, links, and buttons.
If you encounter any issues or have suggestions, feel free to create an issue here.
Refining Data Views
Ability to Set the Density of Information in the Grid Layout
In WordPress 6.7, users gain the ability to adjust the density of grid layouts, offering a more customizable and responsive viewing experience. This update brings a 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. control in the grid view, enabling users to select their preferred density. For more details about changes related to this, please follow the discussion.
Testing Instructions:
Open the Site Editor from the dashboard.
Navigate to the Pattern section.
Click on the settings icon to open the appearance and settings panel.
Adjust the grid density option from ‘Preview Size’.
Observe how patterns display.
Option to Hide/Show the Filters in the User Interface
Looking for more details about this change, refer this ticket #63203
Ability to Customize the Column Order in Table Views
WordPress 6.7 introduces the ability to customize the column order in table views, offering more flexibility in how data is displayed. This feature allows users to move table columns left or right to create a more personalized layout when managing templates, patterns, or pages.
Testing Instructions:
Open any table data view (Templates, Patterns, or Pages) in WordPress.
Click the headers of the columns to see available actions.
Select “Move left” or “Move right” to reorder the columns.
Verify that the columns adjust accordingly and maintain the new order across page refreshes.
Please refer to ticket #63416 for more details about this change.
Graduate Data View Options Out of a Menu to Allow More Design Expression
The data view options have been improved for better design flexibility. A new “View Option” setting has been added with a gear icon. This opens an “Appearance” popover, allowing users to manage view preferences such as items per page and sorting options like “Sort by”, “Order by.”, Preview size, items per pages, etc. More details: #64175
Testing Instructions:
Open any data view (Templates, Patterns, or Pages) in the site editor.
Click on the gear icon to reveal the “View Option” setting.
Open the “Appearance” popover to explore the available options.
Adjust the items per page and sort options (e.g., “Sort by” and “Order by”).
Verify that the settings are applied and reflected in the data view.
Polishing the 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.
The Query Loop block, a key component for site building in WordPress, is undergoing refinements to enhance its usability and intuitiveness. While it remains a powerful and versatile block, the focus of these improvements is on making customization more straightforward. Key changes include better context detection and clearer settings copy to ensure users can easily create and manage complex queries.
Testing Instructions:
Open the WordPress dashboard and create a new page or post.
Insert a Query Loop block into page or post.
Review the settings in the sidebar, paying attention to the descriptions.
Customize the Query Loop and ensure that the changes are intuitive and easy to apply.
Save your changes and check the front-end output for accuracy.
Follow this iteration issue for more information about changes.
Zoom Out to Compose with Patterns
WordPress 6.7 is introducing a new “Zoom Out” feature to enhance how users interact with patterns while building and editing their sites. This feature offers a high-level editing view, allowing users to focus on patterns rather than granular block-by-block adjustments. Key aspects include a zoomed-out interface for inserting patterns, creating new pages with an emphasis on patterns, and managing them (moving, deleting, etc.) via a vertical toolbar. Users can toggle between zoomed-out and detailed block editing, enhancing the overall user experience with improved pattern manipulation and advanced content-only editing.
Build with Patterns
Testing Instructions:
Navigate to the Site Editor and Insert patterns into a page or post.
Use the Zoom Out button to switch to a zoomed-out view.
Verify that the overall structure of the page is visible, allowing for easier manipulation of patterns.
In the zoomed-out view, try moving, deleting, and rearranging patterns using the new vertical toolbar.
Ensure the patterns respond accurately to drag-and-drop actions and are placed correctly without shifting unexpectedly.
Check that the zoom option functions as expected, allowing you to zoom in for detailed block edits and zoom out for a broader view of the page.
Observe whether there are any UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. issues or inconsistencies when interacting with patterns in the zoomed-out mode.
Exit the zoomed-out mode and ensure that all changes remain intact and display correctly in the standard block editor.
Explore Zoomed-out with Style Variations
Testing Instructions:
Open Appearance > Editor to access the Site Editor.
Select the canvas to begin editing the blog home template.
Open Styles and select Browse styles to view the various style variation options. This will automatically trigger the zoomed-out view.
Scroll through the different style options and explore how the zoomed-out view functions.
Toggle between entering and leaving the zoomed-out view by turning the Style block on and off, switching style blocks, and returning to the style variations for comparison.
Please refer to ticket #64197 for more details about this change.
Media Improvements
WordPress 6.7 introduces significant media improvements, enhancing how media is handled and displayed. Key updates include support for HEIC image uploads with automatic conversion, automatic sizing for lazy-loaded images, and expanded background image functionality. Users can now set background images at the block and global levels, with new options like fixed backgrounds. Additionally, a more streamlined modal interface has been introduced for managing background images. These improvements optimize media handling and elevate site design flexibility.
Support HEIC Image Uploads
HEIC image uploads are automatically converted to JPEG on the server, ensuring compatibility with all browsers. The original HEIC image can still be downloaded from the attachment page. If the server doesn’t support HEIC conversion via Imagick, WordPress will prompt users to manually convert the image.
Testing Instructions:
Upload a HEIC image in the Media Library.
Confirm the image is converted to JPEG.
Check if the original HEIC is available for download on the attachment page.
Verify Imagick HEIC support in Tools → Site Health → Info → Media Handling.
Ensure a warning appears if the server lacks HEIC support.
Confirm the image displays correctly in posts and pages across different browsers.
Please refer to this detailed post about this feature.
Auto Sizes for Lazy-loaded Images.
This feature automatically adds the auto value to the beginning of the sizes attribute for any image that is lazy-loaded. This enhancement improves image responsiveness by helping browsers to determine the appropriate image size automatically.
Testing Instructions:
Enable lazy loading for images on your WordPress site (this may be enabled by default).
Upload or insert an image into a post or page.
Open the browser’s developer tools and inspect the image tag.
Check that the sizes attribute begins with auto for any lazy-loaded image.
Save and preview the post or page to ensure proper image loading behavior on the front end.
Please refer to ticket #61847 for more details about this change.
Block-Level Background Images in Global Styles
WordPress 6.7 introduces the ability to set background images for blocks at a global style level, giving users greater control over the appearance of their site. This new feature allows users to apply background images across all instances of a specific block type, such as the Quote block, while also maintaining the flexibility to override the default background at the individual block level. This adds another layer of customization to WordPress themes, allowing for more cohesive and visually appealing designs.
Testing Instructions:
Open the Site Editor from the Appearance > Editor
Select a template and navigate to Styles > Blocks.
Search a block and set a background image for a block at the global style level, for example, for the Quote block.
Check that all Quote blocks now have the default background image applied.
Verify that the global and individual block-level settings are working correctly without any issues.
Please refer to ticket #60100 for more details about this change.
Add Support for Background Attachments (fixed backgrounds)
WordPress 6.7 introduces a new feature that allows you to toggle the background attachment behavior for blocks and site backgrounds. Users can now choose whether the background image scrolls with the page or remains fixed. This enhances design flexibility for block and site backgrounds. Please refer to ticket #61382 for more details.
Testing Instructions:
Add a background image to the block.
Confirm that the background image scrolls with the page by default.
Toggle the “Fixed background” option on.
Verify that the background image is now fixed.
Save the changes and check the frontend to confirm the behavior.
In the Site Editor, under Styles > Layout, add a site background image.
Test the same scroll and fixed behavior for the site background.
Update Background Image Support to Use a Modal
This update introduces a flyout sidebar panel that allows users to add, upload, or reset background images. The popover provides easier access to background image controls, ensuring seamless adjustments to background image properties like position, size and more. Please refer to ticket #60151 for more details.
Testing Instructions:
Navigate to the block settings in the sidebar and add a background image.
Verify that clicking on the background image in the sidebar triggers the modal popover.
Use the controls within the popover to adjust the background image properties (e.g., position, size).
Design tools
The design tools have been significantly enhanced with expanded block support, offering more flexibility and creative control for designers and themers. Key updates include the long-awaited shadow support for Group blocks, as well as added support for borders, colors, padding, and backgrounds across various blocks like Buttons, Galleries, and Paragraphs. These improvements aim to streamline customization, allowing for more sophisticated designs directly within the block editor.
Click here to see details about each change
Buttons: Add border, color, and padding block supports. (63538)
Post ExcerptExcerptAn excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox.: Add border support (64022)
Term Description: Add border block support (63630)
Continuing to Improve 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. 8.x Support
WordPress 6.7 continues to enhance compatibility with PHP 8.x by removing code that was specific to older, unsupported PHP versions. This ensures better performance, security, and stability for sites running on the latest versions of PHP.
Testing Instructions:
Update your WordPress site to PHP 8.x.
Performs tests as described in the “General Testing” section above.
Monitor for any warnings, notices, or errors in the site’s functionality.
Check the error log to ensure no deprecated or removed functions are in use.
Verify that the admin dashboard and frontend load without issues.
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. Launches and Iterations
This release includes two new APIs designed to simplify developers’ workflows:
Template Registration API
This feature simplifies template registration for plugins by introducing a new API. Previously, plugins had to hook into multiple filters, but now they can register templates more easily and efficiently.
Testing Instruction: Please refer to the testing steps outlined in ticket #61577 to verify this feature.
Preview Options API
This API allows for greater flexibility in preview functionality, enabling plugin developers to seamlessly integrate custom preview options into the WordPress editor. It addresses the need for varied publishing flows and tools.
Testing Instruction: Please refer to the testing steps outlined in ticket #64644 to verify this feature.
Interactivity API
WordPress 6.7 introduces enhancements to the Block API, including new features aimed at improving interactivity. Currently, the focus is on testing the UI and functionality of the Lightbox Support feature.
Testing Instructions:
Add a Gallery block to a post or page.
Upload and insert a few images.
For each image, select the “Link” option and choose “Click to expand” to enable the lightbox. (See reference: Image)
Save the page and view it on the front end.
Test that clicking on the images opens the lightbox and ensure it supports keyboard 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).
Block Bindings API
The Block Binding API allows developers to bind custom 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. and dynamic data from plugins to blocks. This API simplifies the integration of post meta fields and custom data into block attributes, enabling dynamic content rendering of blocks without changing the existing codebase. This test focuses on verifying that post meta can be successfully registered, updated, and displayed in the front end using various blocks.
Testing Steps:
Add the below code to your theme or plugin file to register the post meta and simulate dynamic plugin data.
add_action('init', function () {
// Register custom post meta.
register_meta(
'post',
'block_binding_meta_test',
[
'label' => __( 'My Custom Post Meta', 'text-domain' ),
'show_in_rest' => true,
'single' => true,
'type' => 'string',
'default' => '',
]
);
// END Register custom post meta.
// Register dynamic data binding.
$blockBindingCallback = function () {
return sprintf( __( 'Current Time: %s', 'your-text-domain' ), date_i18n( 'r' ) );
};
if (function_exists('register_block_bindings_source')) {
register_block_bindings_source( 'my-plugin/current-time', [
'label' => __( 'Current Time', 'text-domain' ),
'get_value_callback' => $blockBindingCallback
] );
}
// END Register dynamic data binding.
});
2. Create a new post and add a Paragraph block.
3. In the block settings, select Attributes and click Content. You should see the option to select My Custom Post Meta.
4. Enter a value for the post meta and save the post.
5. On the front end, check if the custom post meta value is displayed.
6. Add another Paragraph block and ensure the previously entered custom meta value is automatically populated.
7. Repeat the steps with other blocks like Image, Heading, and Button.
8. Now manually add another Paragraph block using the below code.
9. Verify that you can see the current time output on the front end.
HTMLHTMLHTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. API
The HTML API, introduced in WordPress 6.2, is designed for block developers to provide better control and flexibility when working with HTML within blocks. This API enables support for custom HTML tags and attributes within the block editor. You can learn more about the HTML API in this WordPress Core post.
Testing Steps:
If you’re a block developer, explore the support for new HTML tags and functions.
Refer to this 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/issue for further details on how to test the new functionality.
If you’re a developer eager to dive in, check out the details in the API section of this post to give these exciting features a try!
What to Notice
Were all the features easily accessible and intuitive to use?
Did you notice any performance issues, such as slow loading or lag during editing?
Were there any visual inconsistencies or layout issues across different browsers or devices?
Did the drag-and-drop functionality work as expected in patterns?
Did you encounter any accessibility issues beyond screen readers and keyboard navigation, like color contrast or focus management?
Did the preview mode accurately reflect how the content appeared once published?
Did the experience handle large or complex pages smoothly without freezing or crashing?
Where to Report Feedback
If you find any issues but aren’t sure if it’s a bug or where best to report the problem, share them on the WordPress.org alpha/beta forums. If you are confident that you found a bug in WordPress Alpha/Beta/RC, report it on Core Trac for rollback auto-updates and the Gutenberg GitHub repo for every other feature.
As you’re aware, WordPress 6.7 is slated to be the third major release of 2024, with the official release date set for November 12, 2024. As we gear up for this important milestone, our Test team will be shifting gears a bit.
Test Scrub in Place of Test Team Triage
Starting from our next weekly Test team meeting, we’ll be running a Test Scrub instead of the usual Test Team Triage session. This Test Scrub will focus specifically on the WordPress 6.7 milestone tickets. It’s a great opportunity to contribute to this 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. and make a tangible impact on the final product.
We’ll be concentrating on tickets that are tagged with Has Patch / Needs Testing. You can find these tickets in this report.
Interested in Leading a Test Scrub?
Did you know that anyone can lead a Test Scrub at any time? Yes, that means you can!
If you’re interested in leading a scrub, simply pingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me @ankit-k-gupta or @webtechpooja on 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 the day and time you’re considering, along with the report or tickets you’d like to focus on.
Are you planning a scrub that’s specifically focused on WordPress 6.7? That’s fantastic! We can add it to our schedule, so the rest of the team knows to join in. Leading a scrub is a great way to contribute, and you’ll earn props in the Slack channel for your efforts!
Let’s Contribute Together
This is a perfect chance to get involved with the major release of WordPress 6.7, learn more about the process, and help ensure the quality and stability of WordPress. Your contributions will make a difference, so join us for the Test Scrub sessions and be a part of this exciting release!
Update 1: This call for nominations has been extended to 2024-10-01 00:00. (see comment below).
Update 2: Nominations for the 2024-2025 term are closed.
It’s time again to nominate the Test Team Reps who will serve for the next 12 months!
This Call for Nominations is open until 2024-09-23 00:00. Please leave a comment identifying your nominee(s) before then.
For a quick refresher of 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. roles across the project, please see the Team Reps post on Team Updates.
The Role
Reps in the Test Team perform primary and secondary (or backup) duties to help support team chats, make updates to the team’s blog and handbook, remove blockers, keep a pulse on team objectives, and promote testing opportunities within the WordPress project.
As a reminder, Reps are not called “team leads” for a reason. While people elected as Team Reps will generally come from the pool of folks that people think of as experienced leaders, the Team Rep role is designed to change hands regularly.
Help new contributors with their WordPress Testing related queries.
Help raise awareness for testing needs, especially for upcoming releases.
Raise issues or red flags that other teams should be aware of or discussing.
Participate in quarterly update progress reports (example).
These duties are shared between the primary and secondary Reps (see Rep Responsibilities on the Team Rep page).
Qualifications
A Rep is an active team member who is reliable and trusted, advocates for and is knowledgeable of one or more areas of testing, and wants to represent, nurture, and grow the team to better serve the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project.
Test Team Reps must be committed to showing up and performing regular duties, and should expect a time commitment of at least 2-4 hours per week. Reps serve for a term of one year.
How Test Team Elections Work
Step 1: Call for Nominations 📣
The first step is to reach out to the community with a Call for Nominations (this post!)
Please nominate in the comments of this post. You can write a comment as simple as “I nominate @the_persons_username.” Self-nominations are also welcome by leaving a comment such as “I nominate myself.”
After the deadline, each nominee will be contacted to discuss qualifications and to confirm their acceptance of the nomination.
If you get nominated, please do not feel like you have to say “yes”. It’s okay for you to decline the nomination if you don’t feel like this is the right fit for any reason. “Thank you, but no thank you!” 😉
Step 2: Vote for Team Reps 🗳
An election will happen only if there are more than two accepted nominations within the nomination period; otherwise the nominees will become the new Test Team Reps.
If held, the election will be conducted by an anonymous poll (example). The poll will remain open for 2 weeks.
Step 3: Announce Team Reps 🎉
Once uncontested nominations have been accepted, or in the event of an election the voting period has passed, the new Test Team Reps will be announced in a post (example).
Time to Nominate!
Are you ready? It’s time to nominate folks to serve as our Test Team Reps for the new term! If you have any questions, please feel free to ask in the comments.
We’re gearing up for an exciting Contributor Day at WordCamp Europe (WCEU) 2024, set to take place next month in the beautiful city of Torino, Italy! This annual gathering of WordPress aficionados brings together a diverse group of contributors to collaborate, learn, and make significant strides in the WordPress project. Here’s a sneak peek at what we have planned for the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team and how you can get involved.
Core Test Team Goals
Our objectives for the day are ambitious but focused:
Onboard New Contributors: Provide guidance and mentorship to newcomers eager to join the Core Test Team.
Expand Automated Testing Coverage: Increase the number of automated tests for core components.
Test bugs or features and report new issues
Improve Documentation: Enhance the clarity and comprehensiveness of testing guidelines.
Triage Issues: Review and prioritize open tickets related.
Collaboration and Community
Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WCEU 2024 will not just be about work; it will also be about building connections and fostering community spirit. The collaborative atmosphere will be palpable, with contributors exchanging ideas, offering help, and celebrating each other’s successes. The energy and enthusiasm of the participants will be truly inspiring, reinforcing the sense of belonging and shared purpose within the WordPress community.
Test Team Table Leads
We’re thrilled to introduce our Test Team Table Leads for WCEU 2024. These dedicated individuals will be guiding and supporting contributors throughout the day:
To ensure you get the most out of Contributor Day, please review the following before the event so that you can focus on the fun stuff when you arrive:
More technically-experienced contributors will find other useful prep tips in this WCEU 2023 Core post.
Don’t forget your laptop and charger!
Looking Ahead
As we prepare for this Contributor Day, we look forward to the progress and innovation that these contributions will bring to the WordPress project. We encourage everyone who plans to participate to stay engaged and keep the momentum going. Your contributions, whether big or small, make a significant impact.
Thank you in advance to all the contributors who will join us in Torino and those who will participate remotely. Together, we’re making WordPress better.
See you next month at WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2024!
+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//test/
Roll up your sleeves, it’s time to help test WordPress 6.6 ahead of the July 16th, 2024 release date. Finding a bug now will help the millions of folks who upgrade later and this testing period is a critical part of what helps ensure smooth releases for all. Please know that any help you can provide to test this next release, whether it’s 10 minutes or 10 hours, is very much appreciated.
Changelog
June 6th: Updated the section on “Mix and match typography and color palettes from all styles variations” in light of changes to the feature to make it more 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 author focused.
Testing setup
You can test the latest development version, or a specific 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./RCRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. with the WordPress Beta Tester Plugin on any 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. you’d like (don’t use in production). You can also set up a local WordPress environment or create another site on your hosting environment to test.
If you are planning to test patches, you can follow these instructions to set up a WordPress development version locally; or if you want to test just what is already in the release, use WordPress Playground or install WordPress in your local environment and use the WordPress Beta Tester Plugin.
For more detailed steps about the Beta Tester 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, follow this link for complete instructions. With Playground, you can also easily test individual Core tickets.
General testing
These are general steps to take after updating. For more specific features, please read on:
Update your theme and plugins to the latest versions.
Switch to the Beta/RC/Night build you want to test.
Check Site Health to see if there are already some issues that will be unrelated to the update.
Check for Errors, Warnings and Notices
Turn on the debug log by adding settings to your wp-config.php. (Note that SCRIPT_DEBUG can change the behaviour of scripts, so it is recommended to test this constant both on and off.)
Run a spider against your site to process all the available pages.
Open the developer console in the browser.
Try to create a new post, add some content and save it, especially try to copy and paste content from another source, add comments, add media files of different types and do other usual actions in the admin. While doing it, pay attention to the information in the console to see if there are any issues. Note: Sometimes some issues are not visibly affecting any of the site functionality and sometimes it can be tricky to decipher where they are coming from.
Check special functionality, go through the most important logic of your site: if you have an e-commerce store, place an order; perform a search; etc.
Open your site in different browsers and try the same things.
Check the debug log to see if something is reported there. Note: Things that occur in the theme or a plugin need to be addressed to its developer. Additional information about your environment and site setting is in the Site Health information. Check information for any sensitive data before publishing it in any forum or other public space.
Check Site Health to see if some issues were not present before. Note: depending on the message, the steps you should take can be quite different. For example, if you have a low 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. version (this issue should be present before testing the upcoming version) this can and should be changed on the hosting. So, for most of these issues, your hosting provider or a site developer will be the first person to go to.
If errors appear in the log, check the paths to where these issues occurred, and contact the theme/plugin developer, or ask in the Forums (or your local native language Forum). But firstly check if this is already reported by someone else. In our case, multiple reports are not making things more important but only creating additional work for contributors who are triaging tickets. And read the sticky post first to find out how to work and communicate in the Forums.
Data Views
Data Views is the new and improved experience of navigating and viewing information in the Site Editor as part of the groundwork for phase 3. This release focuses on bringing a new side by side layout, consolidating patterns and template part management, surfacing general management views sooner across the experience for easier access, and a wide range of refinements.
Testing instructions
Open Appearance > Editor and select Pages.
In this view, you’ll see the new layout called “list” that shows a side by side view.
Underneath “Add New Page” select the View Options icon.
Change the layout of the view by selecting “Layout” and explore changing other options, like sort by or what fields are displayed.
Click the back arrow to return to the overall Design section and select “Templates”.
Underneath the “Add New Template” select the View Options icon.
Change the layout of the view by selecting “Layout” and explore changing other options, like sort by or what fields are displayed.
Click the chevron back arrow to return to the overall Design section and select “Patterns”.
Explore creating new patterns and template parts before exploring how the two are presented in the same section. For example, view the “All template parts” and “All patterns”, try using different sorting options, and different layouts.
You can continue testing as you see fit by creating different types of content (patterns, template parts, templates, and pages in various states) and changing how that content is then displayed in each management section (Patterns, Templates, Pages).
Overrides in synced patterns
Building upon the power of synced patterns, overrides allow you to ensure a synced layout and style across patterns while enabling each instance of the pattern to have customized content. This provides consistency in design across different pieces of content. For instance, consider a user creating a ‘Recipe’ pattern. With the enhanced feature, the user can insert this pattern into multiple posts, ensuring that the layout and styling components, such as the overall design of the recipe card, remain consistent across instances. Meanwhile, the content, such as Ingredients and Steps, would be local to each post, allowing for individual customization. Additionally, folks would then be able to revisit and modify the design of the recipe pattern without affecting the content in existing instances.
Testing instructions
Create a synced pattern with overrides
Create a new post.
Insert a mixture of blocks that include paragraphs, headings, buttons, images, and optionally other blocks too.
Select the blocks, and ‘Create a pattern’ from the block options menu.
Give the pattern a name and make it ‘synced’.
Once the pattern has been created, note that the content is locked and uneditable.
Click the ‘Edit original’ button on the toolbar, this will take you into an isolated view for editing the pattern.
Select a paragraph block in the pattern, and in the block settings 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. expand the Advanced section. Check the ‘Enable overrides’ option and give the override a name.
Set overrides for a few blocks within the pattern, ideally including a heading, paragraph, button, and image block.
Click “Save” and then use the ‘Back’ button in the headerHeaderThe 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. area of the editor to go back to the post.
Editing the instances
Select the pattern and duplicate it from the block options menu.
Now click the paragraphs for which you checked ‘Enable overrides’ and notice you can edit them. The updates don’t sync across instances of the pattern; the changes are local to the pattern.
Click “Save” and confirm both Posts and Patterns are checked in the saving flowFlowFlow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it.
Flow is the actual user experience, in many ways. If you like, you can think of flow as a really comprehensive set of user stories. When you think about user flow, you’re thinking about exactly how a user will perform the tasks allowed by your product.Flow and Context
, and confirm Save.
View the post, the frontend should match the editor.
Add the pattern with overrides to another page
Create a new page and add the newly created pattern with overrides to it.
Make local changes to the pattern based on what blocks are able to be overridden.
Hit save when done.
Click the ‘Edit original’ button on the toolbar, this will take you into an isolated view for editing the pattern.
Remove override option
Select one of the blocks with overrides turned on and in the block settings sidebar expand the Advanced section.
Select “Disable overrides” and confirm your choice in the warning modal (read the modal and give feedback!).
Select save and use the ‘Back’ button in the header area of the editor to go back to the page.
Confirm you can no longer edit the previous override that was just disabled and that the content matches the original pattern once more.
Inserter shows all blocks
Previously, when selecting a block with the Inserter open, only the blocks that were allowed to be added to the selected block were shown often resulting in a confusing experience with an emptier than expected Inserter. With 6.6 when a block is selected, there’s now a list of blocks that can be inserted at the selected block, and a list with remaining blocks. This helps show both what’s allowed to be inserted within the selected block alongside the remaining blocks someone can still add. When you select a block outside of the allowed blocks, it’s inserted below the current block selection.
Testing instructions
Open Appearance > Editor to open the Site Editor.
Select Pages and “Add new page” to create a new page.
Open the Inserter and add a List block. Notice that all blocks should still appear below the List Item block that’s allowed.
Select the List Item block to add a list item.
Select a different block, like a heading, and ensure it is inserted below the list.
Try this process a few times adding different blocks, like a Buttons block or Quote block.
Unified and refreshed publish flow
The publish flows for both the post and site editor have been unified, bringing with it a new design and experience. Because publishing is such a critical part of the WordPress experience, it’s a key part to explore and find the edges of.
Testing instructions
Create a page in the Site Editor
Open Appearance > Editor to open the Site Editor.
Select Pages and “Add new page” to create a new page.
Add some content and publish the page by changing the options in Block Settings under Page.
Please test further by adding a 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., changing the author, changing the date, etc.
Create a post with the Post Editor
Open the command palette with either Cmd+k on Mac or Ctrl+k on Windows and type “Add new post” before selecting the option that matches.
This will take you to a new post in the Post Editor.
Repeat the process of adding some content and publishing.
Please test further by adding a featured image, changing the author, changing the date, adding categories, adding tags, setting an excerptExcerptAn excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox., etc.
You can continue testing as you see fit by going through the publish flow in each experience again, testing against different plugins, editing the template used, and exploring different post/page states (draft, pending, private, etc).
Create color OR typography only style variations [technical]
To build on the design possibilities of a block theme with style variations, 6.6 adds the ability to target color or typography only variations and offers them as presets, alongside style variations. These new color only and typography only presets offer narrower changes, making it easier to offer broader color and typography options out of the box without larger changes to the design. To use this new option, theme authors will need to create color or typography only variations, meaning variations that only contain changes to one or the other option. For any style variations that only contain color and typography only changes, these will now automatically appear in this separate preset flow.
Testing instructions
These testing instructions can only be followed if you are testing after the release of beta 2 as there are changes in place after the initial release in beta 1 in light of this discussion.
Create a new style variation that only contains changes to color OR typography settings and add this to your block theme under the same styles folder.
Head to Appearance > Editor and open Styles.
If you create a typography only variation, open Typography and you should see the variation under the heading “Presets” towards the bottom. If you create a color only variation, open Colors > Palette and you should see the preset available under “Palettes”.
Select your variation and ensure it updates as expected.
Save changes.
Section styles and changes to CSSCSSCSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. specificity [technical]
6.6 introduces the ability for theme authors to define style options for sections of multiple blocks, including inner blocks, that then appear in the Inspector in the same format as a block style variation. With just a few clicks, folks using block themes that add this functionality can quickly change just a section of a page or template to predefined styles that a theme author provides, like a light or dark version of a section.
Important note:
As part of this work, changes were made to limit the specificity of global styles CSS output to make overriding coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. styles easier and enable the extension of block style variations. This was accomplished by wrapping all the specificity leveled rules in :root. These changes keep specificity mostly the same across the board except for some of the more complex selectors for layout styles and block style variations. You can read the full breadth of the discussion here.
Testing instructions
Please try registering a few different section styles using one of the following methods. For examples of each, please review the PR that implemented this feature.
Programmatically via `wp_register_block_style()`
By standalone theme.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. partials within a theme’s /styles directory alongside a theme’s style variations.
Via theme style variations defining block style variations under styles.blocks.variations.
Grid layout
Grid is a new layout variation for the Group block that allows you to display the blocks within the group as a grid, offering new flexibility. There are two options for the Grid layout:
“Auto” generates the grid rows and columns automatically using a minimum width for each item.
“Manual” allows specifying the exact number of columns.
Within the experience, there’s also a visual resizer that matches the text color set for the blocks to ensure it’s easy to see and use.
Testing instructions
Open Appearance > Editor to open the Site Editor.
Select Pages and “Add new page” to create a new page.
Add a grid block.
Explore adding 3-5 blocks within the grid. For example, a set of headers or images or some combination.
Use the drag handles on an individual block to change the row and column span. Try this a few times!
Select the overall grid block and open block settings.
Under “Layout”, explore changing the various options between manual and auto, along with minimum column width.
Return the settings to auto and change the column span of a few of the items either by using the drag handles or through the block settings under Dimensions for each individual item.
Once done, use the preview option to preview the grid layout in different screen sizes to check whether the layout remains responsive.
Continue making changes: add new blocks, change the column and row span, transform into/out of grid, etc.
Note: The only responsive styles in place for Grid are when there are multi-column spans in auto mode which is why there are intentional steps to test this in steps 8 & 9.
New patterns experience for Classic themes
After adding easy access to patterns with a new Patterns tab under Appearance, Classic themes are slated to have access to the pattern experience baked into the Site Editor in this release. This will provide an upgraded, modern experience of managing and creating patterns, including all of the work that’s gone into data views.
Testing instructions
Create some patterns
Open Appearance > Editor to open the Site Editor.
Select Patterns and create a few patterns. As a tip to move quickly, you can always create a pattern and add in a current pattern from Inserter with a few customizations to make it your own.
Return to the admin dashboard by clicking the back chevron twice.
Switch to a Classic theme
Open Appearance > Themes.
Install and activate a Classic theme. For example, Twenty Twenty-One or Twenty Twenty.
After activating, open Appearance > Patterns. You should see a more confined Patterns experience matching what you’d find in the Site Editor.
Create a new pattern in this new experience and publish it. Ensure it shows up correctly.
Access new patterns page
Return to the admin dashboard by clicking the back chevron twice and create a new post under Posts > Add New.
Within this post, open the command palette with either Cmd+k on Mac or Ctrl+k on Windows and search for “Patterns”. Ensure it takes you to this new patterns experience.
Return to the post, open options and select “Manage patterns”. Ensure it takes you to this new patterns experience.
Return to the post, create or insert a synced pattern and, select the three dot menu in the block toolbar and choose “Manage patterns”. Ensure it takes you to this new patterns experience.
Negative margins
A long-requested feature has finally arrived: you can now set negative margin values. As a guardrail, this option can only be added manually to prevent people from accidentally adding negative values they didn’t intend using the slider control.
Testing instructions
Margin support is included on the following commonly used blocks: Group, Paragraph, Columns, Code, Cover, Separator, Spacer, Gallery. For a full list, please refer to this chart.
Open Page > Add New.
Open the Inserter > Patterns and add a few patterns.
Select or add blocks with margin support within those patterns.
Open block settings > open the styling section > head to Dimension settings.
In the margin controls, manually enter a negative number and try making a few changes.
Publish and view on the front end to ensure it matches the editor.
Repeat this process with more blocks!
Rollback Auto-Updates
To further protect websites and increase confidence in automatic plugin updates, 6.6 includes the ability to perform rollbacks when fatal errors occur during attempted plugin auto-updates by default. This allows you to enjoy the ease of auto-updates with the safety of rollbacks if anything goes wrong.
The 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/ update 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. will serve the version 0.2 version of the plugin, which will cause a PHP fatal error. To confirm a rollback is successful, data is written to the error.log at every point in the auto-update process, creating an audit trail the user can use to discern the flow and results of rolling back an auto-update. This logging is only intended for testing purposes.
Of note, any plugins or themes, other than the test plugin, should also update properly and only the active plugins will undergo the loopback testing.
What to notice:
Did the experience crash at any point?
Did the saving experience work properly?
What did you find particularly confusing or frustrating about the experience?
What did you especially enjoy or appreciate about the experience?
What would have made this experience easier for site building and for writing new content?
Did you find that what you created matched what you saw on your site?
Did it work using Keyboard only?
Did it work using a screen reader?
Did it work while using just a mobile device?
Where to report feedback
If you find any issues but aren’t sure if it’s a bug or where best to report the problem, share them on the WordPress.org alpha/beta forums. If you are confident that you found a bug in WordPress Alpha/Beta/RC, report it on Core Trac for rollback auto-updates and the Gutenberg GitHub repo for every other feature.
We are delighted to announce the publication of a new handbook page detailing the process for acquiring Test Team Profile Badges. The Test Team Badge serves as a recognition of your invaluable contributions to the WordPress testing team. Whether you’re an experienced tester or just beginning your journey with WordPress, these badges signify your commitment and expertise within the Test Team community.
You can find the new page added to the handbook section of Make WordPress Test site.
Test Contributor Badge
To earn the Test Contributor Badge, you must have completed one or more of the following tasks:
Submitted test reports for at least 1 ticket, comprising of testing instructions, issue reproduction, and/or patch testing. Acceptable reports should be submitted to TracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. or 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/, and can apply to any WordPress project area included in the Test Team duty of care.
Submitted unit or end-to-end tests that have been merged.
Contributed to a Test handbook PR that has been merged.
Participated in a Contributor Day as a Test table lead, providing technical support, or assisting with onboarding.
Suggested a thoughtful idea aimed at improving testing processes in any way, which gets implemented.
Test Team Badge
If you have served as a Test 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. or Test Lead in any 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. of WordPress, or have consistently made substantial contributions to the Test Team, you are eligible for the Test Team badge.
To request your badge, please follow the details available here.
Thank you for your dedication and commitment to making WordPress better for everyone. Your contributions are invaluable, and we look forward to celebrating your achievements with the Test Team Profile Badges!
You must be logged in to post a comment.