-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
all content arriving as single classic block, can't publish #516
Comments
@jshwlkr can you confirm whether Gutenberg is active on the site the content is being pulled from and if so whether that version matches the version on the site pulling content? |
This might also be related to #512, which there's an open PR for that we will merge in for a 2.0.0 release. |
@jshwlkr are you able to test the |
I can confirm the same version of Gutenberg is active on both sites. I've tried using |
I want to clarify this a little bit. The issue only happens with pulled posts of external connections. Look at the code below, we use distributor/includes/classes/ExternalConnections/WordPressExternalConnection.php Lines 914 to 917 in 6bd81f6
|
Describe the bug
Running three WP 5.3.2 sites (not multisite) locally via VVV, distributing content via pull seems to lump all content into a single classic editor block. The post is then unable to be published. If I edit the original post the content is added to the classic editor block in the distributed post.
Expected behavior
Blocks would remain intact in the distributed content and it would be publishable directly.
Environment information
Query Monitor 3.5.2
Application Passwords 0.1.1
The text was updated successfully, but these errors were encountered: