- Issue created by @msielski
- π³πΏNew Zealand quietone
Drupal 10 is in maintenance mode with a limited set of allow changes β . A normal bug can be fixed in the main development branch, 11.x, not in Drupal 10.
Does this problem occur on 11.x?
After enabling the new core Views EntityReference filter, the configuration UI for entity reference filters appears to be broken for non-exposed filters. Originally reported to views_core_entity_reference β .
Uncaught PHP Exception TypeError: "Illegal offset type in isset or empty" at /app/web/core/modules/views/src/Plugin/views/filter/InOperator.php line 345, referer: https://d10.lndo.site/admin/structure/views/view/test1
Uncaught PHP Exception InvalidArgumentException: "The configuration property display.default.display_options.filters.field_articles_target_id.value.0.target_id doesn't exist." at /app/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php line 95, referer: https://d10.lndo.site/admin/structure/views/view/test1
drush php:eval "\Drupal::keyValueExpirable('tempstore.shared.views')->delete('test1');"
Unknown. Debugging this some, in InOperator::adminSummary it looks like $this->value is an array of arrays when the code expects just an array. So the foreach ends up with $value as an array, and calling isset($flat_options[$value]) gives us the illegal offset error. I'm not sure though where this can be addressed - maybe further up the inheritance chain in EntityReference class?
Active
10.4 β¨
views_ui.module
Drupal 10 is in maintenance mode with a limited set of allow changes β . A normal bug can be fixed in the main development branch, 11.x, not in Drupal 10.
Does this problem occur on 11.x?