Common Issues
Common IssuesError parsing post

Error parsing post

If you receive a log error like this:

[Query "translate-customposts"] Execution with errors: πŸ”΄ Error parsing post ID 4957: This post does not appear to contain block content. This fields is designed to parse Gutenberg blocks and can not read classic editor content.

The solution depends on which editor you're using:

If using Gutenberg

If you're using the Gutenberg editor, this error indicates that the post content is corrupted.

To fix this:

  1. Edit the post in the WordPress editor
  2. Re-save the post with the correct Gutenberg format

If using Elementor or Bricks

If you're using a Page Builder like Elementor or Bricks, this error occurs because the plugin is trying to translate the post_content field, and that content does not follow the Gutenberg format.

Page Builders store their content in meta. Translating the post_content field is most likely not necessary (only in certain cases, such as when migrating a site from Gutenberg to Elementor, and the post content has not been migrated yet).

To fix this:

  1. Go to the Settings page, under Plugin Integration Configuration > [Page Builder] (Elementor or Bricks)
  2. Disable the option to translate the post_content field
Disabling the 'Translate content' option for Elementor
Disabling the 'Translate content' option for Elementor