Works like a charm, much thanks.
(Didn’t use the plugin, just changed the setting on my server)
Bump… hope that’s allowed here
It makes sense that the desired location would be what the option refers to, but you’re really choosing the desired location in the 3rd dropdown of the rule. That’s demonstrated much clearer when you choose the Page Template in dropdown 1, and all of the page templates appear in dropdown 3.
Dropdown 1 = Group of potential desired locations
Dropdown 2 = Equals/not equals (irrelevant in my example)
Dropdown 3 = Desired location
It seems to be set up like that for everything in dropdown 1, but Taxonomy and Taxonomy Term are just displaying the wrong stuff. Anyway it’s not a big deal, but I thought I’d throw my observation out there because taxonomies are arguably the most confusing thing to wrap your head around as a WordPress newbie and having this (maybe) naming mixup could fluster some people.
PS. I’m also not sure why the final optgroup “Forms” is the most suitable place for Taxonomy Term.
I can live with the Message field solution 🙂
If I had the skill I would create an addon but I’ll leave that to the pros.
I figured it out myself after I realized that the global acf JS object was listening for form submissions. Here is what I did for anybody else who has this problem.
$(‘form#my-form’).submit(function(e){
e.preventDefault();
e.stopPropagation(); // Prevent the acf object from ever hearing about this form submission
});
Thanks for the link, but what I meant was that a field would only be visible to users logged in as administrators, not that a field would appear on the administrator profile page.
I know that ACF doesn’t do view counting ;). It was a quick example to illustrate a use for an admin-only visibility field.
I am also getting NULL when using get_field(‘example_field’, ‘option’) in the secondary language, is there a workaround for those of us who don’t want to translate options? Sometimes it’s just not necessary, like for phone numbers, email address, contact info, custom settings parameters, etc
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.