Skip to content

Fix/block editor integration#22886

Merged
JorPV merged 2 commits intotrunkfrom
fix/block-editor-integration
Jan 14, 2026
Merged

Fix/block editor integration#22886
JorPV merged 2 commits intotrunkfrom
fix/block-editor-integration

Conversation

@enricobattocchi
Copy link
Copy Markdown
Member

@enricobattocchi enricobattocchi commented Jan 13, 2026

Context

Summary

This PR can be summarized in the following changelog entry:

  • Improves the code for the block editor integration.

Relevant technical choices:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

  • Edit a post
  • check that the metabox is rendered correctly and there is no error in the JS console

Relevant test scenarios

  • Changes should be tested with the browser console open
  • Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
  • Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
  • Changes should be tested on different browsers
  • Changes should be tested on multisite

Test instructions for QA when the code is in the RC

  • QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

Other environments

  • This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.
  • This PR also affects Yoast SEO for Google Docs. I have added a changelog entry starting with [yoast-doc-extension], added test instructions for Yoast SEO for Google Docs and attached the Google Docs Add-on label to this PR.

Documentation

  • I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

  • I have tested this code to the best of my abilities.
  • During testing, I had activated all plugins that Yoast SEO provides integrations for.
  • I have added unit tests to verify the code works as intended.
  • If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
  • I have written this PR in accordance with my team's definition of done.
  • I have checked that the base branch is correctly set.
  • I have run grunt build:images and commited the results, if my PR introduces new images or SVGs.

Innovation

  • No innovation project is applicable for this PR.
  • This PR falls under an innovation project. I have attached the innovation label.
  • I have added my hours to the WBSO document.

Fixes #

@enricobattocchi enricobattocchi added the changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog label Jan 13, 2026
@coveralls
Copy link
Copy Markdown

Pull Request Test Coverage Report for Build f3112efe224e778803d09bf63e630ecef07a21fe

Details

  • 0 of 2 (0.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.5%) to 53.35%

Changes Missing Coverage Covered Lines Changed/Added Lines %
packages/js/src/initializers/block-editor-integration.js 0 2 0.0%
Totals Coverage Status
Change from base Build 6804bce2387b8414f0332f167d8bf0f1da684779: 0.5%
Covered Lines: 32901
Relevant Lines: 61853

💛 - Coveralls

@JorPV JorPV requested a review from Copilot January 13, 2026 16:54
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves the block editor integration by removing legacy compatibility code and enhancing error handling. The changes simplify the code that manages the initial opening of the Yoast SEO document panel in the WordPress block editor.

Changes:

  • Removed legacy code path for WordPress versions prior to 6.5
  • Added null check to prevent errors when openPanels is undefined
  • Simplified the logic to use only the current WordPress API

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread packages/js/src/initializers/block-editor-integration.js
const openPanels = select( "core/preferences" )?.get( "core", "openPanels" );

if ( ! openPanels.includes( PANEL_NAME ) ) {
if ( openPanels && ! openPanels.includes( PANEL_NAME ) ) {
Copy link
Copy Markdown
Contributor

@JorPV JorPV Jan 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a safe Array.isArray() to handle the case where the preference might not be an array (they can be of any type)? 🤔 Or is it over-cautious?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's needed, for this preference it's assumed to be an Array and the editor would probably break before us

@JorPV
Copy link
Copy Markdown
Contributor

JorPV commented Jan 14, 2026

CR + AT ✅

@JorPV JorPV merged commit cb3129b into trunk Jan 14, 2026
23 checks passed
@JorPV JorPV deleted the fix/block-editor-integration branch January 14, 2026 08:11
@enricobattocchi enricobattocchi added this to the 26.9 milestone Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants