dvmorris

What exactly was your fix? Did you grab an initial set of rewrite rules from somewhere specific? I found some here: https://core.trac.www.ads-software.com/ticket/23748

But they differ from yours in 3 different places. Do your blogs.dir rewrite rules also work with the above configuration?

Thanks,
Dave

I noticed that the latest version is designed to be run within the /plugins folder. Will it still work in the mu-plugins folder? I run 1500 blogs on this platform, so I want to make sure that I don’t break the caching mechanism when I do the upgrade.

Thanks,
Dave

Do you have any ideas what I can do about this issue?

Thanks for your help,
Dave

Here is a sample feed URL: https://insidescoopsf.sfgate.com/feed/?taxonomy=niche-site&term=ns-main-well

Here is a pastebin of the super cache debug log: https://pastebin.com/T7KJHyu7

I see what you mean about how Super Cache is not handling this feed. I suppose where I’m getting confused is when I set the timeout to something like 10 seconds, I would expect that WP Cache file that is being served up to regenerate if I make another request to it after 10 seconds.

Is this the expected behavior, or am I missing something else in my configuration of the WP Super Cache plugin?

Thanks,
Dave

I’m running the commands from the local machine, as well as the browser.

Did you ever resolve this issue? I would like to do the same thing.

Thanks,
Dave

Any idea why this would be happening? Could it have to do with default request header setting in cURL?

Thanks,
Dave

Yes. It does not seem to run when making a request with curl or wget.

Would there be a way to accomplish this by looking at apache access logs?

Dave

That seems to clear the cache for all blogs no matter which blog i’m on when I click the button…

Dave

That does work, but I want to hook this functionality in a plugin and have my theme handle the loop without any knowledge of the plugin. Does that make sense?

It seems that if I add this line:

$wp_query->is_tax = true;

And wrap it in an is_home() conditional statment, then it seems to work as I was expecting it to.

Is this correct? Will it cause any other issues with other loops on the page?

Thanks,
Dave

Okay, that’s good to know. Is there any plan to add this in the future? Or, how difficult would it be to add? I could probably help with it if we end up using this plugin on my project.

Thanks,
Dave

Thanks so much for your reply. I will look into turning caching off for known users.

Thanks,
Dave

Thanks so much for your reply! It is true that this issue does not affect RSS reading applications. I guess I go hung up on it because one of our testers reported it yesterday and the behavior was really confusing me.

While I have your attention, do you know why Super Cache might be causing a user who posts a comment to be redirected to the home page of that blog rather than the blog post page.

Then, when the user visits the blog post page where they just left a comment, they see their comment as expected, but the “Post a Comment” form is pre-filled out with the following information:

Name: Sulemaw
Mail: [email protected]
Website: https://zspf.ru/content.php?id…

Or some other random user’s info. I confirmed that this user’s information exists in a different blog’s wp_*_comments table, if that helps clear things up. It’s as though super cache is throwing a cookie out there that has the random comment information in it.

It’s very intermittent and difficult to reproduce consistently, especially in a VM environment.

Thanks for your help,
Dave