Address search differences between V1 & V2
This topic contains 7 replies, has 4 voices, and was last updated by Alex Rollin 6 years, 6 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketTagged: search
-
AuthorPosts
-
April 30, 2019 at 12:18 pm #483666
Hi, in GD V1 the address search was very powerful and could find pretty much anything in Google Maps quickly – including landmarks, building names, restaurants, etc. Then it was easy to adjust the pin manually if needed.
The search box in V2 seems limited in that it only finds proper street addresses in the auto-complete, so you can’t just type a (for example) restaurant name and have the map automatically zoom to that location.
Is this a known issue, or is there perhaps some modification I can make to get the search back to V1 functionality?
Thanks for any assistance
April 30, 2019 at 4:59 pm #483746Hi,
no, we are not aware of what you describe.
The search engine of V2 is more powerful than the search engine of V1.
Please share a link and make an example.
Thanks
April 30, 2019 at 7:58 pm #483810Hi, uh sorry I see my mistake
We first built our listing site with Listify, then we rebuilt it in GD V1 then V2
I was confusing the location lookup in Listify with GD V1.
So to rephrase the question:
When creating a new listing, is there any way to have a full text location lookup like the way Listify does it? it makes finding locations so much faster, so if I’m looking for “Big Ben London” I just type that and it appears as an option.
With GD it seems the person listing has to know the address first, and often addresses don’t match up with landmarks correctly, that makes for a lot more map moving around to get the pin located.
You can see a demo of the way listify vs GD handling of location lookups here: https://drive.google.com/open?id=10VFhtOGlWPjMYWnuN8JTDUGdAn504Udv
May 1, 2019 at 12:59 pm #483956On https://developers.google.com/maps/documentation/javascript/examples/places-autocomplete
it looks like this is the difference between setting autocomplete to “All” instead of “Address”
Is it possible to change this in GD to bring back all results?
May 1, 2019 at 3:27 pm #483999Hi!
We have a task to look into this. If memory serves the address information that was returned was less complete but we will have another look to see if it is something we can do in a future version. For now it would be a customization to undertake yourself or with support from a freelancer.
May 1, 2019 at 4:21 pm #484009The way we have it “types: [‘geocode’]” returns the most consistent addresses, in some areas other options miss out region info, this is why we have it this way.
In next release you will be able to use this filter to remove or change it
goedir_lm_autofill_address_types
example
remove (which sets to all)add_filter("goedir_lm_autofill_address_types","__return_empty_string");or set a specific one
add_filter("goedir_lm_autofill_address_types","_my_lm_address_type"); function _my_lm_address_type($type){ return "types: ['establishment'],"; }Thanks,
Stiofan
May 3, 2019 at 1:45 pm #484322thanks for the feedback
I have commented line 1137 in geodir_location_manager/includes/custom-functions
The search is now bringing back all results – great!
Seems to work ok for my tests so I’ll keep it for now
Will look out for the new version
Cheers
May 3, 2019 at 9:16 pm #484407If you make changes to the plugin files they will be overwritten on updates.
The snippets can be added with the code snippets plugin.
When you add them with the plugin they will persist across updates.
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket