I would like to know this too. I’d like to display ACF prepend/append values using shortcodes.
Excellent point, I forgot about that. Thanks Elliot.
Elliot,
I’m using the select field with “allow null” set to yes. With the select box left on “- Select -” it still saves a value of “null” to the custom field. This leads to a bunch of custom fields like this:
It appears this just isn’t with null values, as ACF creates blank custom fields also (see the “link” custom field above).
This is particularly a problem when the existence of a custom field is used for determining “null.” For instance, consider a custom field “Name” with a value of “null.” Well, is there a name? Is the name null? This wouldn’t be an issue if the custom field wasn’t created.
Great! Thanks for your help.
Yeah, I was referring to the select box only, not the value (sorry if that was unclear).
So for my situation, should I just make the first option “Select” followed by “True” and “False”? That way I could tell which custom fields are blank.
Also, is there a way to decrease the width of the select box in ACF?
Elliot,
Sorry for the complicated question. It’s probably easier to explain with a screenshot 🙂
As you can see, the default value for the select box is “Select.” So if I create a new custom field, then come back to edit this post, I can tell I haven’t set that custom field before. Whereas with your plugin the default is “True” and I have no way of knowing if I set it to “True” or not. Does that make sense?
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.