Benjamin Pick

API Change: It is now $record->isEmpty instead of $record->traits->isEmpty.
Documentation is on Github (but could need some format love. Volunteers welcome).

https://github.com/yellowtree/wp-geoip-detect/archive/2.0.0-rc3.zip

This is nice but shortcodes will change in v2 as well.

Yes this will be possible with Version 2.0. Please try out the Beta/RC and tell me if you find any issues. Status currently is “for me it works but API may still change slightly.”

Update:

* New shortcode ([geoip_detect2 property="country" lang="de" default="default value"] -> needs documentation)
* Some minor API changes (see migration guide). Instead of NULL, an empty object is now returned. Not sure if the attribute isEmpty stays.
* Change update schedule to match when the database is actually updated once a month.

https://github.com/yellowtree/wp-geoip-detect/archive/2.0.0-rc2.zip

Remaining TODOs:
– Document Functions and Shortcode on Github Pages
– Test cron update again
– Comment out isEmpty until Maxmind tells me if such a extension is possible/desirable

I would appreciate feedback before releasing it as update.

Just released a Release Candidate:

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

The standard behaviour now is to use the site locale as language if possible, english otherwise.

The data already includes city coding, but this is not available for every IP. You could try on their website if their Pro data includes it more often. But in any case you can’t rely on it (e.g. mobile networks often have more than 50km off).

It is only visible when a Proxy Header (HTTP_X_FORWARDED_FOR) is detected. Does your reverse proxy use a different header name?

(Oh and there is no seperate settings screen. You have to go to Tools > GeoIP Detection.)

See https://www.maxmind.com/en/ipv6 :
In theory Legacy supports IPv6, but the normal GeoLite database doesn’t contain the data. (It is a seperate file and seperate function calls, so I didn’t support it.)

In this plugin version, both v4 and v6 should work.

There is a first beta version (aka could possibly work, but still needs polishing):

https://github.com/yellowtree/wp-geoip-detect/archive/2.0-beta1.zip

Known Issues:
– Backend debug console needs to output the new function
– Migration notes need more info about the update (https://github.com/yellowtree/wp-geoip-detect/wiki/How-to-migrate-from-v1-to-v2)

You can try and replace the plugin (legacy functions should still work) and then try out the new function.

Bug reports and pull requests are welcome.

Version 1.8 was now released.

Version 1.8 was now released.

I have added reverse proxy support now. Please try the development version:

https://github.com/yellowtree/wp-geoip-detect/archive/master.zip

You will have to enable it in the options.

Oh, does your server use a reverse proxy?

(How to find out: look at var_dump($_SERVER) and tell me which array key contains your IP.)

Hi Greg,

thanks for your interest. I am hoping to finish v2 support end of this year. Paid Web Service should follow soon, and paid database file when I have found access (or demo) to try the auto-update.

The Plugin already looks at the /uploads/-Folder as-is:
https://github.com/yellowtree/wp-geoip-detect/blob/master/updater.php#L15

There seem to be going on something else: the plugin “ised” also includes the Geoip library because this is where you get your error from.