Gutenberg Block Recovery

TranslateSense Gutenberg Block Recovery helps you identify and address supported Gutenberg block issues that may occur after translating WordPress posts and pages. A block may become invalid when its saved markup no longer matches the markup generated from its attributes and registered block implementation.

This section explains why these issues occur, how to use the recovery workflow, and how to reduce the risk of recurring problems by storing translatable content correctly instead of relying on language-specific default values.

What causes Gutenberg block issues?

Gutenberg blocks use registered attributes, saved HTML, and block-specific rendering logic to represent their content. Some blocks also rely on default attribute values when a value is not explicitly saved. If translated content and the values used to reconstruct the block become inconsistent, Gutenberg may report an invalid block or display unexpected content.

  • Invalid saved markup: The HTML saved in the post no longer matches the markup generated by the block’s current save implementation.
  • Default attribute values: A block relies on a registered default instead of storing its translatable content explicitly.
  • Attribute source mismatches: A block reads an attribute from an HTML element or attribute that does not contain the expected value.
  • Block implementation changes: A plugin or theme update changes the block’s schema or saved markup.

Gutenberg Block Recovery guides

Recommended workflow

  1. Open the translated post in the Gutenberg editor.
  2. Allow TranslateSense to scan for supported block recovery issues when recovery is pending.
  3. Review the detected blocks and available repair candidates.
  4. Use Apply Repairs when an appropriate repair is available.
  5. Verify the repaired content and investigate any unresolved issues.
  6. For recurring issues, inspect the block’s attribute definitions, saved markup, and default values before translating the content again.

Block recovery can help with supported issues, but not every custom, dynamic, or third-party block can be repaired automatically. Always verify important content and layouts after applying repairs.

Screenshot to add: [TranslateSense Gutenberg Block Recovery prompt and editor sidebar]