I am getting the same error, however I also cannot seem to log in as admin, all it shows is the same 4 notices and a warning that I cannot modify header information due to “headers being sent by” etc etc.
A quick google search is showing a LOT of sites showing the same Notice.
I reverted to 5.3.1 and it has gone away. I will wait for them to fix it.
Yes, I disabled Wordfence manually and my site is just fine now. I’ll revert and install some back-up security for the interim while we wait for a fix.
We’ll update the dev team and try to reproduce. Can you confirm your version of wordpress, caching on or off, any duplicate plugins, etc?
Also, can you try enabling the java console in chrome and look for the error in red. Screenshot that and post a link here. Chrome javascript console is found by going to the link in the upper right of your screen, selecting ‘more tools’, then javascript console.
Thanks
tim
WordPress 4.0 no caching. I don’t know what you mean by duplicate plugins. If you mean any other security plugins, then none.
I have just updated the development site rather than live. No errors are shown in the Javascript console.
Duplicate plugins probably wasn’t descriptive enough. I meant plugins with duplicate functionality like w3 total cache and our caching enabled. Or another security plugin that is handling logins while ours is too. Those are just examples though. A list of your plugins would be good but I think you ruled out conflicts with duplicate functionality.
So is the error still showing on the dev site? I want to see if you can reproduce it so you can check the java console on the page that’s showing the error
Tim
No caching or other security plugins.
Yes it is reproducible installing either on live or dev triggers the error.
No errors shown in the java console, unless I am using it incorrectly. The error is the same on either dev or live.
Have another reported so that makes three so far. Escalated to the dev team. I’ll update as soon as I can.
tim
Dev team is on it. Will have a fix in place within the next day or so. When I get an update, I’ll update this thread.
Thanks for reporting it!
We are a little concerned that you are seeing the error on your screen if you have not enabled debug mode. That usually points to a website configuration error with the hosting company. Can you verify the wp-config does not have debugging enabled?
tim
Definitely do not have debug enabled in wp-config and also have
error_reporting(0);
@ini_set(‘display_errors’, 0);
In my wp-config to ensure no errors are shown in the front end.
Can you send me the domain name. If you don’t want to post here email to tim [at] wordfence.com
tim
I can confirm that this is now fixed.
