<li class="tabs-title"><a href="#panel7" data-tabs-target="panel7">Categories</a></li>
## Entity Proximity Webform Select — Multi-value region filter support
### Bug fix
The region selector now works correctly with multi-value region filter
fields. Previously, only the **first** value of the field was used to
assign an entity to a region: an entity tagged with several regions
(e.g. a dealer serving both Belgium and France) only appeared under the
first one and was hidden when the user selected any of the others. Every
field value is now taken into account, so the entity is listed under each
of its regions.
### API change — action may be required
The `region` key attached to each entity record is now an **array of
strings** (one per field value) instead of a single string. This affects
`hook_entity_proximity_entities_alter()` implementations:
```php
// Before
if ($entities[$id]['region'] === 'Belgium') { ... }
// After
if (in_array('Belgium', $entities[$id]['region'], TRUE)) { ... }
If your site implements this hook but does not read the region key
(e.g. it only reorders or filters entities by other properties), no
change is needed. Sites that subclass EntityLocatorService and override
the protected extractRegionValue() method must also update it, as its
return type changed from string to array.
Upgrade notes
- Run database updates (drush updb): update 10101 purges entity
lists cached in the old single-value format. Without it, the fix only
becomes visible once the cached lists expire or on the next cache
rebuild.
- No configuration change is required: the filter_value of each region
on the webform element keeps the exact same semantics.
- The bundled JavaScript remains compatible with records cached in the
old string format, so a stale cache degrades to the previous behavior
rather than breaking.