Hey there.
Firstly, thanks for the useful module. (I am just a user btw)
I get the notifficayion in Status Report:
Old GeoPHP Library
GeoPHP library version 1.0 was found, but you are running an old version. GeoPHP version 1.1 is bundled with this module. Please either remove or update your older version of geoPHP found at sites/all/modules/geophp/geoPHP/geoPHP.inc. The newest version of geoPHP can be found at https://github.com/downloads/phayes/geoPHP/geoPHP.tar.gz.
What I am doing is:
If I remove /sites/all/modules/geophp/geoPHP folder or /sites/all/modules/geophp/geoPHP/geoPHP.inc file, the site gives error. If I update it from https://github.com/downloads/phayes/geoPHP/geoPHP.tar.gz, the notification above doesn't change.
I know this is not too much important, but i am writing just in case.
Cheers,
Duru.
Comments
Comment #0.0
durum commentedSee edit note in the message body.
Comment #1
netbek commentedIn your /sites/all/libraries directory, is there a geophp directory? If so, it should probably be deleted. The GeoPHP library is bundled with this module and you should use it instead. You don't need the one from Github.
Comment #2
robcarrI haven't got a /geophp directory under /sites/all/libraries. I still see the error message: if I inspect
function version()in geophp.inc then the bundled file is version 1.0. If I follow the link to download the archive from Github, that - too - is Version 1.0.So is there a version 1.1 in existence anywhere, or is this a bug? Sensing the latter, so changed the issue Category to a bug report.
Comment #3
phayes commentedbah,
I forgot to update the geoPHP library's version string when I did the 1.1 release. my fault.
Comment #4
robcarrThought it was finger trouble...
So I just 'edited' my version of geophp.inc [taken from the GitHub download) to change the version number to 1.1 (line 38). It then generated an error because one of the library include files was missing. Copying the directory '/lib' from the downloaded archive across into the sites/all/modules/geophp/geophp directory. Then the problem was sorted.
Comment #5
phayes commentedThis should now be fixed in the latest dev snapshot.
Comment #6
mgiffordSeems to work in dev now, thanks!
Comment #8
deanflory commentedYes, newest dev corrected the issue, felt like I was going crazy.
Comment #8.0
deanflory commentedFalse alarm for no error.