WP-Cache version 2: cache plugin

I have found when I publish new posts they don’t publish live straight away because a previous version is cached. Is there anything I can do about that?

Just wondered. I love the concept though ??

Karl

Hmmm just tried the new version and it reset my wp-content folder to 000 permissions.

Me too – I got the ‘wp-content is not writable by the webserver’ message and then when I went to change it via ftp it was chmod 000.

yeah I had to email my hosting to re-fix.

I have gone back to previous version for the time being.

Could you not change it pack with your ftp client? I had to e-mail my host to fix it too, but thought it was just because I was using a web based ftp, which is pretty limited.

Note really. My host is pretty good. I think athough I might be wrong) that once no permissions are showing the hosting company has to deal with it.

I have full FTP access.

Thats what I thought, I was going to mess around with it tonight (with a decent ftp program) but I don’t think I will if I have to keep bugging my host to reset the permissions every 10 minutes!

exactly!

Hi, I just released Beta2, which avoid those “chmod” problems (which must be a bug in hostings’ server. Did yoy try just renaming the dir and creating a new one?).

2005-05-06: 2.0-beta2
– removed paranoic chmod’s
– check for cache file consistency in Phase1 several times
– addded option to prevent cache based on user-agents
– added size in KB to every listed file in “cache listing”

BTW, I’m sorry for those that got in troubles due to the chmod bug.

Ok, great plugin, but ……

I think I found a bug and and I have a theory whats going on. If you have this plugin installed AND you select Options ->Reading ->Wordpress should compress articles (gzip) …

you get gibberish the second time around on a page. What I think is going on is the output to the browser goes something like this:

WordPress -> gzip (internal) -> cache -> browser

problem is, second time around it looks like maybe this is happening

cache hit -> gzip -> browser but the content in the cache hit is gzipped already (as evidenced by looking at the html file in the cache directory) and it gets run through the compressor AGAIN. So, when you get it on the browser, its garbage.

Looks like the cache population routine needs to intercept the output BEFORE it hits the zipper, cache it to disk, then feed it to the zipper when needed. This is especially true for browsers that can’t handle zipped pages very well.

Thoughts?

Option B is screw it on the selection and let Apache mod_deflate do the compression, but I digress …

Thanks for a cool plugin! It made a noticeable difference.

Eric

Possibly I’ll implement gzip compatibility in version 2.1. But there things that must be taken in consideration and I’m not sure yet what is the best option, so I decided to stabilize and hard test this version before implementing a feature that I’m not sure what’s the best approach. For example:

1. A server that reay needs wp-cache has serious problems with CPU usage, not bandwidth.

2. Zipping or unzipping html contents consumes CPU, so both versions must be stored. Or select the most frequently used, do most of clients accept gzipped?

3. In any case, the performance of wp-cache will be negatively affected. In the “cache serving” (i.e. more filetesting and md5 generation, which is no so cheap) or during generating a page the first time.

Ideas? Recommendations? (please do it at https://mnm.uib.es/gallir/wp-cache-2/ )

Possibly I’ll implement gzip compatibility in version 2.1. But there things that must be taken in consideration and I’m not sure yet what is the best option, so I decided to stabilize and hard test this version before implementing a feature that I’m not sure what’s the best approach. For example:

1. A server that reay needs wp-cache has serious problems with CPU usage, not bandwidth.

2. Zipping or unzipping html contents consumes CPU, so both versions must be stored. Or select the most frequently used, do most of clients accept gzipped?

3. In any case, the performance of wp-cache will be negatively affected. In the “cache serving” (i.e. more filetesting and md5 generation, which is no so cheap) or during generating a page the first time.

Ideas? Recommendations? (please do it at https://mnm.uib.es/gallir/wp-cache-2/ )