Postponed
Project:
Ad GeoIP
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
24 Feb 2009 at 23:06 UTC
Updated:
17 Apr 2009 at 16:36 UTC
Jump to comment: Most recent file
Comments
Comment #1
webchickAnd the answer appears to be... no, not easily. ;)
The first problem is there's no geoip_db_avail() function when you go this route. If I create one manually when that function doesn't exist, something still isn't working quite right because it's not saving the country association.
Here's a very incomplete and terribly crappy patch, but possibly something to start from.
Comment #2
webchickOooo. I just found http://drupal.org/project/geoip tonight. This is a much better idea. Basically, remove all of the stuff about checking GeoIP to see if it's installed, maintaining state, etc. and leave it to GeoIP API module to figure out. This module need only worry about the Ad -> GeoIP integration.
The only problem is that the module doesn't yet support city/region levels, which this module does. For my purposes, Country is fine-grained enough, so I'll try and get something working and post back here.
Comment #3
jeremy commentedI'm certainly not opposed to seeing the ad_geoip module properly integrated with the geoip module. A couple potential issues:
Once these two issues are solved, I'm all for moving forward with this.
Comment #4
webchickWell, even though the project page says country only, http://drupal.org/node/383086 implies city support was committed, although I admit to not having looked at the code since whenever I posted that issue. :)
Might be worth a look. Also my experience with Roger is he's a very responsive maintainer who would gladly accept patches.
Comment #5
jeremy commentedGreat! It's not clear to me if it also supports the commercial offerings (which are more accurate). And equally important, I do not yet see a solution for my performance concerns: we need to filter/serve advertisements without bootstrapping Drupal.
I'm not opposed to this idea, but it's not a project I'm likely to take on anytime soon as what we currently have works well for my current needs. Sorry. I'm moving into a postponed state, awaiting a patch that addresses all of these concerns.