jerd

This has to do with changes in the mobile support in the latest version of WP Super Cache.

The reason the site is randomly showing the mobile site is because a non-mobile version is being cached (this means that someone on a mobile device probably visited that page and they have the mobile site turned off [by toggling the option at the bottom of the page])

I wrote a very quick and very dirty patch that works around the problem, feel free to use it if you like.

wp-super-cache-1.0-wptouch.patch

For everyone that switched over to JetPack — were your stats from WP stats preserved or does everything start at zero again?

I think I just found the reason. I went into the options and unchecked the ‘Cache rebuild’ option in the ‘Miscellaneous’ section under the Advanced tab and the caching is now working as expected. When a post is made it now immediately updates the homepage.

Thanks, Jeremy

No, I don’t have DB cache (or any other caching plugin) installed. As far as I know there is no other caching happening.

One other thing I noticed is that even though the files have a new timestamp, the page itself is old. For instance, I just made a post, and the file on the server has a timestamp of 11:52am, but inside the file itself is:

<!– Cached page generated by WP-Super-Cache on 2010-10-31 11:46:01 –>

It’s like the file has been touched but not regenerated.

Any other ideas you can think of? I’m completely stumped on this one.

Thanks, Jeremy

After spending hours digging through the code and looking at the database, I discovered that this is being caused by the new revisions in 2.6. To disable them, just add:

define (‘WP_POST_REVISIONS’, 0);

to your wp-config.php and the problem disappears.

After spending hours digging through the code and looking at the database, I discovered that this is being caused by the new revisions in 2.6. To disable them, just add:

define (‘WP_POST_REVISIONS’, 0);

to your wp-config.php and the problem disappears.

After spending hours digging through the code and looking at the database, I discovered that this is being caused by the new revisions in 2.6. To disable them, just add:

define (‘WP_POST_REVISIONS’, 0);

to your wp-config.php and the problem disappears.

*bump*

Still exists in 2.5.1