mojori5638

Thanks for taking the time to respond.

Before I disabled the plugin I had already done as you suggested and didnt see anything unusual. I seen wget listed as I said earlier, and I disabled it to no avail.

Well I got it working by disabling the plugin stop bad bots.

I went into the access log and wanted to see if the cron job was running. It was running fine but was returning a 0 byte file with each run.

I remember seeing wget in the list of bad bots, so in the stop bad bots plugin I disabled wget. That didnt resolve the issue but it now was at least returning a 5kb file in the access log. I completely disabled the plugin and it started working.

Something in that plugin is preventing preload from working.

• This reply was modified 7 years, 11 months ago by mojori5638.

update..

So I cleared browser cache and cookies and went back to site and clicked around. Using this method, it DOES create a new cache file for each post, so that tells me the plugin is able to write to the directory.

I then manually run ?action=wpfastestcache&type=preload as a guest and that doesnt generate any new cache files.

So I am at a loss. No matter how I run preload, it is not generating cache files.

It was one of these two plugins causing the problem

Social Share WordPress Plugin – AccessPress Social Share
Social Login WordPress Plugin – AccessPress Social Login Lite

View post on imgur.com