Problems with location search

Hi @ziegel1976, thank you for getting in touch.

Directorist provides the option to enter the location in two forms. One is the Location taxonomy, that’s the one you’re talking about here. Another one is the Location API, which basically takes an address as an input, and gets the address using either OpenStreetMap API (this is the default) or using GoogleMap API.
For these two types of locations, the Location field on the Search Bar also has two options. You can either search using the Location API or you can search using the Location Taxonomy. One doesn’t work with another. For example, you have a listing in which Location Taxonomy is set to London but when searching, you’re searching London using the Location API field, so it won’t work. You’ll have to either change the field to Location Taxonomy or search using the Address that is listed on that particular listing. Location API also comes with the Radius Search Feature. You can search for an address and then set the Radius to let’s say 50 miles, any listings that are within that 50-mile radius of that particular address can be seen.

You can change the type of Location Search from Directory Builder > Search Form Layout.

Hope this clears up any confusion. Let me know if there’s anything else I can help you with.

Regards,
Mahdi.

This makes perfect sense and works as you’ve described. Great, thanks!

One suggestion though for the default configuration of your sample dataset:
– either you could set the location source on search form by default to “Location Taxonomy”
OR
– you could properly configure the entries in the sample dataset, so they really point to the city which category they are assigned to.

Currently, in the default dataset you have discrepancies like:
– “All American Lock and Key” is pointed on the map to New York, but in the taxonomy it’s set to “london”

Maybe it would be worth to submit a change request to your product development team. I promise that it will help to cut down on your support requests volume (not even speaking of those potential customers who will just ignore your plugin because of this little nuisance.

In any case, you’ve helped me great and I really appreciate your explanations.

Hi @ziegel1976, it’s my pleasure to help you.

Thanks for the suggestion, it makes perfect sense to make the default data more continuous. I’ll be sure to pass it to the relevant team.

Regards,
Mahdi.