Benjamin Pick

Not sure if I understand the config rule correctly. Does it change the header X-Forwarded-For? I always thought reverse proxies do this by default.

(BTW the plugin already supports multiple reverse proxies, e.g. if your varnish would be behind a Cloudflare setup, HOWEVER this is not exposed to the options UI yet.)

Now that there are several data sources, the answer is “it depends”.

If you use the default hostip.info-Source, then yes, each detection requests takes around 0.6s because it has to do a Web lookup. If you use a file-based lookup (the automatic or manual option) it’s less then 10ms, so no significant impact to the performance.

Soon I will release v2.4.0 with caching per IP for the Web APIs, and it will also include support for the Maxmind Web APIs.

You are probably using PHP < 5.3, which is not supported for the 2.x-Versions of this plugin. (Of course the plugin should tell you this in a nicer way, but that’s another story.)

No the Plugin treats all pages equally. I suppose it is interfering with some theme or plugin function of your installation, you can try it out by deactivating plugins / using the standard wordpress theme.

Cron probably will try to update (the same file) automatically – which made me realise that nothing currently prevents concurrency issues (ie 2 processes writing the same file at the same time). Will try to fix that for the next version.

I won’t support multisite as I don’t have experience with it but if somebody writes a pull request (if possible, also some unit tests), I will be happy to merge it.

Yes I will change that to a link in the next version.

Hm for me the interesting part would have been “at the end of the process it through up some PHP syntax error” because obviously it shouldn’t do that. If it is possible for you could you try to find out what exactly it was?

Yes, when the plugin is disabled the plugin function calls throw an “Function not found”-error – you would have to check with function_exists first to avoid it.

Good question I never tried. Probably not because the uploads folder are different for each subsite. (Note to self: how would cron update work?)

Hm I agree the plugin should show clearer that a user intervention is necessary. Of course it’s also written in the Documentation but not 100% will read it. Doing something “on update” is not so easy (https://make.www.ads-software.com/core/2010/10/27/plugin-activation-hooks-no-longer-fire-for-updates/), but maybe worth it.

I didn’t make a comparison of how much the two databases differ, but I guess they are roughly the same as they are both still updated monthly. If you don’t need the new API you don’t need to update, but there won’t be any updates for v1 anymore. And possibly Maxmind will stop supplying updates to the old API data at some point.

Stable version is being released now. Hope there are not too many glitches left …

@steliodj :

No there is no mailinglist but you can subscribe to my SVN commits (Plugin Tab Developers) – I only commit when releasing a new version as the development happens @ github.

This is probably due to another plugin which also uses Maxmind GeoIP.

However there will be a completly new version of this plugin very soon (which does not suffer from this problem because the necessary classes are auto-loaded). Try it here:

https://www.ads-software.com/support/topic/geoipv2-beta-version-available?replies=5#post-6410588

* Fixing isEmpty not defined
* Fixing shortcode error message when isEmpty.

https://github.com/yellowtree/wp-geoip-detect/archive/v2.0.0-rc4.zip

I am guessing: are you developing on a machine that does not have internet access? If not, what is your IP? The results you get have errors because he didn’t find any data attached to this IP, and normally, if it is a local IP, he tries to get his Internet IP first (which of course only works if you are connected to the internet.) This should not be an issue for web servers, but only for development boxes.

EDIT: I have fixed the error message to say “<!– GeoIP Detect: No information found for this IP (127.0.0.1) –>” instead.