GeoIPv2 Beta version available

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.

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.

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

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

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

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

Is the new version better than the old also without premium account? Old version been working fine for me (VATMOSS compliance – need only to get the country, but that please as correct as possible)

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.

Hi,

I had my first user update to this… and instantly file a support request, because their GeoIP detection stopped working. In fact, everything was fine – but they had not understood that they needed to immediately do a fresh database download after installing.

Suggestion: either schedule the database update immediately, or just carry it out immediately, upon the update. Otherwise, people are either not going to know why their GeoIP detection stopped working, or they will be unaware of it and things on their sites will break.

David

P.S. Congratulations and thank you for updating to the modern API!

okay – thanks for the answer – will update soon then.

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.