AdvancedCustomFields / AdvancedCustomFields/acf

Custom ACF Meta Box on post type blocks loading of WP 7.0 visual revisions editor

Open
#1,015 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
945
Forks
197
PR merge metrics
No merged PRs in 30d

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
  1. Ensure a custom post type is set up and a field group (ACF) is assigned to it.
  2. Create or edit a post under this custom post type.
  3. Save or edit the post, ensuring the custom ACF meta box is visible in the editor/sidebar.
  4. Attempt to view or interact with the revisions panel/editor for that post.
  5. Result: The system loads the legacy (old) revision editor, failing to utilize the new visual revision mode.
  6. 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)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
php
Domain
web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.