Nice module .. you just saved me from writing the exact same thing myself (which I was about to do).

But why aren't you referencing the IP2CC module instead of requiring us to download the same list of codes from the same source again?

http://drupal.org/project/ip2cc

Comments

jboukes’s picture

jboukes commented

Hi Mr. J,

The why is - likely because I didn't stumble upon it when googling if other country ban modules had been already created ;) I think what I can look into is see about renaming the country ban ip_to_country table to be the same as what the IP2CC module uses. This way, if you've installed the table already via IP2CC, there will not be a need to create the table again - and vice versa of course.

All for now,

--JB

mr.j’s picture

mr.j commented

All good!

mr.j’s picture

mr.j commented

I fixed this one myself by making a dependency on ip2cc and country_api modules.

See here
#942232: Much improved version of this module

jboukes’s picture

jboukes commented
Status: Active » Closed (fixed)

The dependencies are now 'official' as of 1.3. However, I opted to use IP-based Determination of a Visitor's Country instead of IP to Country. I like how this new module uses ARIN for its IP source, and also allows the user to select other source options. In addition, it appears webhosting.info (which IP to Country and the old version of Country Ban used) is no longer updating its IP list. The last update as of this comment was December 14 2010.