You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After digging around a bit more, it looks like I might have narrowed down the cause.
I discovered that the console error "An invalid form control… etc" seems to be a Chrome-specific error meaning that an input element that is marked as "required" is not visible. This is because the normal native browser form validation behavior is to put user keyboard focus on any empty required input on form submission event, but since this element is not visible by default (it's hidden inside the ACF Field Group's "Settings" panel which is collapsed by default), it's unable to focus, hence the error.
The end result is a silent failure to save/update a Field Group.
The only way to work around this is to give every ACF Field Group a GraphQL Field Name (even if it's not marked "Show in GraphQL". Since someone wouldn't otherwise know this is the cause of the issue described I think it's fair to call it a bug. The fix would likely involve only marking the "GraphQL Field Name" input as required when "Show in GraphQL" is toggled on.
After I activate this plugin I'm unable to update or save new ACF Field Groups.
When I open the console, I see the following error when clicking the Update/Publish button on my Field Group:
The text was updated successfully, but these errors were encountered: