Home › Forums › ACF PRO › v220.127.116.11 name property in sub field object has changed › Reply To: v18.104.22.168 name property in sub field object has changed
Well, then it is a recent change, 22.214.171.124 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’re hard at work on ACF 6.1, and Beta 1 is now available 🚀— Advanced Custom Fields (@wp_acf) March 16, 2023
This release includes custom post type and taxonomy registration, an improved experience when selecting field types, PHP 8.1 and 8.2 compatibility, and more!
Let’s take a look 🧵https://t.co/Y0WcAT11l4
© 2023 Advanced Custom Fields.