ericr23

Solution! I thought if I edit one of the posts, or even just open it and click Update, it would be counted. The result was even better: The whole count was updated, and the category now appears in the dropdown menu!

I converted a tag to category and have the same issue. Since WP now thinks there are 0 posts in that category, even though clicking in the admin page on the 0 lists all of the posts, the category doesn’t appear with the other categories in the dropdown menu.

That appears to have taken care of it.

I have wrapped the iffeed-scotland.php file in ob_start() and ob_flush(). We’ll see if that helps.

Yes, it’s the same provided on the settings page (debug tab).

Thanks. No applicable errors. “httpd -M” shows that auth_basic_module is loaded.

That sounds like a good idea.

Very good points. I was going to think through that, so many thanks. And the server itself should provide protection against DDoS attacks.

It appears that to allow Wordfence (in “extended protection” mode) to act first, WP Super Cache has to be “simple” mode and “late init” has to be turned on.

Also “late init” in WP Super Cache (“Display cached files after WordPress has loaded”). (I tested easy/simple mode without late init.)

That appears to work! Each reloading of a post is logged.

I tested it in WPSC “expert” mode, too, and it did not work.

This seems to be the case for me, too. My Wordfence is using “extended protection”. WP Super Cache is in “expert” mode. In the htaccess file, WF’s block is first, then WPSC’s, and finally WP’s.

I tested by turning on “all traffic” and including my (logged-in user) own for Wordfence’s live traffic. Then I went to another browser and went back and forth between two stories that I knew were cached. Neither of them was logged by WF, only as referrers to the Ajax-loaded feed in the sidebar.

Then I deleted the WPSC cache and loaded the stories. They were now logged by Wordfence. Then I went back and forth among them again (now that cached copies would have been created), and they were not logged.

I suppose the fact that the ajax-loaded feed in the sidebar is still logged on cached pages means that in my setup Wordfence would still catch bad actors. Also, each cached file is set to persist only 1 hour, so there’s still a good chance that bad actors would get a noncached file.

Wordfence appears to be working fine.

Wow – I’m so pleased! My programming knowledge is strictly as-needed, so that’s great. Thanks.

Line 12 of debug.php, creating the link, appears to remove $_SERVER[‘DOCUMENT_ROOT’] from $cache_path – leaving the extra /news?