Closed (outdated)
Project:
Field Group
Version:
8.x-3.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 May 2019 at 08:31 UTC
Updated:
1 Jun 2024 at 20:32 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
bbombachiniI was having the same notice, then I realized there was a database update pending.
Comment #3
publishing future commentedThank you for the hint. But unfortunately I get the messages without any pending database update.
Comment #4
bailey86 commentedProbably related to: https://www.drupal.org/project/field_group/issues/3059614
Comment #5
nils.destoop commentedSeems like your config is a bit broken, as all of those properties are required field_group properties. I suggest you export the config and fix the broken config in the yml files. I don't think it's related with the missing region, as that one was a property that was added in latest releases. The notices you are getting are properties that always existed.
If you need more help, you will need to do some debugging by placing breakpoints at the places that are giving the notices.
Comment #6
nils.destoop commentedComment #7
kasey_mk commentedOn Drupal 9.2.2 with Paragraphs 1.12.0 and Field Group 3.1.0 I get these errors when I have a term with an Entity reference revisions field for Paragraphs. If I edit the term and add or edit one or more Paragraphs and then save the term without collapsing the Paragraph edit subforms, I get these errors:
My Paragraph form display is pretty complex, using Tab and HTML element field groups.
If I collapse the Paragraphs subforms before saving the term, I do not see these errors. There doesn't seem to be any problem with my data; just lots of these notices.
Comment #8
kasey_mk commentedThis patch adds some checks for empty properties before trying to use them, which makes the error messages I was getting go away.
Comment #9
kasey_mk commentedComment #10
yassersammanThanks for the patch, but imho, and correct me if I'm wrong, the patch in #8 isn't really a solution, the issue is still there, it's literally just avoiding empty objects to hide messages. I think when checking for empty objects, we should provide an "else" for the "if" to handle object variables to be used in the rest of the code.
Also, if you are using the patch in#8, no need to use the patch here:
https://www.drupal.org/project/field_group/issues/3059614#comment-14012954
Comment #11
yassersammanHere is a re-roll for the patch in #8
Comment #12
joseph.olstadupgrading to 3.4 fixed this without patch
Comment #13
nils.destoop commented