Benjamin Pick

Ok great! Thanks for your patience!

Yes wordpress saves the plugin options even when you disable the plugin. You can change the data source manually by entering the url <your-server.com>/wp-admin/options.php and setting geoip-detect-source to hostinfo.

Can you try again with Beta5, please? Also, please let me know if you see any additional error message (as I have added a few error conditions).

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

Oh, the Github Updater plugin changed – I will need to remove that method then.
The second method should work fine, just click on “continue” …

Hi, I have made a change, can you please try the newest beta ?
https://github.com/yellowtree/geoip-detect/wiki/Beta-Testing

Did I get it right that the notice appeared after you saved the Maxmind API key?

Is the Maxmind automatic update source working for you?

This is a weird notice that I haven’t seen before, let me know if you have any idea how I could reproduce it … he seems to try to open a file that is actually a directory, but why?

Thanks – this was fixed already:
https://www.ads-software.com/support/topic/getting-external-ip-throws-a-php-notice/
So it will go away when I release the next version of the plugin.

[geoip_detect2_show_if country=””] Some Content [/geoip_detect2_show_if] should work in the current beta (4.3.0-beta3), can you have a try?

https://github.com/yellowtree/geoip-detect/wiki/Beta-Testing

I realized that empty parameter values were ignored before, accounting for the weird behaviour that you saw.

Thanks, you are right – they stopped the API on Nov, 10 :

https://whatismyipaddress.com/api

I will remove it from the next version from the plugin. The lookup should still work because it should fall back to another service.

Behaviour – do you mean, the plugin is not executed?

The AWS documentation says:
If you choose the Whitelist option, each header that you add to the list becomes part of the cache key for the URLs associated with the distribution. Adding a header to the list simply tells CloudFront that the value of the header can affect the content returned by the origin server.

You could use AJAX mode so that caching the HTML is not a problem. AFAIK the AJAX requests are not cached (they shouldn’t be but please check in the headers if that is the case).

When using the header print, which value do you get for $_SERVER['CloudFront-Viewer-Country'], my test case has de (lower-case 2-letter iso code) ?

• This reply was modified 3 years, 4 months ago by Benjamin Pick.

Ok yes …

There is another problem – of course AWS might change these IP ranges anytime. So I guess I have to add downloading the file and updating these ranges to the plugin … I have added this as a feature request:

https://github.com/yellowtree/geoip-detect/issues/160

Hi lucianodefranco,

oh, that’s because 172.26.26.89 as an internal IP is not whitelisted yet…

Can you add
10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16
to the list and see if it works then?
I might add an option for this in future versions of the plugin, but adding these ranges should work for you.

Yes you observed correctly – adding a reverse proxy changes the behavior. Because by default, if no whitelist is there, the first proxy is assumed as reverse proxy – but in your case, there are two reverse proxy, so you need to specify them.

[geoip_detect2_show_if country=””] Some Content [/geoip_detect2_show_if]

is working for me. Here is a test case, it should show Empty in all three lines:

Country empty or not?: [geoip_detect2_show_if country=""]Empty[else]Not Empty[/geoip_detect2_show_if]
Country empty or not?: [geoip_detect2_hide_if country=""]Not Empty[else]Empty[/geoip_detect2_hide_if]
Country empty or not?: [geoip_detect2_show_if property="isEmpty" value="1"]Empty[else]Not Empty[/geoip_detect2_show_if]

Can you tell me:
– Are you using AJAX mode?
– Which IP did you test? You can send it to my Email if you want, wp-geoip-detect posteo de