Breaks Site Editor (Full Site Editing (FSE)) (page content)

  • Resolved strarsis

    (@strarsis)


    2 years, 1 month ago

    The plugin removes the core/ Gutenberg block registrations of post-related blocks.

    That’s fine and intended, however, the Site Editor used for Full Site Editing (FSE) uses the core/post-content for any type of post type, including pages (which are basically also posts). With the blog features disabled, that core/post-content block is also un-registered, which results in an error in the Site Editor (Your site doesn’t include support for the "core/post-content" block. You can leave this block intact, convert its content to a Custom HTML block, or remove it entirely.).

    The page contents still load on site frontend, but the editor error and missing preview in Site Editor are both issues that needs fixing.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Hey @strarsis thanks for reporting this!

    I’ll have a fix for this in the next release, but in the meantime you can stop Disable Blog from removing blocks by adding the following line to your functions.php file or a custom plugin, or revert to version 0.5.0 of the plugin (this was just introduced in v0.5.1)

    add_filter( 'dwpb_disabled_blocks', '__return_false' );

    Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Just a follow up to note that version 0.5.2 reverts the block editor functionality introduced in 0.5.1, this filter is no longer exists and the block editor issues should be resolved with the new version.

    I’m going to close this topic, but if you are still encountering issues please feel free to re-open or reach out with a new issue.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Breaks Site Editor (Full Site Editing (FSE)) (page content)’ is closed to new replies.