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
