I first save a field group with one column, and then tried to update it to two columns, and once I click save I get this error:
TypeError: Argument 2 passed to field_group_formatter_row_update() must be of the type array, null given, called in /var/lib/tugboat/stm/web/modules/contrib/field_group/includes/field_ui.inc on line 163 in field_group_formatter_row_update() (line 555 of /var/lib/tugboat/stm/web/modules/contrib/field_group/includes/field_ui.inc)
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | Screenshot from 2024-05-02 12-18-58.png | 166.2 KB | amandeep123 |
Issue fork field_group_layout-3392514
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
shreya_th commentedComment #3
shreya_th commentedComment #5
ravi kant commentedI got different errors.
Error
Warnnings
Comment #8
amandeep123 commented"Hello @Valentine94 and @RaviKant I've created a merge request to address the previously mentioned issue. The solution has been implemented, and now the functionality is working smoothly." Please Review.
Comment #9
amandeep123 commentedHy @Valentine94 ,@matsbla
I Have Raised The Merge Request ,Please Review Once.
Thankyou
Comment #10
matsbla commentedI tested the patch, but the group layout is not changed, and I get some new errors:
Comment #11
amandeep123 commentedHy @matsbla ,please have a look at the merge request 5 created and working for the above issue
Thanks
Comment #12
matsbla commentedYes, that is the one I tested:
https://git.drupalcode.org/project/field_group_layout/-/merge_requests/5.diff
And it gives the new errors.
Comment #13
amandeep123 commentedComment #14
amandeep123 commentedhy @matsbla. This change fixes the error showed in the screenshot and also sorts out the issues you had before. Now, you can move field groups from one column to another without any trouble. It makes everything smoother and easier to use. please review
Comment #15
matsbla commentedThe error mentioned in #10 is still there. In addition when you click update the whole website encountered an unexpected error:
Comment #16
matsbla commentedPlease upgrade to 2.0.0-alpha1, this should be fixed now.