Also took me hours to fix several of our websites, these essential changes came extremely unexpected. There should have been a prominent notice in the backend for the latest 2-3 versions, that there are fields/functions in use, that could cause issues with the upcoming version.
Apart from that: If you are facing serious issues that have impact on your site/rankings, I would recommend to download a previous version of this plugin on your account page and then implement all needed fixes in another dev environment without hurry and testing everything, before doing the final switch on the live site
If you’re using a seo plugin (e.g. yoast) and some custom filters to modify the meta titles/descriptions, make sure, that you are not using get_field() there or at least only on fields, that have really been created with acf. I didn’t get any notice from the acf plugin on one of my website, but then I realized all my meta data is broken, because the placeholder values are no longer working; switching to get_post_meta() fixed all issues in this case also
@itchef
Is there a way we can check which fields are being ‘rejected’ when calling get_field in 5.11? That way it makes it easier to add these fields that are not registered through ACF.
Try your luck with the “query monitor” plugin and have a look at the “php errors” tab, this saved my life. I was using get_field(…,”option”) outside of a function in my theme, I would have never found this by myself, since we’re having hundreds of fields.
See: Screenshot
I’m running into the same issue, I’ve added an image via filter to make it easier to connect products with another post type. I’ve tried
add_filter( 'wp_kses_allowed_html', 'acf_add_allowed_iframe_tag', 10, 2 );
function acf_add_allowed_iframe_tag( $tags, $context ) {
if ( $context === 'acf' ) {
$tags['img'] = array(
'src' => true,
'height' => true,
'width' => true,
'alt' => true,
'class' => true
);
}
return $tags;
}
to allow img tags, but this does not change anything. Any option, to deactivate this security feature completely? I’m the only one working on this page, so I don’t need any filters, I can care of these things myself. 🤐
For the moment I’ve downgraded to 5.9.9. again
Their addon seems to have some more problems, took me several frustrating hours now. Solution is:
Deactivate their ACF Field Addon and simply add the field names in the custom field section instead of mapping them with the acf groups directly. And also remember to change the fields, that should get updated on each import (switch from acf to normal custom fields and add the field names).
This will also work with fields, that are created via json.
Thread can be closed then. Thanks!
I also stuck on this problem. I’ve imported some posts, but one group ist not accessible via get_field(), although all values appear in the backend. So I guess I need to update these group values to register them correctly in the database. But how to do it? They are placed inside flexible content fields themselves, so the meta_key in the database look like
content_section_3_button_text
…..
…..
…..
content_section_9_button_text
Which means, ‘content_section’ is the flexible content field with different sections inside, and these sections have got a group called ‘button’ with a child field ‘text’ (for the button text) inside.
I also tried to access them with the field_keys, but no success yet. Any ideas? Thanks a lot!
After reading further threads I came up with this solution provided by James:
https://support.advancedcustomfields.com/forums/topic/fields-groups-not-showing-on-the-fields-groups-list-screen/
And it works. So this thread is solved. Thanks 😛
I would also appreciate if this feature could be included in one of the next versions. As drewcovi already mentioned, checkboxes or radio boxes are not pratical if you have to deal with a great amount of values. So it would great, if the select box (search function) would also get this feature 🙂
