Kimberly

Fascinating. I wonder if your problem is like the other fellow. Curious:

1. Are ALL files not re-caching (remaining old)? Or just a selection of them?

2. If only select files then is there a pattern such as query strings in their url?

I would like to verify that loopback requests are working on your server.

Try adding these 2 test files to your server and running the LoopbackTest-Call.php file from your browser:

LoopbackTest-Call.php:
Note: Replace {YOUR SITE HOST NAME HERE} shown in the code below with your actual host domain (e.g:www .mysite.com).

<?php
	$ch = curl_init();
	curl_setopt($ch, CURLOPT_URL, 'http://{YOUR SITE HOST NAME HERE}/LoopbackTest-Reply.php');
	curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
	$html = curl_exec($ch);
	echo "Loopback Response: ".$html;
?>

LoopbackTest-Reply.php:

<?php
	echo "SUCCESS!!";
?>

If successful you should see “Loopback Response: SUCCESS!!“. It’s important that you call the LoopbackTest-Call.php file from your browser and NOT the LoopbackTest-Reply.php file. Once we know loopback requests are working on your server then we can continue to pinpoint what is going on.

sounds like its specialized cron it adds to wp-cron list isn’t working on your end. When i check my list i see a quick cache garbage clean up that is run either one per hour or once per day (cant remember which).

Curious…are those old pages continuing to use those old cachce files even though when you check the bottom of the page the expiration date indeed shows it has expired?

I wish i remember my coding. I use to know the answer to this. Granted my plugin is patched by me to resolve all my problems and works with WP3.4.2. Because so many people are having problems i may muster up the energy to just zip my forked version for those here to use.

There are a few others here who’ve made their own fork of this plugin too which u can read in this forum and contact. They might then get back to you sooner with the zip than me.

This is a known bug which a few of us addressed and fixed. Check out one of the other comments to find a step-by-step fix.

I had to write my own patch that got rid of it. Its been a while but i think that # is also used in determining the final minify name (md5 hash) which is probably not a good idea since every time it does a new minify on the same files you will get a new name which will break tihngs like cache plugins if the times arent in sync (missing files). And then there is the issue with those who crawled your page will find your minify js/css file(s) are now gone and will potentially flag the site as suspicious since these files keep disappearing every xx hours/days.

There are a few of us here who have made our own forked versions of this plugin and one day we might just merge them.

I havent worked on this plugin for several months now so i forget all the things i’ve added or patched but it works very well in every way now.

I just did a quick hunt through the author’s code and I could give you a quick fix line of code you can add to resolve this problem but i am not sure if you are even bothering with this plugin anymore.