AdvancedCustomFields / AdvancedCustomFields/acf

Gutenberg editor shows unsaved changes prompt without any changes (ACF 6.6 + Blocks v3)

Open
#985 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
Since updating to ACF 6.6 and my blocks to version 3, the Gutenberg editor incorrectly prompts about unsaved changes after loading a post/page with ACF blocks in it, and then navigating away or refreshing, even when no modifications have been made. Pages with just regular JS blocks do not prompt about unsaved changes when navigating away.

To Reproduce

  1. Install/Update to ACF 6.6 and blocks to version 3
  2. Navigate to edit a post/page that contains ACF block fields
  3. Navigate away or refresh the page without making any changes to the content
  4. Get prompted about unsaved changes

Expected behavior

  • Only actual content modifications should trigger the unsaved changes prompt

Version Information:

  • WordPress Version: 6.8.1
  • PHP Version: 8.2.29
  • ACF Version: 6.6.1
  • Browser: Chrome 141
  • OS: macOS Tahoe 26.0.1

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

Reproduce the prompt in the Gutenberg editor with WordPress 6.8.1, ACF 6.6.1, and ACF blocks v3, then compare a page containing ACF blocks with one containing only regular JavaScript blocks. Trace when the editor marks content as changed during load; done means navigating away or refreshing after loading unchanged ACF blocks does not prompt.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.