Recognize the message and define the problem
In the editor, a notice reports that a block contains unexpected or invalid content. The text or image sometimes remains visible on the public site while this block becomes difficult to edit. The desired result is not merely closing the warning: you need complete, editable content that saves correctly.
For some blocks, WordPress compares the saved structure with the structure the block can produce. A difference can trigger validation: a manual HTML edit, an unusual paste, or a change to the component providing the block. HTML is the markup that describes page elements. This message does not, by itself, demonstrate database corruption.
Do not confuse this situation with an invalid JSON response when saving. That other error concerns communication with the server. If it also appears, preserve your work and have the second issue handled separately. An unavailable block, a lock, and a JavaScript runtime error also require separate diagnoses.
Keep a copy before attempting recovery
Prerequisites: retain access to the original document and prepare a local text file and a separate draft. This copy protects the content during tests; it does not replace a site backup.
- Leave the original tab open. In the editor’s main menu, look for the command to copy all content, then paste the result into the local file. Check the beginning, end, and affected part before considering the copy usable.
- If copying everything fails, select the affected block and look for Copy in its three-dot menu. Separately preserve accessible text, media URLs, and a screenshot of the layout. A screenshot helps reconstruct appearance, but retains neither interactive settings nor block structure.
- In Posts or Pages, use Add New to create a working draft. Paste the content there and verify that you are in this new document before testing. Do not publish it: visitors should continue viewing the original version. Media and components are still shared with the site.
- Keep the initial file without replacing it with a conversion result. Give test versions separate names. You must be able to return to the initial text even if the draft becomes unusable; editor undo must not be your only protection.
- Before updating a plugin or making a broader intervention, have the database and file backups and restoration procedure confirmed. If that protection is missing, stop component changes: the text copy could not restore a plugin or configuration.
Check access and the block’s scope
You need permission to edit the affected content; plugin operations require other permissions. Record the WordPress version, theme, block name, and change preceding the error. Also state whether you use self-hosted WordPress, WordPress.com, or a multisite network. Hosting access and available menus are not interchangeable.
Open List View from Document Overview at the top of the editor. Expand the group containing the block and locate it precisely. Selecting the entire group instead of a paragraph may result in a much wider conversion than intended.
Finally, check whether this content belongs to a synced pattern, formerly called a reusable block. Editing its original may affect every use. Copying a page does not necessarily remove that relationship. For a local test, detach it when the option is available and you are authorized; otherwise ask the responsible person to intervene before proceeding.
Choose between the three approaches
Start with targeted recovery if one isolated block displays the message after its content was changed. The goal is to compare a limited correction with your copy without touching the rest of the document.
Choose revisions if you know a correct version was previously saved and want to recover that content. This is particularly useful when recovery removes important elements. It does not automatically repair a component that has become incompatible.
Move to third-party block diagnosis if several old documents deteriorate after an update, or the block depends on a missing plugin. In that case, repeating a conversion on every page may hide the cause and lose functionality. None of these paths requires installing a new troubleshooting plugin.
Approach 1: attempt recovery on the copy
Prerequisites: use the separate draft and verified external copy. This approach suits an isolated block whose provider is still available. The expected result is complete content that remains editable after saving.
- Open the draft’s List View, select only the affected block, and verify its location. Avoid selecting the group or the whole page: satisfactory recovery of a paragraph proves nothing about a gallery or a commercial block.
- In the warning, click the recovery button once, often labeled Attempt Recovery or Tenter la récupération depending on language and version. Immediately compare the result with the initial file and saved screenshot.
- Check words, links, images, and useful presentation settings. Recovery may remove unrecognized markup. If anything is missing, use Undo before multiplying attempts; if you cannot recover the desired state, start again from the initial copy in the draft.
- If the content seems complete, save the draft, leave its editor, and reopen it. Check that the block remains editable and the warning does not return. This tests saved content rather than only the editor’s momentary display.
- Record the result: correction retained or error returned, immediately, after saving, or after reopening. If the test fails, leave the original untouched and compare a conversion or revision in the following sections. Do not repeat the same recovery on every page.
Compare a conversion without sacrificing content
If recovery is unsuitable, open the warning’s three-dot menu. When Resolve is offered, inspect the comparison between existing content and the expected version. Identify the proposed removals before choosing conversion to blocks. If you do not understand the differences, leave the comparison without accepting the transformation.
Converting to Custom HTML is another possibility, especially to preserve a markup fragment for inspection. It does not restore the original block’s settings. This choice better suits someone able to check HTML; for a beginner, rebuilding a simple paragraph in a native block may be easier to maintain.
Do not paste unknown code to make the error disappear. Some HTML elements may be filtered on saving depending on permissions and the environment. A correct preview before saving is not enough. Do not request broader permissions or disabled filtering to bypass this protection.
Stay on the copy during this comparison. If conversion removes text, changes links, or replaces content with an empty block, stop that approach and use the preserved original for reconstruction or revision recovery.
When to use the Classic block or rebuild the block
Some interfaces offer conversion to a Classic block. This is a block built into the block editor, with tools similar to the old editor; it is not an invitation to install the Classic Editor plugin or change the editor for the entire site.
Try this conversion only on the copy, if available. Verify what it preserves before another transformation. Subsequently converting Classic content to multiple blocks is another conversion: do not automatically chain it into the diagnostic process.
For simple content, you can instead add a Paragraph, Heading, or Image block beside the faulty block. Reenter the text without its problematic formatting, recreate links, and select images from the Media Library. Compare both versions before removing the faulty instance from the copy. If this reconstruction remains correct after reopening, you have a targeted repair to transfer, not a reason to rebuild the whole page.
Approach 2: find a usable version in revisions
Prerequisites: a version saved before the error must exist, and your account must have access to the history. Preserve the current state outside WordPress; a full restore may replace recent changes and immediately alter a published page.
- In the original document, open settings, then the Post or Page tab and Revisions. Depending on the version, inspect the visual preview or the HTML content comparison. Confirm the document title before browsing dates.
- Select a version from before the problem appeared without clicking Restore. Identify the author, time, and useful passage. An autosave is not an unlimited history; do not promise recovery of text that was never retained.
- Also compare recent changes elsewhere on the page that need to be kept. Prefer extracting only the required block, using the method in the next section. On WordPress.com, Restore may directly reinstate that version on the public site: have the person responsible for publication decide on a full restore.
- Leave history without a full restore until the choice is validated. This search should produce an identifiable version and an agreed recovery scope. If no state is useful, or your permissions do not allow history access, report that limitation to an authorized editor.
- Then check the recovered fragment in the draft. If you selected the wrong passage, discard that copy and repeat extraction from the preserved state. If the same block becomes invalid after reopening, move to component diagnosis; restoring multiple dates does not fix its incompatibility.
Recover part of the content without restoring the whole page
Where visual history lets you select blocks, copy the useful part from the revision, then leave history without a full restore. Paste the content into your working draft and check it. This method is documented on WordPress.com; do not assume that every older interface has the same commands.
If only an HTML comparison is available, use it to identify the passage you need. Do not copy a rough selection that cuts through block boundaries or leaves an incomplete group. If necessary, have a knowledgeable person extract the fragment correctly, or rebuild simple content from the recovered text.
Save and reopen the recovered copy. If the same block becomes invalid again, the older content version is not sufficient: the problem may lie in the component’s current version. Move to the third approach rather than successively restoring multiple dates on the public page.
Approach 3: identify the component providing the third-party block
Prerequisites: record the versions and block name; plugin changes require an authorized administrator. A third-party block comes from a plugin or theme. This path identifies its provider before any conversion or migration.
- In the warning and List View, record the block name and technical identifier where displayed. Keep a minimal example without private data. Have the administrator match the name to installed components, without randomly installing a replacement plugin.
- Distinguish a present block whose old content no longer validates from a block described as unsupported. In the first case, record the provider version and recent updates; in the second, check whether the provider is deactivated, missing, or unavailable in this context.
- Keep missing blocks during the inventory. Conversion to HTML may preserve some content but does not restore their functions. On multisite, ask the network manager to check components managed at that level. On WordPress.com, use the available access or service support.
- The expected result is an identified provider and a precise hypothesis to test on a separate copy, as described next. If identification remains uncertain, stop editing and send the block name with the versions. This read-only inventory needs no rollback; preserve the original before the following tests.
Verify an incompatibility before migrating
Prerequisites: have a staging environment prepared with its own database, a backup, and live payments, notifications, and messages disabled. Mere timing between an update and the error does not prove the cause.
- Consult the provider’s documentation and release notes for the exact block. Record the suspected change and choose a representative page. Verify that the error reproduces on this copy before touching the component.
- With the maintainer, change one element at a time on staging. Keep its initial version and configuration, along with the restoration procedure, then reopen the same content. Do not globally deactivate plugins in production.
- Compare content and functions after testing, then restore the previous configuration before changing hypotheses. If the provider changed the saved format, send the minimal example: compatibility with older blocks belongs in its documented migration.
- Stop if the copy does not reproduce the issue or you cannot restore its starting state. Do not modify provider files to improvise a migration, and do not retain an older version indefinitely without reviewing security and compatibility. A confirmed cause lets you choose a correction, not immediately generalize the change.
Migrate to maintained blocks when necessary
If the component is abandoned or its provider recommends migration, first establish what each block does. Text and an image can often be rebuilt with existing blocks. A form, search feature, or calculated display needs a functional replacement, not merely a copy of its appearance.
Some blocks generate their output on the server. Their saved content may not include the complete final rendering; retaining HTML therefore guarantees neither functionality nor even the presence of all information. Have the solution validated for the relevant block type before removing its provider.
On the copy, add the replacement alongside the old instance, reenter useful data, and check functions. Remove the old block only after comparison and backup. For multiple pages, start with one representative instance and keep a list of content to revise. A successful migration is measured by retained uses, not the number of warnings removed.
Validate the repair before changing the public page
Reopen the draft after saving. Check that the block remains editable and the message does not return. Then open its preview on a wide and a narrow screen. Check headings, alternative text, element order, links, and content hidden behind an accordion or tab.
For an interactive element, define a test with no real-world effect. Seeing a form’s fields does not prove it processes responses; conversely, do not send messages to real recipients to test a copy. Have an appropriate environment prepared if an important function needs validation.
Once the result is approved, transfer only the necessary correction to the original content using the required permissions. Before saving an already published page, compare the list of changed elements and avoid simultaneous edits by another author. Then check the public page and reopen the editor. Keep the copies until both checks pass.
Know when to stop and request targeted help
Stop conversions when content disappears, an essential function is lost, or multiple blocks return to an error state. Send the case to the block developer for a specific incompatibility; ask the host for a backup, staging environment, or server-side error investigation. On WordPress.com, support can guide service-specific checks.
Provide the exact message, versions, block name, reproduction steps, and result of a single documented test. Remove personal data, private commercial information, and authentication values from example content. Do not publish a complete export of a confidential page on a forum.
To prevent recurrence, keep a backup before component changes and check representative pages after updating. Avoid manually changing HTML structure in blocks you want to continue editing visually. The repair is complete when useful content and its functions are preserved, not merely when the error notice disappears.
Understand a Paragraph block through its markup
In a disposable draft, a simple paragraph may be saved in the form below. The comments delimit the block; the text between the p tags is its content. This fragment explains the structure; it is not intended to replace a complete page’s code.
If someone manually replaces the p tags with div tags while keeping the wp:paragraph declaration, the output may still look like text, but the structure no longer necessarily matches what the Paragraph block can save. The right repair is to rebuild that paragraph alone with its text and links, then save and reopen the draft. Removing comments to suppress the warning would change the nature of the content rather than repair the block.
For a third-party block, do not generalize this tag replacement: its code may require particular classes, attributes, or inner blocks. The developer must maintain support for reading older formats with a deprecation and, where necessary, an appropriate migration. A useful check includes old content, new content, and reopening after saving, without losing expected attributes.
<!-- wp:paragraph -->
<p>Texte de démonstration conservé.</p>
<!-- /wp:paragraph -->Sources and references
Use these references to check the features, requirements and limitations described. Reading documentation is not a practical test.
View 17 references
- WordPress: unexpected or invalid block content ↗
- WordPress.com: resolving block errors ↗
- WordPress: validating saved block content ↗
- WordPress: block editor workspace ↗
- WordPress: copying blocks and block options ↗
- WordPress: Custom HTML block ↗
- WordPress: Classic block ↗
- WordPress: revisions ↗
- WordPress.com: restoring a revision or part of its content ↗
- WordPress: List View ↗
- WordPress: synced patterns and detaching them ↗
- WordPress: compatibility with older block versions ↗
- WordPress: static and dynamic blocks ↗
- WordPress: blocks that have become unavailable ↗
- WordPress: backing up the database ↗
- WordPress: roles and capabilities ↗
- WordPress.com: troubleshooting plugins and themes ↗


