You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Legacy posts that use Classic Editor instead of Gutenberg Blocks are returning content and not falling back to Freeform block.
See attached images below
Here is an imported legacy post using Classic Editor:
Here is the gql query returning the post content but an empty block for freeform with no content:
Expected behavior is to have the classic content html be returned as freeform content.
The text was updated successfully, but these errors were encountered:
@dChiamp I investigated the case, but it works fine on my side. I guess the classic block is empty and that's why the content field is empty.
I did some tests on my side and it works fine.
Legacy posts that use Classic Editor instead of Gutenberg Blocks are returning
content
and not falling back toFreeform
block.See attached images below
Here is an imported legacy post using Classic Editor:
Here is the gql query returning the post
content
but an empty block for freeform with nocontent
:Expected behavior is to have the classic
content
html be returned asfreeform
content.The text was updated successfully, but these errors were encountered: