barkins

Experiencing this as well. What should we do?

Got it, thanks for the quick replies @launchinteractive

Very cool, thanks @launchinteractive

Would this plugin interfere with WP Super Cache?

Thanks @launchinteractive

Just checking, would the prompt also popup on the live website for those who don’t have Java installed on their computer?

I don’t know, but I’m not the plugin developer.

Tag out @kcpt? What do you mean?

Thanks @kcpt for the tip. Fixed my issue.

Thanks @karimeo

That indeed solved the problem. In short 4.7 update should come with instructions on deactivating object cache before updating.

Thanks. I updated the same website locally (MAMP) and the update worked perfectly.

The same website on the live server generates the following error:

Fatal error: Call to a member function do_all_hook()

On the same server, I updated other websites successfully. :\

Lots of errors popping up after the update. Can’t access the Admin without manually deleting the plugin.

Had to disable the plugin on all my websites, can’t access the Admin.

Perfect, thanks Will.

Got it. So it’s safe to assume whatever is showing up in the Wordfence log is up to date and accurate? Thanks

Ah, Cloudflare. I did have to turn it off when I installed SSL on the domain. Sounds like that’s what it was. Thanks for the info.

Thanks WFMattR. I already had that feature checked off, making it even more disturbing how the account names were found out. I also don’t have the usernames listed in the body class either. Quite disturbing.

Thankfully WordFence was installed on the site.

Thanks for the tips barnez.

Thankfully I already had ‘enforce strong passwords’ active.