Conversation
supportI have been using the plugin for a while but visitors are experioencing a fatal error message since two weeks ago. The message I am getting fddrom WP is “An error of type E_ERROR was caused in line 288 of the file /wp-content/plugins/ip-based-login/init.php. Error message: Uncaught TypeError: method_exists(): Argument #1 ($object_or_class) must be of type object|string, null given in /wp-content/plugins/ip-based-login/init.php:288”. Any kind of solution for this problem?
Hi, Sorry for the inconvenience caused. I have just released v2.3.4 which should resolve the issue. Can you please upgrade to the latest version of the plugin and check if you are still facing the issue let us know.
Hi, Thnx for the quick response! Still not working. The solution I found works for me though. I just added on additional reuirement in line 288 off the init.php. [quote] if(is_object($wpsec->alerts) && method_exists($wpsec->alerts, ‘register_group’)){ [unquote] Maybe this will never invoke the WAS but that is better then blocking access. By the way: the error was not showing on another site of mine. So maybe it has something to do with the plugin settings of the Shield Security plugin?!
Thank you for sharing the solution. We will release a new version with the fix soon. Yes it seems there is some other plugin that is conflicting because we have not received anyone else reporting this issue. I am also not able to replicate this issue on my test server.
We just released v2.3.5 with this fix. Please upgrade to 2.3.5 and let us know if you still face the issue. Thank you for reporting the issue.
Hi, Sorry for the inconvenience caused. I have just released v2.3.4 which should resolve the issue. Can you please upgrade to the latest version of the plugin and check if you are still facing the issue let us know.
Hi, Thnx for the quick response! Still not working. The solution I found works for me though. I just added on additional reuirement in line 288 off the init.php. [quote] if(is_object($wpsec->alerts) && method_exists($wpsec->alerts, ‘register_group’)){ [unquote] Maybe this will never invoke the WAS but that is better then blocking access. By the way: the error was not showing on another site of mine. So maybe it has something to do with the plugin settings of the Shield Security plugin?!
Thank you for sharing the solution. We will release a new version with the fix soon. Yes it seems there is some other plugin that is conflicting because we have not received anyone else reporting this issue. I am also not able to replicate this issue on my test server.
We just released v2.3.5 with this fix. Please upgrade to 2.3.5 and let us know if you still face the issue. Thank you for reporting the issue.