Fatal error: Cannot redeclare geoip_country_code_by_name() when PHP geoip extension is enabled about geoip-api-php

[oschwald]

Thanks for the report. How did you install the API? We already list the extension as a conflict in the composer.json file.

[daigo75]

I'm not sure I understand the question correctly. I included the API (geop.inc etc) in a small software that I then package and distribute. The GeoIP library is included using Composer, but I can't predict if the environment where the package will be installed will contain the geoip php extension or not.

Please note that, when my package is installed, Composer is not used to update the dependencies (nor it should be). Vendor libraries, including GeoIP, are simply included in the package, which is then just unzipped and executed "as is".

[oschwald]

Couldn't you check if the function exists before you load geoip.inc?

[daigo75]

geoip.inc is loaded automatically by Composer, I don't have control over it. Also, that would not be a good workaround, because several, but not all of functions declared in geoip.inc match ones existing in geoip php extension.

A better workaround, which is what I've done at the moment, if check for the existence of every single function in geoip.inc. This, however, is still rough and far from optimal. A better solution would be replacing global functions with classes, or using namespaces. I understand that this would have the side effect of breaking compatibility with previous interfaces, but global functions are a legacy solution anyway and I don't think it makes sense to support PHP 4 anymore (Composer requires PHP 5.3 anyway).

[oschwald]

We won't be redesigning the interface of this library as we are in the process of releasing a more modern GeoIP2 library, https://github.com/maxmind/GeoIP2-php.

We might consider merging a pull request with your other solution, but we would need to look at it more closely.

[daigo75]

I saw the GeoIP2 library, I will probably switch to it when it will be ready.

Regarding the pull request, I don't think it would be necessary. I definitely don't recommend the solution I adopted, which is just an ugly hack that I put in place because I needed a solution quickly to prevent it from crashing my software.

Unfortunately, I don't see a reliable way to fix the incompatibility without a redesign. The geoip php extension offers some, but not all of the features of the GeoIP library (at least, not according to the documentation). Therefore, in their current status, a simply "one or the other" is the wrong logic and it won't work in many cases. If the two were fully overlapping, and providing the exact same functionalities, then it would be possible to add a simple check at the beginning of geoip.inc, such as:

if(extension_loaded('geoip')) {
  // geoip php extension loaded, don't load this library
return;
}

Since that is not the case, skipping the geoip.inc altogether in the presence of the php extension could cause unpredictable results.

[oschwald]

Given that we don't have control over the extension and the extension has a different API, we are unable to fix this. The extension is already marked as conflicting in the composer.json file. If you want seamless transition between a C extension and a pure PHP implementation, we suggest that you use GeoIP2.

[TokyoDesu]

i can solved this problem i Got to my CPanel Choose version of PHP and select the actual and disable in the options geoip extension.

Now all work good =).

Only need check your hosting cpanel or if you have a vps only change your php.ini