TypeError: array_filter(): Argument #1 ($array) must be of type array, null given in array_filter()

Solved the error.

Thanks @kul.pratap.
Seems like you brought many other changes. Please, only commit changes related to the issue, not 1000 files.

@vladimiraus, I have only changed one file, not 1000 files. All other commits are not done by me, I have only done one commit.

kul.pratap → changed the visibility of the branch 3513598-typeerror-arrayfilter-argument to hidden.

kul.pratap → changed the visibility of the branch 3513598-typeerror-arrayfilter-argument to active.

Here is my commit :

@kul.pratap, if you view the MR on GitLab, https://git.drupalcode.org/project/drupal/-/merge_requests/11515/diffs, in the upper right corner you will see the number of changes as, 1000+ files + 4548 − 12566. I have seen that number of changes when someone was not working on 11.x HEAD. I think this needs a rebase on 11.x. There is help for that at Rebase a merge request →

Further investigation of the issue:
- when Use aggregation is on, fields on the view have "Aggregation settings"
- if Aggregation type set to "Group results together" other form options (Group column and Group columns (additional)) are rendered
- if Aggregation type set to Max/Min/etc other form options are not rendered, but they are being processed by submitGroupByForm() in web/core/modules/views/src/Plugin/views/field/EntityField.php
- if Aggregation type set to other than "group" - EntityField::submitGroupByForm() still processes although EntityField::buildGroupByForm() was never called (only HandleBase::buildGroupByForm() is called)

see attached screenshots

Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .

jannakha → changed the visibility of the branch 3513598-typeerror-arrayfilter-argument to hidden.

jannakha → changed the visibility of the branch 3513598-typeerror-array_filter to hidden.

#12 reads like the solution shouldn't be what I see in the commit in #10, we shouldn't just revert to an empty array to ignore the problem, we should probably fix the submit flow described in #12 right? EntityField::buildGroupByForm() should be called or EntityField::submitGroupByForm() shouldn't not be called? Am I reading that right?

@lendude exactly! #10 is just treatment of a symptom, not an actual solution to the potentially bigger issue.

If EntityField::buildGroupByForm() is not called, then EntityField::submitGroupByForm() should not be called.
EntityField::submitGroupByForm() expects certain fields to be there (hence the null exception).

I haven't found a reason why EntityField::buildGroupByForm() is not called but EntityField::submitGroupByForm() is called on aggregations like min/max/sum/etc, but when it's default (eg group) both EntityField::buildGroupByForm() and EntityField::submitGroupByForm() are called.