Home › Forums › Bug Reports › l10n: ACF translates label VALUES in group editing screens › Reply To: l10n: ACF translates label VALUES in group editing screens
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' );
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We’re working hard on Advanced Custom Fields PRO 6.0, and Beta 1 is now available 🚀
— Advanced Custom Fields (@wp_acf) August 12, 2022
Featuring improved performance for Repeater fields with large datasets, and a new generation of ACF Blocks.
Let’s take a look 🧵https://t.co/Befre3kFAo
© 2022 Advanced Custom Fields.
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.