orbalon

I’m curious about the answer to this as well. Though, I figure worse case I can always use the settings in SuperCache to exclude my contact form pages. Not ideal though.

Thanks MSPC, That worked for me too. Washerhelp, I assume you are using WP 2.6? I’m using 2.7.1 and I would guess silverwolf21 is too.

-This is not a built in functionality as far as I can tell
-There is an option to clear cache after creating a post in the settings.
-Most people need caching for pages because the run widgets along them like on posts. Like “recent posts”. Purging the cache on these pages lets you see things like this update.

go through all the troubleshooting steps in the readme.txt. Chaces are supercache is not automatically placing things where it needs to be because it doesnt have write permissions. Which just means some manual leg work.

Also 100 hits on a wordpress site shouldnt be causing that much cpu usage. research your plugins and make sure you dont have too many and/or very intense ones.

I’d question how many other people are hosted on your box and the host you’re using in general if excessive plugins are not the issue.

There is a rather long checklist in the readme.txt that comes with supercache. Doing what supercache says to do out of the box is sometimes only a cornerstone of what needs to be setup. Check out that file and verify each step on there. A big one is the .htaccess files which you didnt mention anything about.

super cache uses chmod in one place in the script from what I remember and running it on your public_html folder was not what it was doing. I think it was in there as a fail safe in case the file couldnt be edited.

Also note, typically the main html dir your site is in is also chmod 755. At least on my server. I run a self managed dedicated machine, so unless I dont remember changing it, it came like that out of the box.

Are you sure its not complaining about “wp-content”? Check that file…

Note, this appeared to be because of a server configuration issue. I moved it to a different server and everything started working fine. (its now on a linux box). The previous box was a dev environment hosted under windows with apache 2.x and php 5. I was also running the site off of a port: 8085 (since I have other sites on that box). Any of these things might have played a role, but I never narrowed it down.

Hopefully this will lead someone else with the same issue down the right path…

I am not logged in as any user when testing this.
I also tested it from another computer (but on the same network) and had the same issue as described above.

Any other ideas?

The previous post appears to be version based after further research.

Another thing to note:
When I load a page in firefox (lets say) I can see the cache file being created: “wp-cache-eab2666771bac18604d50f5419c0c7cb.html”. Refreshing the page serves that file correctly.

But then loading the same page up in IE creates another new file:
“wp-cache-f3eb4a12ce2832564c134d19c3909cc0.html”.
Refreshing the page in IE again serves that file correctly.

After doing that refreshing the Firefox page still serves wp-cache-eab2666771bac18604d50f5419c0c7cb.html until garbage collection comes around or cache is manually cleared.

So confused…

I noticed something else…

On another site (which I know is using super cache. I did a view source and see this as the last line: “<!– Dynamic Page Served (once) in 1.529 seconds –>”.

Note the “(once)” part?

On my site, I see this as the last line of the source:
<!– Dynamic page generated in 0.854 seconds. –>

I’m guessing that “(once)” tag has something to do with this?