Benjamin Pick

Are you using the PHP API, the shortcodes, page cache, AJAX mode … how is it configured on your site. There are many different ways of using this plugin.

Bypass / Override: It is always a good idea to allow the user to bypass the IP detection, because you might have clients travelling to a different location (e.g. US client travelling to Australia, interested to see the US site), or the IP detection might be wrong. If you are using AJAX mode, I am working on making this a lot easier: https://github.com/yellowtree/geoip-detect/issues/94

In theory this should work, you could try the geonameId of Ontario instead:
https://www.ip2location.com/free/geoname-id

If you have an IP that has “Ontario” as region, let me know, then I can check it myself.

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

Dear Richyaus,
I do not understand your usecase … Can you explain how you are using this plugin, please?

You might be interested in this plugin instead:
https://www.ads-software.com/plugins/iq-block-country/
https://www.ads-software.com/plugins/ip2location-country-blocker/

For more information about my support policy, see
https://www.ads-software.com/support/topic/community-support-here-and-where-to-get-paid-support/

I’m interested for auto-deletion, too (in order to implement the GDPR “right to be forgotten).

This plugin seems to be doing it already (but of course it also does a lot of other stuff): https://www.ads-software.com/plugins/gdpr-framework/

This plugin seems more approriate but abandoned:
https://www.ads-software.com/plugins/inazo-flamingo-automatically-delete-old-messages/

The question is – how do you want to detect that this is a “first visit” ? By the cookie that is set by the AJAX function? By the referer (previous site) that is outside your domain (e.g. Google)?

Probably 90.XXX.XXX.XXX is not in the database of hostip.info, you can try on their website: https://hostip.info/

Which datasource are you using? Do you get information for the IP 8.8.8.8?

In 4.2.2, it works the same as in 4.1, it just shows a warning message on the plugin page. You can dismiss that warning once you’ve read it.

Yes I understand, this is not user-friendly, and I would love to find a solution that is easier.

I wrote up the technical background to the problem here:
https://www.ads-software.com/support/topic/maxmind-lib-incompabilities-meta-ticket/#post-14670970

The issue is tricky because every plugin potentially influences the code of the other plugins, and in this case this happens often, as this library is installed via composer and composer is not meant to be used seperately in every plugin. Typo3 is solving this by using a installation-wide composer set up (so that composer would complain at install time that two different version of the same Maxmind library are required by 2 different plugins).

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

The automatic deactivation has been removed in the Hotfix update 4.2.1 now.

See my reply there …
https://www.ads-software.com/support/topic/maxmind-lib-incompabilities-meta-ticket/

What my plugin is doing is checking whole wordpress install if there are other plugins that are using the Maxmind libraries as well, and if so, check via MD5 if their plugin is using the same version of the files as my plugin.

The reason for this is that every month or so I get bug report that somehow the Maxmind source is not working, and some users don’t know which other plugin is also using the Maxmind libraries because they don’t use that feature. These notice should reduce the debugging effort of these cases, and alert to this issue pro-actively (because the problem can arise anytime one of the plugins decides to update their files).

Maybe I should make these notices less visible (trying to show them only in case of error, and on a “troubleshooting” page)?

The problem is that there are at least 20 wordpress plugins that are using Maxmind libraries, often using different versions, some are compatible with each other, some not. I tried to automate this detection with 4.2.0 but obviously, the detection was to strict – as both files from wordfence are loaded, it works again. In 4.2.1 (that is about to be released), I left the admin notice, but removed the “automatic deactivation” of the lookup from the GeoIP plugin.

The problem is also whether it works or not depends also on the plugion loading order, which depends somehow on which plugin you activated first. So it’s hard for me to test every possibility. Thank you for your bug reports.

I have released 4.2.0-beta7 now, this shortcode works now:

[geoip_detect2_property_extra__flag]

See the updated documentation:

https://github.com/yellowtree/geoip-detect/wiki/API%3A-Shortcodes-for-Contact-Form-7#insert-the-geoinfos-of-the-user-into-the-email-text

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