Subject: Field group hidden behind collapsed panel when creating new post (WordPress 7.0.2) — suspected iframed post editor issue
Hi Toolset team,
I'm running into an issue on a live site that does not occur on an older clone of the same site. The difference between the two environments strongly points to the new "always-iframed" post editor introduced in WordPress 7.0.
WHAT I EXPECT TO SEE
When creating a new "woongroep" post (custom post type), both the Title field AND the assigned Toolset field group should be visible and directly usable in the post editor, as they are on my clone site.
WHAT ACTUALLY HAPPENS (on the live site only)
When adding a new woongroep post, only the Title field appears. A Stackable block is automatically present, and the Toolset field group is technically there but collapsed/hidden — I have to click a small arrow in the bottom-right corner to expand it. Once expanded, all fields are editable, but then the Title field is no longer visible on screen. Both cannot be shown/used at the same time.
REPRODUCTION
Live site: hidden link
Example post showing the problem: hidden link (draft, "Test woongroep 20-07-2026")
Preview link: hidden link
Working clone (same site, older core/plugin versions): hidden link
ENVIRONMENT COMPARISON
Live site (broken):
- WordPress: 7.0.2
- Toolset Blocks: 1.6.26
- Toolset Maps: 2.2.4
- Toolset Types: 3.6.2
- Stackable: 3.19.9
- Theme: Blocksy 2.1.49
Clone (working correctly):
- WordPress: 6.9.5
- Blocksy Companion (Premium): 2.1.25
- Toolset Blocks: 1.6.21
- Toolset Maps: 2.2.1
- Toolset Types: 3.6.1
- Stackable: 3.19.10
Note that Stackable is actually newer on the working clone than on the broken live site, which makes Stackable an unlikely root cause on its own. The clearest differentiator between the two environments is the WordPress core version: 6.9.5 vs. 7.0.2.
WHY I SUSPECT THE WP 7.0 IFRAMED EDITOR
WordPress 7.0 changed the post editor to run inside an iframe whenever all blocks actually inserted into the post content use Block API version 3 (previously, any classic meta box present would keep the editor out of the iframe). Toolset field groups are rendered as classic meta boxes. If the Stackable block auto-inserted into this post type uses apiVersion 3, the iframe would now be enforced where it previously wasn't on WP 6.9.x — which matches the exact symptom of the Toolset meta box no longer rendering/expanding correctly alongside the title field.
I have Toolset licensed as a lifetime unlimited subscription and would appreciate help confirming whether this is a known compatibility gap with WordPress 7.0's always-iframed editor, and whether a fix or workaround is planned.
Happy to provide temporary admin access if that helps with debugging.
Thanks in advance,
Winy