Home › Forums › ACF PRO › v5.3.8.1 name property in sub field object has changed › Reply To: v5.3.8.1 name property in sub field object has changed
Well, then it is a recent change, 5.3.8.1 came out the same day as 5.3.8 due to bugs that needed fixing. To be honest, I gave up on using field names for sub fields a long time ago so it may be another reason I haven’t notices, I almost always use the field key. The field names you’ve mentioned have always been there (or been there long enough that I can’t remember them being different) when using filters like load_field and load_value. It could be that the way they are now was something that’s been overlooked and may have been causing other issues, honestly, I don’t know, just guessing 🙂 I do know that the “_name” index has been there as long as I can remember though.
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.