Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
InvalidArgumentException: The configuration property display.default.display_options.filters.field_[field_name]_location_proximity.group_info.group_items.1.value.value doesn't exist. in Drupal\Core\Config\Schema\ArrayElement->get() (line 74 of core/lib/Drupal/Core/Config/Schema/ArrayElement.php).
Comment | File | Size | Author |
---|---|---|---|
#7 | 2870523-7-support-grouped-proximity-filter.patch | 1.24 KB | ChristianAdamski |
Comments
Comment #2
ChristianAdamski CreditAttribution: ChristianAdamski at Wolters Kluwer commentedCould you lay out the steps to reproduce this on a clean drupal install?
Comment #3
caldenjacobs CreditAttribution: caldenjacobs commentedThe error occurs if the following steps are taken:
Add a geolocation field to a content type.
Create one or more content nodes containing the geolocation field, populated with valid data.
Create a View querying the geolocation field's proximity.
Add a geolocation field:proximity exposed filter to the View, selecting 'Grouped filter'. Populate the exposed filter's Label (cannot be empty), Operator ('Is less than or equal to'), and Value (desired distance limits, i.e. '5', '10', '50') columns.
Attempt to save the View.
Comment #4
ChristianAdamski CreditAttribution: ChristianAdamski commentedHave to check later, but that double 'value' in the schema is probably wrong. Should be easy to fix.
Comment #5
ChristianAdamski CreditAttribution: ChristianAdamski commentedComment #6
ChristianAdamski CreditAttribution: ChristianAdamski commentedIt's actually not simple. Darn.
Comment #7
ChristianAdamski CreditAttribution: ChristianAdamski commentedThis patch locally allows for grouped proximity filters against a statically defined center. The exposed form proximity filter requires more work.
Comment #8
ChristianAdamski CreditAttribution: ChristianAdamski commentedNext task:
Make ProximityFilter.php -> acceptInput() function smart enough to retrieve values from a grouped filter.
Comment #9
ChristianAdamski CreditAttribution: ChristianAdamski commentedHmm, the exposed form is not rendered at all, when the filter is set to grouped input, so that can't work.
Comment #11
ChristianAdamski CreditAttribution: ChristianAdamski commentedAdded check to not try to retrieve exposed values when grouped.
Fixed.