Please note that this feature request is now 6 years old. Item 2 has been thoroughly solved by the introduction of clone fields some years ago.
I would still, to this day, love to see an option to remove the group header for groups that really, really don’t need it. But over time this has wilted into “minor annoyance.” Right now I have the honor of actually working with Elliot on another completely different issue and for this reason I am diving really deep into the codebase, getting very familiar with the code. Maybe I will find a solution and propose it myself. Maybe it will even be possible using a plugin. Let’s see.
I’m sorry to see that after 4 months this bug is still marked as “unread”, i.e. not even acknowledged. Is it too obscure, or did I do a bad job at describing it?
For posterity, I ended up on the following hotfix. The additional test for the existence of get_current_screen() is necessary on some (unrelated) admin screens.
function conditional_acf_set_l10n(){
if ( is_admin() ) {
if ( function_exists('get_current_screen') ) {
$current_screen = get_current_screen();
return ( $current_screen->post_type != 'acf-field-group' );
}
}
return true;
}
add_filter( 'acf/settings/l10n', 'conditional_acf_set_l10n' );
Hello John,
thanks for answering. In the last two months since I reported this here, I was in direct contact with the ACF support who was very helpful, even though the problem was not directly connected to ACF.
It was indeed not a problem with ACF itself but a rather obscure server bug that triggered an error with another plugin (IWP Client) which in turn prevented the AJAX call to be completed. Strato, the hoster in question, has since updated/bugfixed their servers.
Best
Freddy
JFTR: I believe you are spot-on with the have_rows issue. Just yesterday, I stumbled over the error and narrowed it down to a single, lonely if ( have_rows('field') ) starting off the treatment of a flexible content field. And, like for the others here, the 5.1.2 update corrects it.
By the way, with ACF 5 this “bug” has been corrected. ACF now allows you to save the post with the “yes/no” in either state, even if set to “required”. Which means that the “required” option on “yes/no” fields is completely meaningless now.
deepfriedfilth, I have no idea how that would have been a solution to the problem.
However, with the release of ACF 5 and its new layout this feature request has, obviously, become obsolete.
