Skip to content

Editor: Add admin notice for Gutenberg block markup in content#11960

Open
Infinite-Null wants to merge 7 commits into
WordPress:trunkfrom
Infinite-Null:feature/classic-editor-gutenberg-block-warning
Open

Editor: Add admin notice for Gutenberg block markup in content#11960
Infinite-Null wants to merge 7 commits into
WordPress:trunkfrom
Infinite-Null:feature/classic-editor-gutenberg-block-warning

Conversation

@Infinite-Null
Copy link
Copy Markdown

@Infinite-Null Infinite-Null commented May 25, 2026

https://core.trac.wordpress.org/ticket/65335

Summary

Adds a warning notice in the Classic Editor when the post content contains Gutenberg block markup (<!-- wp:). Since block markup is stored inside HTML comments, the Visual tab may appear empty even though content still exists.


Changes

  • Added a conditional check in edit-form-advanced.php that detects WordPress block syntax (<!-- wp:) in $post->post_content
  • Displays a dismissible warning admin notice using wp_admin_notice() when block markup is found
  • Notice is placed immediately before the <form> element so it is visible without interrupting the editing flow

Before / After

Before After
Screenshot 2026-05-26 at 11 54 58 AM Screenshot 2026-05-26 at 11 55 52 AM

Testing Instructions

  1. Create or open a post that contains Gutenberg block markup in its content:
<!-- wp:group {"layout":{"type":"constrained"}} -->
<div class="wp-block-group"> </div>
<!-- /wp:group -->
  1. Open the post in the Classic Editor.
  2. Verify that the warning notice appears above the editor form.
  3. Confirm the notice is dismissible.

@github-actions
Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@Infinite-Null Infinite-Null marked this pull request as ready for review May 26, 2026 06:34
@github-actions
Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props ankitkumarshah.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant