The latest installment of ACF Chat Fridays gave the community an exciting preview of the imminent ACF 6.6 release. The session detailed major upcoming improvements, including the official launch of ACF Blocks v3, and quality-of-life enhancements to Field Groups and the Color Picker field. The open Q&A session also provided welcome news, as the team confirmed that the architectural changes in Blocks v3 will resolve a long-standing editor bug.

Hosted by Iain Poulson, Matt Shaw, Phil Johnston, and Anthony Burchell.

Sign up for the next session →
ACF Chat Fridays Banner Image.

Session Recording

Watch the full session below or skip to the highlights in the session summary.

Session Summary

Iain Poulson kicked off the session with the big news that ACF 6.6 is expected to be released very soon, likely this week. This major version is centered around the introduction of ACF Blocks v3, a significant update that improves compatibility with modern features of the WordPress block editor. This new version resolves the conflict caused by WordPress’s use of iframes to render blocks in the editor and introduces a much-improved editing experience for fields located in the block sidebar. This foundational work also paves the way for the highly anticipated inline editing feature, planned for a future release.

Beyond ACF Blocks v3, ACF 6.6 will ship with several other highly-requested features:

  • Field Group Display Title: A new setting that allows developers to define a user-friendly title for a field group that is shown to content editors, while keeping a separate, more administrative title for the backend.
  • Enhanced Color Picker: The Color Picker field now has two new options for defining its color palette. Developers can either provide a custom list of hex or RGB values, or toggle an option to automatically inherit the color palette defined in their theme’s theme.json file.

The session concluded with an in-depth discussion about how the changes in ACF Blocks v3 will impact existing workflows and solve specific editor issues.

Q&A

Questions and answers from the session have been paraphrased for clarity.

Q: We have a persistent bug with custom blocks that contain multiple WYSIWYG fields. When adding a new paragraph or block above the first WYSIWYG, the cursor focus unexpectedly jumps to the last WYSIWYG field on the page, making editing very difficult. The lazy-loading workaround hasn’t solved it. Will this be fixed?

A: Yes, we believe this will be resolved in ACF 6.6. The engineers on the call were able to replicate this bug with ACF Blocks v2, but also confirmed it does not occur with the upcoming ACF Blocks v3.

The issue is resolved because ACF Blocks v3 changes the architecture of block editing. Fields will no longer render in a form inside the block preview. Instead, they will only be available in the sidebar or a new, larger pop-out modal. This change removes the underlying conflict between multiple TinyMCE instances that was causing the focus-jumping behavior. To get the fix, you will need to opt-in to ACF Blocks v3 by updating the apiVersion in your block.json or PHP block registration.

Resources & Links

Coming Up on ACF Chat Fridays

Register today for the next session of ACF Chat Fridays. Sessions are typically held on the first Friday of every month. Questions and suggestions for the development team are always welcome.

Register for the next session of ACF Chat Fridays here: https://wpeng.in/acf-chat-fridays/

The list of upcoming sessions is below.

  • November 7, 2025
  • December 5, 2025
  • January 2, 2026
  • February 6, 2026

Tag or DM us on Twitter with suggestions or feedback using #ACFChatFridays.