search

AdvancedCustomFields / acf

Advanced Custom Fields
http://advancedcustomfields.com/
832 stars 169 forks source link

Standard Gutenberg Blocks not showing in Preview when ACF is installed #118

Open jweston491 opened 5 years ago

jweston491 commented 5 years ago

When adding/updating vanilla Gutenberg blocks, the blocks are not updated when previewing the page. I have to update the page to see the Gutenberg changes reflected. This only occurs when a page is already published. Pages set to Draft appear to work as expected.

I am currently using an ACF Group field which is set as a meta box (not as a Gutenberg block) to the front page.

When uninstalling ACF OR removing the ACF meta boxes from the page, preview works as expected when a page is currently published.

Note: Previewing the front-end display of the ACF fields works as expected, it is just vanilla Gutenberg block content that is not updated in preview.

elliotcondon commented 5 years ago

Hi @jweston491

Thanks for the bug report. I'll add this to our to-do list and will perform some testing shorty.

elliotcondon commented 5 years ago

Hi @jweston491

I've just done some testing and can confirm the issue. It looks like if any metabox exists on the edit page, WP is unable to preview the content. This issue is not just related to ACF, but can be replicated with any plugin that adds a metabox such as Yoast SEO.

Would you mind contacting the Gutenberg developers or WP core to notify them of the issue?

jweston491 commented 5 years ago

Thanks @elliotcondon

Looks like this issue has had pretty hefty discussion the past few days over on https://github.com/WordPress/gutenberg/issues/12617

I added my issue description there.

elliotcondon commented 5 years ago

@jweston491 Thanks for the link. Let's hope that WP fix it soon.

designsimply commented 5 years ago

This is something being worked on in https://github.com/WordPress/gutenberg/issues/12617 and https://core.trac.wordpress.org/ticket/46076. There is an additional report which may be a simultaneous or underlying bug being tracked in https://github.com/WordPress/gutenberg/issues/13232 where the same problem happens when no metaboxes are in use.

Thank you for the report @jweston491 and for testing!

jweston491 commented 5 years ago

This appears to be no longer happening with the current version of the standalone Gutenberg plugin (though still persisting with Core)