engelsol

it’s buggy but it is working great for me… wp 2.7.1

I am thinking about fork it and just keep the Category-specific permalinks without the extra features.

I just upgraded nicely

ok… this is has being working well…
the last version sold many problems for me…

Thanks donncha

$cache_path = WP_CONTENT_DIR . ‘/cache/’;

THE PROBLEM….
Donncha… I am on my own server…
wp-super-cache is caching well to “wp-content/cache/”

But for some reason it also create many many files at the “/tmp” creating all kind of problem for wp, mysql, etc. when that memory dir become full.

After I MANUALLY delete wp-super-cache files from /tmp and clear the cache everything works until /tmp got full again.

HOW to avoid those files at the “/tmp” directory of linux

UPDATE:
I just installed your your version.

Now I dont see the garbage at the “/tmp”

I am suffering a DIGG like effect since 2 days ago… the site is almost unusable because of this… I have upgrade the server 2 times in 2 days… it is a news site with a hot news we published…but at least now I can browse… I will let it run 2 hours and then will give an update to see how it goes… I am using the latest build…wp 2.7 RC1

same problem as above….

and adding to that why there are so many generated wp-super-cache files at /tmp directory…

the garbage collection delete wp-super-cache files in the /tmp dir also?

Hi donncha

I love your plug-in but after my traffic increased wp-super-cache is giving me problem… because is getting the /tmp directory full quickly

Then mysql cannot write temp table… etc etc and wp-super-cache then caches my frontpage without categories and without content…
Only direct url post are visible… and the cats menu disappears.

Is there any way to tell wp-super-cache to store those files in another location different than /tmp ??