- Issue created by @kenrbnsn
- Status changed to Needs review
over 1 year ago 6:24pm 10 November 2023 A lot of sites are using Drupal 10, views filters, and BEF. We need to find out the real steps to reproduce.
- last update
over 1 year ago 29,682 pass - 🇺🇸United States kenrbnsn New Jersey
Ok. We will try to come up with a way to reproduce the error. As of now, we're just seeing it in our Drupal logs.
- Status changed to Needs work
over 1 year ago 6:48pm 10 November 2023 - 🇺🇸United States smustgrave
Moving to NW for the steps as mentioned in #2. May need to investigate too why that value could be null so we aren't masking a larger issue potentially.
- Status changed to Postponed: needs info
over 1 year ago 2:21pm 11 December 2023 - 🇳🇱Netherlands Lendude Amsterdam
Moving to postponed since there is obviously more needed for this error to be shown than just adding any filter to a View
- 🇪🇸Spain akalam
I can reproduce it after upgrading to 10.3.1
The patch solved the issue - 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
TypeError: Drupal\Core\Render\Element::children(): Argument #1 ($elements) must be of type array, null givenis like a Virus these days. It spreads all over the issue queues and we can reproduce it on every single Drupal 11 install here. No matter if barebone vaniall core or added up with contrib modules, the error occurs with back trace to core Views, Layout Builder or to different bigger contrib modules like Display Suite and others. My assumption is that PHP becomes now more strict on types and we got away with it before how it was ... until now. - First commit to issue fork.
- Merge request !11065Issue #3400858: Argument #1 ($elements) must be of type array, null given → (Open) created by Unnamed author