Not showing scan results after wordpress update

This might be caused by scripts on your site — often other plugins or themes that have a script error — do you see anything in the JavaScript console, when viewing the page?

Instructions on viewing the JavaScript console are here:
Open the JavaScript console

If you can disable other plugins on the site and try running a scan, that might also show if a plugin is causing it. (You could also switch themes temporarily to test it — only do this if you know that your theme doesn’t break when changing themes. I’ve used one that does!)

It could also be caused by browser add-ins — if you’re running NoScript or similar add-ins, you might need to disable them for your own site.

My loudest problem is this: tor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. /wp-includes/functions.php on line 3457

which I get even after updating plugins for the 4.3 compatible versions.I’ll try turning them off but I think some of the most disturbing are:
SyntaxError: test for equality (==) mistyped as assignment (=)?
SyntaxError: in strict mode code, functions may be declared only at top level or immediately within another function
because whatever they do they are coming from a wordpress core js, not a plugin.
ReferenceError: reference to undefined property d.attributes[c].expando load-scripts.php:4:4651
ReferenceError: reference to undefined property jQuery.migrateMute

this is only a few and they all seem to be wordpress core.
Oh dear…turning off the plugins works but I need some of those…

Ok, so the next thing you can do when plugins are disabled is to turn plugins back on one at a time, and check for the original issue above, to see which one of them starts causing all of the error messages.

Were these all appearing in the javascript console, or were some in the site’s error log?

If you’re getting the warning about WP_Widget being deprecated, you might need to turn off WP_DEBUG — it should generally be off on live sites, and some of the error messages it displays can break other plugins. (At the same time, if there are plugins reporting a lot of errors, you can report them to the plugin authors, or find a suitable replacement!)

To turn off WP_DEBUG, find this line in wp-config.php:
define(‘WP_DEBUG’, true);
… and change the true to false.

Were you able to see which of your plugins was stopping Wordfence from displaying the list of issues to resolve?