IP Location Block 0.2.2.1 isn’t so attractive for you because there’s no new feature except several bug fixes, but it includes a very important alteration related to the IP address geolocation API for local databases of Maxmind and IP2Location.
In this changelog, I’ll mention about it.
Replacement of the directory for local databases
In the previous version, geolocation database files are located at as follows:
With this configuration, the Maxmind DBs will always be removed and downloaded at every upgrading of this plugin.
Now, those DBs can be placed outside this plugin e.g.
wp-content/ip-geo-api/ to cut the above useless process. And also cooperation with IP2Location plugins such as IP2Location Tags, IP2Location Variables, IP2Location Country Blocker had been deprecated.
Additionally, the class libraries for DBs can be put together under that directory. It means that the class libraries and DBs have become independent of this plugin. You can also get them from WordPress-IP-Geo-API separately from this plug.
Filter hook for DBs
The following filter hooks can be used to customize the settings of your DBs around.
Full path to the class libraries and local DB files.
Full path where Maxmind GeoLite DB files should be saved.
Full path where IP2Location LITE DB files should be saved.
Full path to IP2Location LITE DB file (IPv4).
And here is a sample code how to use these.
You should always deactivate then activate again when you change your settings.
You can check your configuration for DBs at this plugin’s option page.
Don’t you need different types of DBs?
In my observation on coverage for IPv6, Maxmind is better than IP2Location. In any case, the coverage of each DB might be limited by their own data sources. So I think something fallback might be needed.
If you don’t want one of these, please remove
ip-geo-api/ip2location and this plugin would not download its DB files any more.