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.Same problem with Proximity Filters as in version 1 for Drupal 8.
1) The first "Adresse" (boundary) for the user to enter a city.
2) The second "Distance" (proximity) based on the first exposed filter, so that the user selects a search radius.
If I enter 1 "Athis de l'Orne" and in 2 "50 km", the results are displayed for "Athis de l'Orne" but nothing is displayed in the radius of "50 km".
Why ?
I did the test on simplytest.me
I added :
- a node with the location (61100 Flers, France)
- a node with the location (61450 Banvou, France)
- a node with the location (14000 Caen, France)
My furthest node is 50 km away.
I enter the filter exposed address (61100 Flers, France). Only the point (61100 Flers, France) is displayed on the map.
If I add the distance 200 km, only the point (61100 Flers, France) is displayed.
Logically I should see the 3 points.
| Comment | File | Size | Author |
|---|---|---|---|
| #24 | 2936637-24-demo-schema-fix.patch | 211.83 KB | ChristianAdamski |
| |||
| #22 | 2936637-22-proximity-rework.patch | 212.36 KB | ChristianAdamski |
| #20 | 2936637-20-proximity-rework.patch | 212.57 KB | ChristianAdamski |
| #18 | 2936637-18-proximity-rework.patch | 207.58 KB | ChristianAdamski |
| #16 | 2936637-16-proximity-rework.patch | 207.79 KB | ChristianAdamski |
Comments
Comment #2
zenimagine CreditAttribution: zenimagine commentedComment #3
Manoj Raj.R CreditAttribution: Manoj Raj.R as a volunteer commentedAny Solutions for above filter question?
Comment #4
ChristianAdamski CreditAttribution: ChristianAdamski commentedComment #5
zenimagine CreditAttribution: zenimagine commentedComment #6
zenimagine CreditAttribution: zenimagine commentedComment #7
zenimagine CreditAttribution: zenimagine commentedComment #8
zenimagine CreditAttribution: zenimagine commentedThis problem severely limits the functionality of the module. Can not perform a proximity search with an address.
Proximity search has never worked with this module and it's a shame. Is it added ?
Comment #9
zenimagine CreditAttribution: zenimagine commentedDo you have a patch for this problem ? Thank you
Comment #10
tannerg CreditAttribution: tannerg at Acquia commentedThis is a serious limitation in my view as well.
I think this is the most requested feature for this and the geofield module.
It seems to work fine using the default value provided by the contextual filter - it is just that changing the source origin does not work. No matter what I put in the URL for the lat long center - the filter picks up my default value.
Comment #11
hsponner CreditAttribution: hsponner commentedAlso following this issue, really would appreciate this function.
Comment #12
ChristianAdamski CreditAttribution: ChristianAdamski commentedWith all due respect, you can always sponsor me, if this is so urgent. I am doing this in my spare time after all.
Comment #13
ChristianAdamski CreditAttribution: ChristianAdamski commentedThis got a bit large, but I won't break it up right now.
- moved proximity handling to Plugins
- introduced "nominatim" OSM Geocoder
- introduced separate ProximityFormField using viewsForm as opposed to ProximityField which does not
- fixed a lot of issues around geocoders
- multiple bugfixes along the way
TODO:
- can't test client location locally for lack of https right now
Comment #15
ChristianAdamski CreditAttribution: ChristianAdamski commented- lotsa schema fixes
Comment #16
ChristianAdamski CreditAttribution: ChristianAdamski commentedActual error in Proximity Argument
Comment #18
ChristianAdamski CreditAttribution: ChristianAdamski commentedArgument handling fixed.
Comment #20
ChristianAdamski CreditAttribution: ChristianAdamski commentedTest / demo view updated
Comment #22
ChristianAdamski CreditAttribution: ChristianAdamski commentedComment #24
ChristianAdamski CreditAttribution: ChristianAdamski commentedAhh. Accidentally added a google geocoder reference to demo/test view, which does not have google enabled.
Comment #26
ChristianAdamski CreditAttribution: ChristianAdamski commentedThis will cause a lot of fallout. I am sure a lot will break/broke. But the whole structure is much saner now and can be adapted much easier.
"Client location" needs a bit more love in #2879171: Proximity Field - Use HTML5 Geolocation as source
Comment #27
zenimagine CreditAttribution: zenimagine commentedExcellent news ;-)
What can be broken? the views ?
Comment #29
zenimagine CreditAttribution: zenimagine commentedComment #30
Rob230 CreditAttribution: Rob230 at CTI Digital for The Chartered Society of Physiotherapy commentedIs there any documentation for this? I was using the proximity filter in v1 of the module and it worked fine when setting the coordinates proximity_lat and proximity_lng (direct_input) pictured below. It would find how far the location field was from those hardcoded coordinates, and then the proximity field would be able to display the value.
In v3 it's completely broken. It has a huge number of options but none of them seem to work. From stepping through the code, center is never set when it's trying to find the proximity. Coordinates input causes some extra options to appear after you apply it, but any value entered is lost when saving.
Fixed coordinates causes some options to appear inside the location input list. But neither seems to actually set the center. In ViewProximityFilter $filter->value['center'] is always empty regardless of what I have configured and the proximity field pointing to that filter always shows 0 miles.
The documentation on https://www.drupal.org/docs/contributed-modules/geolocation-field/how-to... it seems to be explaining how to find the proximity to itself? Or I don't understand it. It doesn't make any sense. How do I get it to simply show the proximity of a field on the node to a hardcoded center point?