nickwinter

Hi Matt,

Thanks for your help. I did as you suggested and it now scans OK. It seems to be fixed, so that’s great.

(I couldn’t find “disable config caching” on the options page, maybe I just can’t see for looking! I’ll try again.)

Anyway, it is all working now and thanks again for your excellent support!

Nick

Hi Matt,

I forwarded your request to the host and they replied as follows:

****
We run the latest stable version of mySQL so that we are certain it is compatible with most customer websites. To upgrade mySQL to a newer version would put other sites at risk of not working as they may not be compatible with the new mySQL version and mySQL cannot be rolled back. This is how most if not all hosting companies work. (Don’t fix what isn’t broken). To upgrade further could cause major issues and we are now running Currently installed: 5.5.5-10.0.24-MariaDB which is the most widely supported and most up to date stable version which is recommended by cPanel/WHM on a Centos 6 environment.

We use word fence on our own church website which is hosted on the same environment with no issues. What I would suggest is that you uninstall word fence and install it again to see if this helps.

It’s also interesting that they note a boolean error 2 days ago in their own changelog – see here:
https://www.ads-software.com/plugins/wordfence/changelog/

Hope this helps.

***

I tried deleting WF and reinstalling it, but there was no change, still not scanning. (I was interested to see that it retained my old settings, despite being a new installation?)

Am I really the only person on the planet affected by this? Obviously not my day!!!

Thanks for your help, but I’m not sure where I go from here?

Nick

Just tried a scan and it still doesn’t work!

Glad yours is working, Steve!

Matt,

Report sent.

Nick

Matt,

One thought: the previous WF version went from learning mode to normal scanning around this time. (But then so did my other site and that’s OK…)

Nick

Hi Matt,

Thanks for looking at this.

Yes, I’ve tried several manual scans and it still does it. I updated WP today but it was already showing this in the live activity, with yesterday’s date, so probably not related to the WP update. My other site also has the latest WP and works fine with WF.

If it helps, last few lines in the live activity are:

[Apr 21 14:06:58] Getting plugin list from WordPress
[Apr 21 14:06:58] Found 11 plugins
[Apr 21 14:06:58] Getting theme list from WordPress
[Apr 21 14:06:58] Found 1 themes
[Apr 21 14:07:13] Analyzed 100 files containing 1.26 MB of data so far
[Apr 21 14:07:17] Scan can’t continue – stored data not found after a fork. Got type: boolean

Thanks!

Nick

I have the same problem as you, Steve. I have updated to WF 6.1.4 and I am still getting:

Scan can’t continue – stored data not found after a fork. Got type: boolean

on scans on a site I look after at: aldeburghparishchurch.org.uk

Works fine on my other site.