Props to Pacart. –> Sounds like a plan!
Cool thing. Thank you for “the crude fix”. It works still.
Hi John,
Thanks for your answer. Updating the fields didn’t help, so I went full circle:
When I ditched the database and kinda “started from scratch” concerning the db (synchronizing all fields from the json files), the errors did not occur again.
So I’m guessing: Might have been a minor glitch which might have nested itself in the db when I duplicated the fields into another language.
–> Somewhere there/towards your assumption:
it could be that the duplicated groups that include cloned groups the key of the cloned group was not set correctly
Concerning this bug report: I’m good. I don’t think I’ll run into these notices again any time soon.
Cheers
Thanks for the info.
I’ve got over 60 field groups, some of them are flexible fields with several of the other field groups as clones inside their flexible field layouts.
Notices started to pop up after I’ve duplicated the field groups via WPML (WordPress Multilingual Plugin) functionality to make the field groups available in other languages.
I did not consider the hierarchy of the fields while duplicating them. Meaning: I should have duplicated the ones which are used as clones first. And only after duplicating all the basic field groups I should have started with duplicating the rather complex ones.
–> Might be the reason why I get these notices now.
Same here:
Notice: Undefined index: key in .../acf-field-functions.php on line 349
I switched off the WP_DEBUG_DISPLAY for now.
