Views geofield proximity filter does not work for anonymous users

Created on 31 March 2023, over 1 year ago
Updated 7 April 2023, over 1 year ago

I havent seen this documented anywhere and Im not sure if its supposed to work, but the views proximity filter does not work for anonymous users. It works fine for autheticated users.

For anonymous users, all locations on the map are displayed regradless of the distance entered in the filter.

🐛 Bug report
Status

Postponed: needs info

Version

1.52

Component

Code

Created by

🇬🇧United Kingdom problue solutions Northern Ireland

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @problue solutions
  • 🇬🇧United Kingdom problue solutions Northern Ireland

    Some more information - for some reason it works for anonymous users on dekstop devices, but not mobile devices.

    We have tested on a number of different andoid devices using Chrome, it doesnt work on any of them for an anonymous user, but once they log in it works fine. On desktop it works fine on Chrome, Firefox and Edge for anonymous users.

  • Status changed to Postponed: needs info over 1 year ago
  • 🇮🇹Italy itamair

    Weird ... I cannot reproduce this.
    I am on my iPhone with Safari and this Geofield demo page: https://www.geodemocracy.com/drupal_geofield_stack_demo/web/
    works correctly also filtering on the Proximity filter.
    It works well the same also if use Chrome for iPhone.

    For instance I input "Central Park" ... wait (a while) for the autocomplete response and once I select and Filter, the View returns only the close Markers. Screenshot attached.

    Probably you should provide better evidence of what you assume being a bug.
    May be inspect and providing the Js console outcome/errors from your Android Browser ...

  • 🇬🇧United Kingdom problue solutions Northern Ireland

    Yes I thought this was weird also, the only reason I posted here is because we seen it on multiple different devices. We had changed our requirements so that we didnt need to allow access for anonymous users which is why I did not investigate further and report back sooner, There could be many factors at play, for example we use better exposed filters, and filters exposed in a block for a block display etc.

    I guess its probably better to close this and I will open a new issue with more info if we encounter this again in future.

Production build 0.71.5 2024