I was getting “The pages do not match! Timestamps differ or were not found!” message too when using the Cache Tester.
Even with “Don’t cache pages for known users. (Logged in users and those that comment)” unchecked I was getting the error when using the Cache Tester.
I tested it manually and found it is working perfectly. Thanks for the tip donncha.
On my installation of WP Super Cache 0.9.9.3 with WordPress 3.0 (multi-site), the error message at the bottom of my generated page was:
WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed!
Now, the main line in advanced-cache.php is:
@is_file( ‘CACHEHOME’ . ‘wp-cache-phase1.php’ )
How would I change the path to wp-cache-phase1.php then? I’d have to reset the CACHEHOME variable?
How did you install the plugin? That CACHEHOME string is supposed to be a path to your supercache plugin directory. It’s installed by wp-cache.php
I just re-installed the plugin to make sure I remember how I installed. I used the WP Dashboard built-in “Add New” plugin, selected WP Super Cache, did a Network Activiate, and then went to WP Super Cache Manager. Changed Status to “HALF ON”, clicked Update Status. Then clicked on “Test Cache”. Same error message
Test your cached website by clicking the test button below.
Fetching http://xyzsample.us to prime cache: OK
Fetching first copy of http://xyzsample.us: OK
Fetching second copy of http://xyzsample.us: OK
The pages do not match! Timestamps differ or were not found!
However, this time around, the bottom of the generated page says things are ok:
<!– Dynamic page generated in 1.018 seconds. –>
<!– Cached page generated by WP-Super-Cache on 2010-07-17 09:04:07 –>
Okay, good by me, even tho’ the test part timestamp isn’t working. Thanks for reply.
Hi Guys
I have loaded up this Plug-in and it looks like it has worked (the site seems faster and cached pages appear in my files) but I get this message:
The pages do not match! Timestamps differ or were not found!
The debug message says: URI rejected. Not Caching
Any ideas – site is http://www.leadinganddevelopinghighperformance.com
Many thanks
Andy
I have the same test cache response:”The pages do not match! Timestamps differ or were not found!” on one of two WP installs in the same domain.
The install in the blog directory passes (matches)(ex. http://www.dajuanjones.com/blog/ ).
However, the install in the ‘wordpress’ directory whose URL is the root does not pass (ex. http://www.dajuanjones.com ). In the later, I gave that WP install it’s own directory. The ‘test cache’ tested http://www.dajuanjones.com/wordpress, which doesn’t exist. Donncha, is that expected behavior for this type of WP install?
There’s something weird with blogs where WP is installed in a subdirectory. The plugin tries to load site_url() which should point at the right place. When I have time I’m going to replicate that setup!
I’m having the same issue with “The pages do not match! Timestamps differ or were not found!”
Here are the debug log entries being emailed to me:
• Writing meta file: /home/me/mysite.com/wordpress/wp-content/cache/meta/wp-cache-text#string.meta
• URI rejected. Not Caching
• 404 file not found not cached
• gc: deleted /home/etc/etc… (A bunch of these)
• Buffer is blank. Output buffer may have been corrupted by another plugin or this is a redirected URL. Look for text ‘ob_start’ in the files of your plugins directory. There is no ‘ob_start’ there
• No closing html tag. Not caching.
• Anonymous user detected. Only creating Supercache file.
I have deactivated supercache until I get this figured out. Also, I have WP in a subdirectory.
??
I found the problem with the cache tester, it was using site_url() which returns the subdirectory. That’ll be a 404. I’ve just changed it to “trailingslashit( get_bloginfo( ‘url’ )” in trunk and it works. Try the development version on the download page (other versions) to test it!
@donncha — Thanks! This appears to have resolved my ongoing problem with wordpress being installed in a subdirectory but hosted at the root of the domain. I had been wondering if WP-Supercache had issues with this scenario but assumed that it was my configuration issue.
By default we install all our sites in a subfolder and then when they are ready to launch we make it live on the root of the domain using this method: http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory
But we were noticing that this seemed to cause an issue with Supercache
Thanks for your help – I will follow this thread to see the results for others and to let you know if there is anything else that is an issue.
I am getting the same – The pages do not match! Timestamps differ or were not found – message on my site http//www.himachallive.com
The debug log entries mentions – URI rejected. Not Caching
I am using the permalinks in http://www.himachallive.com//%postname%.html format.
I downloaded and uploaded the developmental version of the plugin and am getting the same error.
Is there a fix for this?
I have the same error. Does it actually mean anything? Does it mean that SuperCache isn’t working?
Second questions – how does this debugging work? How do I get some information that might be useful? I checked it “on” and enetered my email adress, but it doesn’t do anything.
Thanks!
nityin – the plugin isn’t caching because of some setting you in have in the “rejected uri” field I’d guess.
nickaster – yes, it means the plugin probably isn’t working. If you didn’t get any emails from the debug system did you try loading your blog while debugging was on?
yeah, I loaded it and left the “debug” checked …. with my email address in the slot. It’s been like that for days, I have not gotten any email. Blog’s been loaded thousands of times…. what do you think I’m doing wrong?
yeah, I loaded it and left the “debug” checked …. with my email address in the slot. It’s been like that for days, I have not gotten any email. Blog’s been loaded thousands of times…. what do you think I’m doing wrong?
