Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
I have problems getting the module installed. Drupal would not let me activate it at all and I always get the message: The GeoIP database file is missing or not configured. Download the latest file at ...
Comment | File | Size | Author |
---|---|---|---|
#5 | geoip-fix-module-install-2404869-5.patch | 817 bytes | netdreamer |
Comments
Comment #1
aagd CreditAttribution: aagd commentedComment #2
aagd CreditAttribution: aagd commentedComment #3
tezalsec CreditAttribution: tezalsec commentedSame here.
Checks for values in variables_get in install file while variables were never set and dont exist ;-/
Quite a critical bug, install file seems not tested and for two months no reply on previous comment.. too bad.
Comment #4
tezalsec CreditAttribution: tezalsec commentedGot it to work by just creating the variable or executing the following php code somewhere, then install module again.
variable_set('geoip_data_file', 'sites/all/libraries/geoip/GeoLiteCity.dat');
(possibly your .dat file has a different name, change accordingly)
Comment #5
netdreamer CreditAttribution: netdreamer commentedThere is no need to force a specific value for the variable by hand: the problem is in the implementation of the geoip_requirements(), that is too much restrictive on the initial phase.
I fixed it with a small patch that lowers severity requirements for the missing GeoIP DB file to Informational (now it was Error) while on the install phase, so that it can later be set with the standard module admin GUI.
Comment #6
tezalsec CreditAttribution: tezalsec commentedThat should do it, thanks!
Comment #7
saveva CreditAttribution: saveva commentedThe netdreamer patch didn't work for me! The problem resides in the variable_get for geoip_data_file. Once you configure a default value there things run smoothly.
Code change needed on line 50 of geoip.install:
Comment #9
das-peter CreditAttribution: das-peter at Cando commentedJust pushed a mixed fix.
The check now only runs during runtime. I don't thing it makes sense earlier - no matter what severity would be reported.