This reply has been marked as private.
There could be multiple validation errors across multiple tabs, but I agree with what I assume is the basis of followalter’s suggestion: it can be difficult to locate a validation error when there are many fields, particularly when there are accordions and tabs.
So a related suggestion: list the label of each field that fails validation in the “components-notice” at the top of the page.
I just wrote a script that does this and, as usual, it took me longer than I would like to get it right.
It would be great if this were built into ACF, so you know immediately which field(s) failed validation before hunting through tabs and accordions.
Apparently I have trouble seeing what’s right in front of me. Thanks and sorry to bother you, John!
Elliot: I saw that 5.2.1 was released so I tried it and it seemed to fix the issue. I’m not sure why I got such a crazy result when I installed the pre-release version but I think it’s moot now.
Thanks again for following up.
Thanks for the updated version, Elliott, but it caused things to go haywire on the one site where I tried it. Custom fields for ALL pages were available on a page where they didn’t belong. Most didn’t display because, again, they weren’t ticked in screen options. One field group that didn’t belong to that page was trying to display, but the loader just kept spinning.
I checked my custom fields settings to make sure they were correct, and they were. Those field groups were not configured to display on that page.
So I rolled back to the last version, where the issue on this thread still exists but fields group are at least correctly associated with their pages.
Thanks for trying to get this resolved.
@Dalton Thanks for getting on this, and for the tip about finding the custom fields under “screen options”. I’ve updated ACF on only a couple of my sites today but this is a major glitch, as all custom fields have effectively disappeared for those two sites. I hope another update is forthcoming.
