I know this is an old post, but i’d like to +1 it. Could definitely use the ability to clone whole layouts
Add another +1 to this request.
Can you please set the default to true, and then give us a GUI option to remove or keep? We have CPTs that aren’t available to lower roles that don’t use ACF fields but DO utilize wordpress’ standard custom fields. Having them completely removed and no immediate way to re-enable them is frustrating.
That’s what I meant by “or any combination of those”. Doesn’t matter if i change to private and then preview, or password protected and then preview, or public-to-private-back-to-public: changes in custom fields aren’t reflected in preview. Only way to see the changes is to publish the page/post.
Also experiencing same issue (wordpress 4.6.1 + ACF). Unfortunately, switching from Public to Private and back to Public (or any combination of those) doesn’t make a difference. Custom field data is not displaying until after publishing.
VERY handy to know about. Thanks for pointing that out. I do have a couple of situations where things need to alter slightly for users with contributor permissions. Will definitely come in handy
for the ACF fields attached to post format i was able to use the location rules. for the non-acf fields I was able to update my javascript so there were no longer conflicts between it and ACF’s js. The key piece was the post format in the location rules. just completely overlooked that.
i knew i was just overlooking something. I had not noticed that there was an option for “Post Format” in the location rules. That’s exactly what i needed. Thanks, @hube2 !!
ah. We were on 5.3.7 and skipped over 5.3.8 and went straight to 5.3.8.1. That must be why we didnt see the change until now.
There is another field attribute with the index of “_name” that contains the actual name of the field, this has also been there for a while
PERFECT! Way better than regex’ing the key back out and keeps from having to retrieve and store more than what I want. Thank you!
This is happening to every field included in a flexible layout, not just radios/selects.
I did hear back from James in support who indicated this is a permanent, known change. While disappointing, I’m pretty sure I can regex my way around it and pull out the original key/name. I don’t like doing that as it seems way too brittle… I guess maybe I could switch to using get_field_object instead of get_sub_field_object(), as it appears that get_field_object still returns the real name value instead of the adjusted name value.
