Nataliette,
I’m building a site with the EXACT same requirements and came upon your post as I try to figure out the best way to be able to both order ingredients independently for each recipe AND have them work as custom taxonomies.
I’m curious if your solution worked well or if you would do it differently in ACF now?
I came across this while trying to solve a similar problem. In my case, I have a Taxonomy field as radio buttons that I would like to style more like the True/False UI.
I thought it would be doable via some admin CSS, but the markup is such that there’s no way to target a checked input’s label. (The common way to do this is via adjacent selectors in CSS, but ACF outputs the radio button input as a child of its label, not a sibling, unfortunately.)
It seems like this would be a logical change to the markup in ACF so that we would have more flexibility to “roll our own.” Unless I’m missing a possibility here?
Mishtershmart,
Can you share a snippet of how you did this? I need to do this exact thing, where I have a default field group that is on every page and needs to be right after the title of the CPT, but I need other field groups’ options to always take precedence. I’m not following how you achieved it.
You ever figure this out? I’m in the same boat.
And of course I just figured it out–for some reason the setup_postdata($post) in the first query was throwing it off. Leaving this here in case someone else runs into it.
I think something like that might work. Yeah, basically the notification would just be a feed that lists updates to a specific location’s list of beers as they happen. So if a beer is added/removed, then the feed would populate with a new “post” essentially saying what beer was added or removed. Make sense?
I’m going to try something along these lines and will report back.
Likewise–just realized this bug myself.
Yes, was hoping to see it in ACF Pro based on this thread. Would love to be able to have ratings for a site I’m building be tied into ACF like everything else!
