Problem with geolocation (Use city local DB)

Message

EU e-Privacy Directive
This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.
View e-Privacy Directive Documents

Welcome, Guest
Please Login or Register. Lost Password?

(1 viewing) (1) Guest

Page: 1

TOPIC: Problem with geolocation (Use city local DB)

Forum Tools

#11440

Problem with geolocation (Use city local DB) 10 Years, 10 Months ago	Karma: 0
Hello, dear developer! I have a problem with your geolocation component JMS Multisites 1.3. Using the local database of cities and countries have not worked geolocation, detailed screenshots attached to the letter. Why is this happening? I hope for your help!

fgmedia

Fresh Boarder

Posts: 9

The administrator has disabled public write access.

#11443

Re: Problem with geolocation (Use city local DB) 10 Years, 10 Months ago	Karma: 54
I see that you didn't specified any sort ordering value. So you didn't specified that the slave site with the city must be analyzed before the one without city. Try using the sort field to specify in which order that you want to analyze the website. Also ensure that you are using the latest JMS version.

edwin2win

Moderator

Posts: 5370

The administrator has disabled public write access.

#11447

Re:Problem with geolocation (Use city local DB) 10 Years, 10 Months ago	Karma: 0
Geolocation problem only occurs with a local database of cities and countries. If you include only the local database of cities and countries, the geolocation is not working: If you turn on geolocation paid (Maxmind city key), the geolocation works: How to make a working geolocation using only a local database (Use city local DB)?

fgmedia

Fresh Boarder

Posts: 9

The administrator has disabled public write access.

#11457

Re:Problem with geolocation (Use city local DB) 10 Years, 10 Months ago	Karma: 54
If yuo compare the result with the free and the maxmind key, you can see that the city is not speeled the same way. The free, contain the first letter in uppercase and the paying DB has the first letter in lowercase. I think this is the reason why the matching fails. I will have a look to force the city field into lowercase to avoid such matching errors depending on the case sensitivity.

edwin2win

Moderator

Posts: 5370

The administrator has disabled public write access.

#11465

Re:Problem with geolocation (Use city local DB) 10 Years, 10 Months ago	Karma: 0
Okay, please do update the component to solve this problem with free local database.