Kimberly

If a response includes a Cache-Control field with the max-age directive, that directive overrides the Expires field. It’s possible your web server could be included them.

You can use something like HTTP Analyzer or Firebug to see the headers. Or you can also visit one of many online sites to check and see your page’s returned headers.

Really? Dating back 3-months? If that is the case then DEFINITELY something is wrong. Yea on my side it does go about refreshing them when they expire. Of course, do realize that if no one returns to the page that needs refreshing this old cache file can remain dormant in the folder forever (assuming you dont make use of QC’s auto-cache feature).

I am not sure how big your site is (existing pages) so maybe 19K files is normal, but if not, then it sounds to me you may be caching GET/POST requests too which can get quite sizable as people begin to use a search box or even write a comment. By default though i believe this plugin shouldn’t be caching those.

If these very old files still exist can you view one of them, scroll to the bottom of the file, copy its URL and try testing (in your browser) to see if that same old cache file is returned (view source code and scroll to the bottom to see if the time stamp is the same as what was shown in the file). I am curious to find out if QC will begin caching a new copy of the page.

On the flip side, if you want to test a particular page but dont know what its qc-c.* file is you can use an online MD5 calculator to help locate the file. Assuming you aren’t using a salt (by default it is left blank) the name of the qc-c-* file is postfixed with MD5 hashes of the url of a page. So for example if my page was: example.com/about/ (notice i dont use http:// at the beginning) then it’s MD5 hash would be: 8f17b1f11ffd5b7316d4e404fb533a47, resulting in a QC qache file named: qc-c-8f17b1f11ffd5b7316d4e404fb533a47-8f17b1f11ffd5b7316d4e404fb533a47-617a9471507f0eb608f3858291adb70f

Format:
qc-c-{MD5 of Page URL}–{MD5 of Page URL}–{MD5 of Site Host Name ending with a Slash}

Yup. I can confirm it. That is what i do all the time. I find it is much quicker to do it myself than wait on it clearing when i have too many files.

Actually, using either of these URLs result in the same thing. So there is nothing that needs to be fixed.

Okay you can go ahead and put back your original sitemap-core.php file and delete those two @MY_LOG.txt files. I have the results.

I will have a look and get back to you.

Oh, that’s unique. Well, you can do what i did by way of getting it to work like normal (so put back the original file and making sure it is fine) and just replacing it with my file…so without deactivating the plugin. That way it doesnt realize it has been changed. Works for me.

I am heading out to do some shopping — i am a girl after all 😛 so i will be back in 3 hrs time.

Ok i did a very crude change to sitemap-core.php that includes a simple call to MY_LOG(..) that writes out lines like “1”, “2”, and so on (doesnt write out any other info). Here is the changed file: http://speedy.sh/5CwEq/sitemap-core.php

Can you rename your existing sitemap-core.php file and put the above file in its place and then try to rebuild your sitemap?

What it will do is write out a file called “@MY_LOG.txt” in both the root and wp-admin area of your website. So then i should be able to access it via: http://www.bästalotterna.com/@MY_LOG.txt … when we are done then you can delete this txt file and replace your sitemap-core.php file back to its original.

Just in case you are wonddeirng here is the function i put in:

function MY_LOG($data)
{
 file_put_contents("@MY_LOG.txt",$data."<br />",FILE_APPEND);
file_put_contents($_SERVER['DOCUMENT_ROOT']."/@MY_LOG.txt",$data."<br />",FILE_APPEND);
}

Notice it writes out two files. I wasnt sure if your site would have issues using $_SERVER[‘DOCUMENT_ROOT’] so i decided to use two file_put_contents() calls as a backup so i can either access the file from the root and if that didnt work then i can access the file via: http://www.bästalotterna.com/wp-admin/@MY_LOG.txt (assuming you kept the default plugin name the same).