Looks like the latest update is forcing preview mode when editing patterns. We force edit mode on site, so this causes a different issue where an unstyled version of the front end code renders in the editor.
Is there an issue with the way Gutenberg uses an iframe in the pattern editor?
Also having this issue on all our client sites. Any word on a fix?
It seems to occur when starting the insert block process above an existing ACF block that contains a WYSIWYG in Visual mode, focus is dropped down to the next TINYMCE instance. Starting the insert block process below all ACF WYSIWYGs (or if the WYSIWYGs are in Text mode) does not shift focus.
I think the concept of translating existing flexible layout instances into block instances should be possible. Gutenberg blocks are stored in post content as HTML comments that conform to a consistent and predictable format, so editing/updating via PHP is certainly doable.
I think the challenge is how to actually implement the process. A few questions that come to mind: What happens if the user hasn’t yet converted all layouts in the source field to stand-alone auto blocks? Would we drop the new blocks at the beginning or end of any existing post content? Should the conversion be a post-by-post process for the user, or a global edit/update from a single admin screen?
I’m not sure how much time I’ll have to dedicate to a solution but would love to continue the conversation!
Looks like acf_get_field_id was removed at some point. I just pushed an update (1.0.5) that will resolve the issue.
A quick note: You probably don’t want to enable auto blocks in the field group that contains the source flexible content field. Those settings will be added when creating a new field group from the layout.
