When exposing a filter in views of a proximity search, and the origin point is current user, or entity from url, or other geofield, etc. the empty field which is used for manually entering a point should not be shown, but it is.

See screenshot below. The "from" and empty field should not be shown. There is no reason to manually enter a point when filtering by some other data which is already entered. The blank field is confusing for the user. Can it be hidden or something?

http://drupal.org/files/prox.jpg

CommentFileSizeAuthor
#8 exposed-current-user-1887122.patch653 bytesBrandonian
prox.jpg49.34 KBIWasBornToWin

Comments

IWasBornToWin’s picture

IWasBornToWin commented
Title: Manual field shouldn't show when filtering by anything except manual input » Distance filter not working when exposed, asking for manual input of origin.

Actually just noticed exposed filter isn't working if user changes the distance then clicks "apply", maybe because the blank field isn't being filled in? Buy again, shouldn't need blank field. I'm changing title of this issue

IWasBornToWin’s picture

IWasBornToWin commented

?

IWasBornToWin’s picture

IWasBornToWin commented

Would really appreciate an answer. I'm currently out of commission after attempting to rebuild my views.

Thanks

IWasBornToWin’s picture

IWasBornToWin commented
Category: feature » bug
Priority: Normal » Major

I expect you will have an issue with me changing the priority. But hopefully no more than I have an issue with getting an answer, sorry. Would really appreciate some help. Thanks

IWasBornToWin’s picture

IWasBornToWin commented

Bump

mototribe’s picture

mototribe commented

I was running into the same issue:
when selecting the "current user" as the origin point it shows the first page of the view correctly (in my case of other users closeby).
However, when I click to the next page it's all incorrect, showing random users from all over the place.
Or if I change the radius the same thing happens.
Also, I wouldn't expect the exposed filter for the "from" field to show. Or at least populate it with the current user's location and then allow overwriting it.

When I use "Geocoded Location" as the "origin point" it works fine. I'll probably just use ?field_geofield_distance[origin]= to pass in the location of the
current user as a work around until this page has been fixed.

IWasBornToWin’s picture

IWasBornToWin commented

Any help here please?

Brandonian’s picture

Brandonian commented
Priority: Major » Normal
Status: Active » Needs work
StatusFileSize
new exposed-current-user-1887122.patch653 bytes

@iwasborntowin, here's a quick patch that fixes the problem at hand. I haven't committed it yet because I'm not sure it's the best long-term solution for the module. The proximity element that comes bundled with geofield was originally conceived as a way to elegantly work with View's exposed filters, and as we've started to implement the widget itself with our proximity views, it's starting to look like we need some more polish on the element end to deal with the wider array of options than I initially expected.

IWasBornToWin’s picture

IWasBornToWin commented

Thanks, If I apply this patch, rebuild my views....will I need to do it again down the road?