skippybosco

Thanks, I’ll try that out, was confused about that setting and what all was “refreshed” if that was left unchecked. I appreciate the clarification.

On a side note, did the latest upgrade from SVN, very happy to see the integration of OSSDL CDN Off Linker. Had been using that plugin independent of WP Super Cache for a while now. Good stuff!

I’ve seen a few SVN updates since this topic was started, but no commit messages specifically mentioning this bug.

Specifically homepage not being updated when two conditions are met:

1) All posts are scheduled (in my case, 1 every 30 minutes)

2) No actions taken for hours or sometimes days which require someone to log in to WordPress (all comments to the site are done via guest comments.

Considering just having something delete the cache/mydomain.com/index.html every 30 minutes.. but wanted to follow up to see if there was a more suitable option in the works.

Thanks for the follow up. Understood.

@donncha: as always, thanks for the follow up. makes sense now that you pointed out the obvious to me ??

@jasonkong: I believe so, but hard to say as we average > 500,000 pageviews a day so a good many of our ~10,000 posts are Super Cached naturally as a result of visitor activity.

Thank you for your reply. Yes, I do have “only refresh current page when comments are made” checked. I had assumed that a scheduled post publishing would expire the home page and force a refresh, is my logic in error?

In the cloudfire.com solution the CDN is actually hosting the domain name and redirecting non-cachable content back to the site.. I’ll explore this a bit more and see what, if any, options are available. Creating a globally distributed cached site could really make a site “Digg Proof” ??

I’ve seen something recently as well where folders are being created in my supercache that are variations of my primary domain with a trailing period. (mydomain.com <- good -vs- mydomain.com. <- not good)

Has anyone seen that before? Any ideas on how to prevent it (suggestions on .htaccess rules perhaps?)

Ok, found the solution to my problem.

For those having difficulties with mod-rewrite and subdirectories with protected content:
—
https://www.ads-software.com/support/topic/142943
—
Essentially the workaround is to add this into the root .htaccess just before the wordpress entry:

ErrorDocument 401 /onerror.html
ErrorDocument 403 /onerror.html

Might want to give the Redirection plugin a whirl:

https://www.ads-software.com/extend/plugins/redirection

Thanks Diane.

I’m thinking somehow disabling the Rewrite Rules in the .htaccess may be the trick to getting the Digest security working?

Surprised no one else has run into this before.

For those curious, just tested under 2.51 and working splendid.

Thanks for the great plugin. Check is in the mail.

I agree. The site colors and pictures are very cool.

Regarding text, I’m guessing google translation.

“We come to pitch west hillock village visit stupid bright town”