crashes since update

It could be an issue with PHP 8.1 – it’s always a risk running such a recent version of PHP with WordPress as many plugins won’t taken 8.1 into account. It’s far stricter.

We need to see the exact error:
– try and find a PHP error log somewhere for your system. Your host could point you in the right direction. It may just be “error_log” in the root public HTML directory.
– you may have received an email from WordPress itself outlining the error?

I’m going to quickly test the plugin on 8.1 to see if I can reproduce it regardless.

After testing PHP 8.1 I can’t reproduce any fatal errors to crash page loading. Perhaps there’s a conflict with another plugin somewhere along the way.

Definitely going to need to see what error is being generated on your particular site…

Also, did you try removing and reinstalling the latest verison incase the upgrade didn’t complete successfully the first time around. Rare enough, but it can happen on WordPress easily enough.

• This reply was modified 2 years, 9 months ago by Paul.

Thanks for looking into it! I’ll check the logs and get back to you! Many thanks for your help.

Fatal error: Uncaught TypeError: Argument 1 passed to MaxMind\Db\Reader::getWithPrefixLen() must be of the type string, null given, called in xxx/wp-content/plugins/geoip-detect/vendor/geoip2/geoip2/src/Database/Reader.php on line 246 and defined in xxx/wp-content/plugins/woocommerce/vendor/maxmind-db/reader/src/MaxMind/Db/Reader.php:149 Stack trace: #0 xxx/wp-content/plugins/geoip-detect/vendor/geoip2/geoip2/src/Database/Reader.php(246): MaxMind\Db\Reader->getWithPrefixLen(NULL) #1 xxx/wp-content/plugins/geoip-detect/vendor/geoip2/geoip2/src/Database/Reader.php(217): GeoIp2\Database\Reader->getRecord(‘Country’, ‘Country’, NULL) #2 xxx/wp-content/plugins/geoip-detect/vendor/geoip2/geoip2/src/Database/Reader.php(90): GeoIp2\Database\Reader->modelFor(‘Country’, ‘Country’, NULL) #3 xxx/wp-conten in xxx/wp-content/plugins/woocommerce/vendor/maxmind-db/reader/src/MaxMind/Db/Reader.php on line 149

Es gab einen kritischen Fehler auf deiner Website.

• This reply was modified 2 years, 9 months ago by Anonymous User 15325940.

That’s what I got from using WP-Debug on. Does that help? I can try to get the php error log as well if that helps

It appears to be a clash between 2 different plugins that have the same library installed, but different version of the library. So your “GeoIP Detect” library has a different version than ours so there’s a fatal error because the way of calling the library is different.

I’ll take a look and see if I can work around it. I’m not sure it’ll be possible…

Thanks, I appreciate it. Interestingly, it worked in the previous versions (<3.0), maybe that helps.

I’ve just released v3.1.0 which will hopefully solve this error altogether. Not only that, it’ll use the API which that plugin actually provides, in order to get the Geolocation data, instead of trying to do it itself. Quite a useful plugin there.

Thanks again for providing the error for me to be able to fix this!

Hi Paul, many thanks for your work! I have updated your plugin to 3.1.0, but still get an error:

Fatal error: Uncaught TypeError: Argument 1 passed to geoip_detect2_get_info_from_ip() must be of the type string, null given, called in /xxx/wp-content/plugins/custom-content-by-country/src/icwp-ccbc-processor.php on line 272 and defined in /xxx/wp-content/plugins/geoip-detect/api.php:44 Stack trace: #0 /xxx/wp-content/plugins/custom-content-by-country/src/icwp-ccbc-processor.php(272): geoip_detect2_get_info_from_ip(NULL) #1 /xxx/wp-content/plugins/custom-content-by-country/src/icwp-ccbc-processor.php(171): ICWP_CCBC_Processor_GeoLocation->getVisitorCountryCode() #2 /xxx/wp-includes/shortcodes.php(356): ICWP_CCBC_Processor_GeoLocation->sc_printContentByCountry(Array, ‘<span style=”co…’, ‘CBC’) #3 [internal function]: do_shortcode_tag(Array) #4 /xxx/wp-includes/shortcodes.php(228): preg_replace_c in /xxx/wp-content/plugins/geoip-detect/api.php on line 44

Es gab einen kritischen Fehler auf deiner Website.

If you need any more information from my side, let me know!

Hi Paul, i had to contact you via this thread cause i dont know how to create a post or mention you, i have an issue with the plugin cloudfare-flexible-ssl, i was trying to see wich plugin was causing problems in my wordpress page and accidentally disabled the cloudflare plugin, after that i got logged out of the wp admin page, and when i tried to log back in with the same credentials it said that my username doesnt exist, this makes sense cause im trying to log in to admin with an admin user we created in the wp, not with a wp account. So i tried croquemadame.com.ar/wp-login and got the too many redirects error, i tried wp-login.php and it redirected me to an html of my web, but without any content,just the html, and couldt do anything in there. I tried creating new admins in myphpadmin but couldnt get in, i tried uninstalling all the plugins and that didnt solve the problem. So at last i read cloufare documentation and i see something about too many redirects, im thinking that this plugin its causing the problem, so, do you know how to enable it again? i see the plugin in my cpanel files so its there, i need to re enable it from the phpadmin, i saw the option enabled plugins, but i know you have to write a code for the plugin there wich i dont have. If you can help me or provide me with the code so i can at least try that you would save my life! I apologyze for the long text but i wanted to tell exactly what i did so maybe you know a way to help me.

Hi Benjacitt! Since I am also using cloudflare, this looks like an SSL error. I once had the same error “got the too many redirects error” and first didn’t know the cause. Have you tried a self-signed SSL certificate and installed it on your server? (in the cloudflare dashboard under ssl, it is the client server certificate). Just copy the key and the certificate. That helped in my case.
Gerald

@csab1915 this should now be address in v3.1.2

Thanks!

Paul, MANY THANKS! I can confirm that v3.1.2 works without any errors. Great job, I appreciate it!

No worries, glad we got it all sorted!