Describe the bug
When a custom meta box, implemented using Advanced Custom Fields (ACF), is added to a specific post type, the system fails to load the modern, visual revisions editor introduced or improved in WordPress 7.0. Instead, the editor falls back to the older, non-visual revision interface. This behavior prevents users from utilizing the new revision features and workflow intended in WP 7.0.
To Reproduce
- Ensure a custom post type is set up and a field group (ACF) is assigned to it.
- Create or edit a post under this custom post type.
- Save or edit the post, ensuring the custom ACF meta box is visible in the editor/sidebar.
- Attempt to view or interact with the revisions panel/editor for that post.
- Result: The system loads the legacy (old) revision editor, failing to utilize the new visual revision mode.
- Verification: Remove the ACF field group entirely from this post type. Repeat Step 4. The new visual revision editor loads correctly.
Expected behavior
The new, visual revisions editor (designed for improved collaboration and history viewing in WordPress 7.0) should load successfully and be fully functional, even when a custom ACF meta box is present and properly configured on the post type.
Version Information:
- WordPress Version: 7.0
- PHP Version: 8.3.23
- ACF Version: ACF Pro 6.8.2
- Browser: Chrome on Mac OS
Additional context
This issue seems to be a direct conflict between the meta box structure and the modern, collaborative/visual editing environment that WordPress 7.0 is moving towards.
It is worth noting the official WordPress developer warning regarding this exact behavior:
"Classic meta boxes will disable collaboration mode". Source: Wordpress
(Source: WordPress 7.0 News and Updates)
Describe the bug
When a custom meta box, implemented using Advanced Custom Fields (ACF), is added to a specific post type, the system fails to load the modern, visual revisions editor introduced or improved in WordPress 7.0. Instead, the editor falls back to the older, non-visual revision interface. This behavior prevents users from utilizing the new revision features and workflow intended in WP 7.0.
To Reproduce
Expected behavior
The new, visual revisions editor (designed for improved collaboration and history viewing in WordPress 7.0) should load successfully and be fully functional, even when a custom ACF meta box is present and properly configured on the post type.
Version Information:
Additional context
This issue seems to be a direct conflict between the meta box structure and the modern, collaborative/visual editing environment that WordPress 7.0 is moving towards.
It is worth noting the official WordPress developer warning regarding this exact behavior: