Custom ACF Meta Box on post type blocks loading of WP 7.0 visual revisions editor
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start by reproducing the issue with WordPress 7.0, ACF Pro 6.8.2, and a custom post type with an assigned field group. Compare the revisions editor with the ACF field group present and removed; done means the visual revisions editor loads and remains functional when the custom meta box is present.
Written by the indexing model from the issue text.
Description
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)
- Dominant language
- PHP
- Stars
- 947
- Forks
- 198
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AdvancedCustomFields/acf
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AdvancedCustomFields/acf#1056 ·
-
PHP 8.5: "Using null as an array offset" deprecation in ACF_Data::is() when rendering a block with empty data (local-meta.php is_request)Possibly taken @faisalahammad claimed this 30 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AdvancedCustomFields/acf#1044 ·
-
is_preview was called incorrectly notice on every early get_field() since 6.8.10 (acf_revisions::acf_validate_post_id)Possibly taken @faisalahammad claimed this 30 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AdvancedCustomFields/acf#1041 · 1 comment ·
-
True / False ACF control bug on RTL layoutsPossibly taken @elicohenator claimed this 53 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
AdvancedCustomFields/acf#1038 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AdvancedCustomFields/acf#1034 · 3 comments ·
All issues in AdvancedCustomFields/acf
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[Sync EN] Formatting improvements to "Large Objects (LOBs)" docs (#6056)Possibly taken A pull request linked to this issue is open or already merged. Opensync-en
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Перевод устарел
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
repo:cms
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
craftcms/cms#20613 · 1 comment ·
Maintainers usually reply within 1 day