bumping this topic for ACF experts. multiple people posting about generally the same thing.
same issue here. A few people have posted about it. Not intuitive even with the existing documentation.
I’m just getting the default Melbourne address on the front end despite the address being populated on the back end. Using a repeater google map field. Have read and tried everything mentioned on here and elsewhere. My page isn’t calling the maps api multiple times, etc etc.
I’m having the same issue and have read and tried pretty much everything here and elsewhere online.
a couple of notes:
1. You can add a specific field’s class on this to differentiate start and end date placeholders, for example.
2. You can’t use the above with repeaters, and nothing I’ve been able to find short of either creating a new custom field or doing some complex render_field_settings and render_field hooks in functions can resolve this.
It will show the placeholder in the first repeater row, but not in the subsequent ones.
holy crap this is super helpful!
Thanks so much. Super helpful. I spent a couple hours digging based on your info and unfortunately have been unable to get it to work. I will update this post if I’m able to figure it out.
this was really helpful, @mkeys. thanks for taking the time to add it.
Ah-thanks. Rhetorical question, but worth asking. Are you aware of any workarounds?
I have ~10,000 tags and it will be potentially be confusing to my users.
I was thinking there had to be some WP Query $arg for this.
Note that “filter for every field” didn’t seem to work either.
@nikosolihin thanks for what you wrote! It was super helpful!
Ok- got it to work. I think the “taxonomy term” filter type might have gone the way of the dodo in a recent release, replaced with taxonomy = all (if you want the field for all taxonomies). When I chose this, my custom fields appeared.
Also, you can filter for the fields to only appear on certain terms with the post taxonomy = whatever category you choose.
If you are still having issues and it is not appearing, see if another field group is already targeting those taxonomies or specific categories. I’m not for sure the rules on multiple field groups to the same targeted whatever, and there could always be a bug.
But I think the above will solve what ails ye. Let me know if it doesn’t.
Yeah- just to let you know (and I’m not sure why no one has replied) – I am seeing the same issue. I’ll reply again if I can figure out why. Seems like a pretty big bug if true, so interesting we’re the only two people who have commented (on this thread at least).
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 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 Privacy Policy. If you continue to use this site, you consent to our use of cookies.