Hi,
My wp-config.php has this:
define(‘WP_DEBUG’, false);
So unless there is another place where i need to disable this i would need to know
Hi Mark,
Changing the WP_DEBUG did not solve the problem. I also tried adding the error_reporting(0) function to the header and it didn’t solve it as well so it looks like something from the plugin.
I hope you resolve this because plugin has to be disabled for the error to disappear.
My site is on a sub domain… I had nothing in my wp-config.php so i guess the default is with debug. I added : define(‘WP_DEBUG’, false); and the message is gone but i guess the issue will be solved as soon as you guys fix the order.
Thanks
Hi Mark,
I tried changing the WP_DEBUG and even adding the error_reporting(0) function to the header and still the warning persists.
I hope you solve this soon cause the plugin has to stay disabled till then.
wierd, i just posted another message saying that i didnt have any debug definition on my sub domain where the site is running and that when i added that the message indeed didnt appear again… but the post doesnt show..
Sorry about the duplicate post. The board seems to be a little lagged this morning.
Rowina: If you’re seeing the is_404() warning that we’re discussing, I think your hosting provider must be enabling WP_DEBUG somewhere else then. Possibly a separate php.ini file. Can you please log a support call with them to verify. If you’re not seeing the is_404() warning then let me know.
Regards,
Mark.
Yes it sounds like WP_DEBUG is defined elsewhere and what you’re doing is overriding it with your own define() statement. But the order of execution is difficult to predict – perhaps your override gets called first or perhaps the existing statement gets called. So I would recommend asking your hosting provider if they’ve set WP_DEBUG and ask them to change that if it’s a production site.
Gotta get back to fixing this issue, so won’t be replying for a little while.
Regards,
Mark.
Wordfence 5.0.2 has been released and is a hotfix for the is_404() warning you’re seeing and includes several other fixes.
Please upgrade and let me know if it resolves the issue for you.
Regards,
Mark.
It’s all good – I’ve just updated and the issue is fixed.
