January 10, 2023, 6:59am
Saw in Gutenberg’s latest release (
Release 14.9.0 · WordPress/gutenberg · GitHub) that they’re finally bringing the iFrame editor to posts and pages.
Post editor: Iframe for block-based themes. (
It’s been the default editor in FSE, and they’ve been wanting to migrate it to posts/pages for a couple of years now.
Among other things, this will make switching between desktop and mobile breakpoints a lot more snappy, and will make it easier to see which element you have currently selected.
I’m sure it’ll also simplify a lot of CSS issues.
It should make it into WP 6.2, which is scheduled to be released at the end of March.
January 10, 2023, 3:35pm
You must be very good at noticing things. I had read the same changelog but missed such a major change. Very productive change for every body.
Yes - this should be a great change. Really like the resize handles of the FSE editor version for moving between breakpoints.
January 10, 2023, 9:45pm
Hah, I think I just got lucky. I saw that there was an update, and I’ve been looking forward to that one change for a few months now.
Just a quick follow up on this:
08:54PM - 07 Feb 23 UTC
I just started testing WP 6.2 beta1. Right away:
1. The ACF Blocks in Edit mo
… de are broken, the Preview mode is ok.
2. This is not new, but I don't think anyone has mentioned it before, the same thing as issue 1 happens with the Site Editor, with 2 distinctions: The first one is that the Edit mode button never shows up, BUT, in the inspector (right sidebar), the columns set in the Field group do not break into a single column, which makes things very difficult. My so far solution was to configure my ACF Blocks in a temp. page, and then simply copy them to the Site Editor.
3. **Side note: This is not related to ACF PRO**, but I'm finding that many other plugins and themes are getting broken with just 10 minutes of testing: The Wayfinder plugin no longer works, as a backup I had the Block Guide Lines to use from the EditorsKit plugin, both of these solutions no longer work, so I'm left with the white space to guess where to click to select an element, of course we have the breadcrumbs and the block Navigation menus. Also there are things that are breaking my FSE theme, like I no longer have a Sticky header, instead I have some extra paddings. Disabling the Sticky header option the extra padding seem under control, but I have to come up with a new sticky header solution. The bottom line for the 3rd point is that test all your plugins and themes that you use...
08:48AM - 24 Jan 23 UTC
I've noticed this merge from [https://github.com/WordPress/gute
… nberg/pull/46212](https://github.com/WordPress/gutenberg/pull/46212). But with the latest Gutenberg plugin I have no iframe in the post editor.
You mentioned several times that switching to iframe could cause issues with ACF. So I wanted to ask if you know anything about this possible change?
It seems that the iframe will only be present if all blocks in the library use the v3 api.
@Louis, where does Cwicly stand in this regard?
March 16, 2023, 5:33pm
This has been a tricky one to understand, and it still isn’t really clear what’s happening.
I’m a bit disappointed about the fact they haven’t been more consistent with their decision on this one.
From my understanding, the iFrame will only be reserved with the Gutenberg plugin active, looking at
Post editor: revert iframed editor for WP core only (#48076) · WordPress/gutenberg@8a24a11 · GitHub
Yes, it appears this is another case of the grasp exceeding the reach… we were looking forward to this in WP 6.2 for a smoother more consistent editing experience for our clients.
Currently the 2 restrictions that make a difference are not being able to use metaboxes and requiring the Gutenberg plugin. It seems that will limit it from being used in a lot of cases in the short term.
Hopefully things will become clearer in time.
March 16, 2023, 5:54pm
Hmm, didn’t know about that.
Was kind of confused when testing the beta but now it makes sense.
Their statement reads for me like WordPress is kind of a hobby project.
I understand their decision though and my take on this is that it will be (likely) a thing in v6.3?
Still, it’s bad news, as it will affect the development (plans) of Cwicly in some way, if I’m not mistaken.
Thanks for the share