The November 7, 2025 session of ACF Chat Fridays was an open forum focused on the recent release of ACF 6.6. The team detailed the improvements in the new ACF Blocks v3, discussed the roadmap toward inline editing, and gathered valuable, live feedback from the community on editor UI challenges and feature requests.
Hosted by Matt Shaw, Phil Johnston, and Anthony Burchell.
Sign up for the next session →
Session Recording
Watch the full session below or skip to the highlights in the session summary.
Session Summary
Matt Shaw kicked off the session by announcing that ACF 6.6 has been officially released. This is a significant update centered on the introduction of ACF Blocks v3.
This new version leverages WordPress Core’s Blocks v3 API, which finally solves the long-standing “iframe” issue. This change prevents WP admin styles from “bleeding” into or competing with your theme’s styles, ensuring that blocks in the editor look exactly as they do on the front end. The team noted one important caveat: for the new iframed experience to activate, all blocks on the page (including non-ACF blocks) must be upgraded to apiVersion: 3.
ACF 6.6 also introduced a new editing experience. The old in-preview edit form has been replaced by a new “pop out” editor modal. This provides a much larger, more focused area for field editing, which is a major improvement for complex fields like Repeaters and Flexible Content.
This release serves as the critical foundational work that paves the way for the next major feature: inline editing, which is planned for ACF 6.7.
Q&A
Questions and answers from the session have been paraphrased for clarity.
Q: Is there documentation for the new inline editing feature and how to use it?
A: Documentation will be published when the feature is released, which is “soon”. We demoed an early version in a previous session, and it’s important to know it will be completely opt-in. The new pop-out form editor introduced in 6.6 will remain the default. We’ve received feedback that many users prefer a form-based experience (especially for data entry), so both methods will be fully supported.
Q: I have a Relationship field in a metabox with 20-30 items. The field’s container is very short and only shows about 6 items, which makes it extremely difficult to manually re-order them by dragging. My only solution is to hack the CSS. Can this UI be improved?
A: This was excellent feedback. The team watched a live demo of the issue and agreed that the fixed-height container is a significant pain point for managing large data sets. We are taking this feedback directly into our planning sessions and will investigate making that container resizable to provide more space for sorting.
Q: I have two related post types, “Issue” and “Article.” Can an “Article” automatically inherit the pub_date field from its parent “Issue” only if the “Article’s” own date field is empty?
A: That’s a very interesting idea for a visual rule builder. It sounds like a conditional rule that also performs a “data-syncing” action. While the closest feature we have now is the bidirectional setting for Relationship fields, this is a great suggestion. We will pass it along to our product manager for future consideration.
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.
- December 5, 2025
- January 2, 2026
- February 6, 2026
Tag or DM us on X (formerly Twitter) with suggestions or feedback using #ACFChatFridays.
For plugin support, please contact our support team directly, as comments aren't actively monitored.