Problem/Motivation

First off, thanks for the awesome module. This solves part of a big problem, but I'm still running into the issue that the "Your site doesn't support the 'undefined' block..." still shows and the "Keep HTML" button breaks the content entirely.

The content that is coming from a body field on an ECK entity is there in the Gutenberg editor, and it shows formatted HTML which it didn't do before enabling this module, but is still greyed out and un-editable.

In my case, I need this to be totally user-friendly as regular website users will use it. I hoped this module would convert a node's body to a ready-to-use Gutenberg block. Am I missing something or is this a bug in the module?

Thanks!

Comments

AlfTheCat created an issue.

isalmanhaider’s picture

isalmanhaider commented

@AlfTheCat

Could you please provide the HTML code sample?
I would like to try replicating it on my local environment in order to identify and resolve the issue.

alfthecat’s picture

alfthecat commented

Thanks for the quick reply, based on you answer I figured out the ECA action wasn't firing. Creating the action in Drupal and then triggering it with ECA works much better. The only issue now is that initially, when viewing the node the body shows as:

<!-- wp:heading {"level":2} --><h2>This is a heading</h2><!-- /wp:heading --><!-- wp:paragraph --><p><strong>This is a strong text</strong></p><!-- /wp:paragraph -->

After manually re-saving the node makes the body show correctly in the front-end. Programmatically saving the node doesn't. Is there a way to remedy this for a completely consistent UX?

Thanks again!