kwdavids

I have resolved this problem. It was a quirk in the latest version of WP Super Cache.

My blog lives in a directory with an upper case directory name. The latest WP Super Cache version forces the HTTP-HOST variable to lower case when it decides where to write the cached files, putting them in a different place than where the .htaccess file points. As a result I was serving old pages unless they were coming from the legacy WP Cache.

I resolved the problem by changing the directory name for my blog to all lower case, then deactivating and reactivating WP Super Cache.

I looked at the mod_rewrite rules, and see

RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz -f
RewriteRule ^(.*) "/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz" [L]

That’s clearly not going to find the cached files which are not under the DOCUMENT_ROOT, but under a lower-cased version of it.

So the question is whether I should hack the mod_rewrite rules to find where WP Super Cache put the cached pages, or fix WP Super Cache to put them in the right place to begin with.

I went through the Troubleshooting 3.1 master list. No joy.

I can’t deactivate plugins one by one because I can’t reproduce the problem, only a visitor can and all my regular visitors have posted comments and made the problem go away for them.

I know now that the problem is not theme related because one visitor sent me the HTML. The WP Super Cache entry at the bottom showed that the user was served a page generated 3 days ago.

I don’t have any inactive plug-ins.

I’ve had the 500 errors too from time to time when the traffic spikes. How many sites are you trying to run at the same time on DreamHost? That in an of itself might be the issue, and unfortunately for some really odd reason, DreamHost will not sell you multiple accounts.

DreamHost has some some very good tutorials on optimizing WordPress and reducing memory. It mentions some plug-ins that are real memory hogs.

My site averages serving about 11,000 pages a day and works OK at that level. I keep my plug-ins to a minimum and use WP Super Cache and WP Widget Cache. I figure the secret to keeping memory usage down is for users to get in and get out fast, and I have my page generation times down to about half a second. I also have FAST-CGI enabled, but that is only because my blog is heavily commented.

I ran the automatic reinstall and this went away.

I have the problem pasting from a web page, from Microsoft Word or any place else where color used to work in the visual editor.

The fact that I have markup for this one page is just accidental.

Pasting markup into the HTML tab brings a totally different set of problems involving line breaks that shouldn’t be there.

I’m new to WordPress.com Stats. I have been using “analog,” which looks at the server logs: it shows 7,000 to 9,000 page views per day while WordPress.com Stats is only picking up around 2,000. Of course the server logs don’t care whether I’m logged in or not, but that should be a fairly small difference.

The problem is that when someone who is BANNED visits your site, WP Super Cache caches the ban message. Then anyone who subsequently visits that page gets the ban message too.

It can be temporarily cleared up by deleting the cache.

I found it necessary to replace the comments.php file as described in the following article to get paged comments to work.

https://techie-buzz.com/wordpress/how-to-use-wordpress-27-threaded-and-paged-comments-feature-in-your-theme.html

Looks like the calendar at https://coveconnections.com is broken. All I see is: EventsCalendarLarge.