haven't tried this module yet. From its description, it seems that it only supports the GeoLite *Country*, but not the GeoLite *City* (free) DB. Is that true? If so, are you planning to support this DB as well?



I got the GeoLiteCity database to work with the geoip dev version by downloading the GeoLiteCity.dat file and then setting the path to that on the admin page. Then your custom module can just use geoip_city() to get the location as an object.

Btw, here's a link to a patch I made for location module's views handler that enables one to filter views results by proximity to the visitor's ip address: http://drupal.org/node/820116

Thank you - sounds nice. Does that mean that the GeoLiteCity.dat file is not supported by GeoIP API 6.x-1.1 (released on 19 May 2010), but by the dev version rolled out 2 days later than the official release?

Subscribing. I have a forked version of the Zipcode Redirect module that uses this database.

I may try to make my version of Zipcode Redirect depend on this, so I can support your effort.



Subscribing as well. I'm going to try your patch david as that is exactly what I am looking to do.


Status:Active» Fixed

There's already a geoip_city() function in module. I'm assuming people just didn't test it? If you encounter problems with it please open a bug report.

Thanks - so could you please add this information to the project's page? Currently, it is only stated that it supports the GeoLite Country DB.

Component:Code» Documentation
Category:feature» task
Status:Fixed» Active

Yes, that was my issue as well - that it wasn't stated on the project page. I hadn't installed the module yet since I was trying to evaluate whether I should build a custom module of my own off of it.

Title:Support for the GeoLite City databaseDocument that the GeoLite City database is supported

I'd already updated the project page: http://drupal.org/project/geoip is that sufficient?

Status:Active» Fixed

Looks good. Thanks.

Yes, now it's 100% clear - thanks!

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.