This is an issue in ACF and how they now handling the meta boxes. Hopefully they can address the issue.
Nikho, it’s normal, elliot add a fix to detect all ACF Group field at initialisation. i asked this feature there are few weeks.
Maybe an enhancement would be to load only ACF Group field based on custom post type
Thread Starter
YuMyo
(@nikho)
Sorry sireneweb, I can’t understand how this is working for you.
In Tabify settings each post type shows all acf’s custom fileds.
What happen if you save a tab setting ?
They’ll be included. Then, in edit.php, switching between tabs causes Tabify try loading those fileds. Since they do not belong to that post types, the screen crashes with a never ending attempt to load the (wrongly) “required” fileds.
Thread Starter
YuMyo
(@nikho)
Since the error seems being not blocking (post save or update action), I came up with a kind of fix (shame) adding !important to line 52 of global.css in advanced-custom-field-pro/css/global.css
So turning:
.acf-visible { display: block; visibility: visible; }
.acf-hidden { display: none; visibility: visible; }
in:
.acf-visible { display: block!important; visibility: visible; }
.acf-hidden { display: none!important; visibility: visible; }
prevent inline styles injected by Tabify to overwrite ACF styles.
There’s still the need to inspect if this could be enough or there’s any other compatibility issue especially concerning data.
I create tab and put ACF Group field inside, the rest of ACF Group fields stay at the end of all Metabox in Tabs parameters field.
After when i go in post, page or custom post i see only the ACF Group field based on the location
