- Status changed to Fixed
8 months ago 11:46am 2 May 2024 - πΊπΈUnited States douggreen Winchester, VA
This appears to have merged, so marking as fixed.
Automatically closed - issue fixed for 2 weeks with no activity.
When using Geolocation CommonMap format in Views, if the Geolocation field is multi-value the map shows all values from the entity, no matter whether the field and filters are configured to show less per row, for example, if we want to show in the map just the first value (delta = 0).
DataProviderBase::getPositionsFromViewsRow()
does not honor its own name because it does not take the positions from the Views Row, but instead it takes the entity from the row (within DataProviderBase::getFieldItemsFromViewsRow()
) and get all positions from the entity field regardless of the views row data.
That might make sense when we want to group all values in the same row (checking that option in the field settings), but not when we want each value in a different row, and maybe filter those results as in the proposed scenario.
We should take the position from the row data if it's available, and show all the entity values only when the option of grouping all values in the row has been set.
Fixed
3.0
Geolocation Field / Backend
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This appears to have merged, so marking as fixed.
Automatically closed - issue fixed for 2 weeks with no activity.