Comet Cache not caching WordPress front page

  • Resolved saintandrews

    (@saintandrews)


    8 years, 10 months ago

    This topic has come up previously, both here and on the WPSharks community forum, though without resolution as far as I can tell.

    I recently noticed that, when logged out and with all browser history cleared, my front page is returning

    <!– Comet Cache is NOT caching this page, because the current user visiting this page (usually YOU), appears to be logged-in. The current configuration says NOT to cache pages for logged-in visitors. This message may also appear if you have an active PHP session on this site, or if you’ve left (or replied to) a comment recently. If this message continues, please clear your cookies and try again. –>

    while each individual article page is serving the appropriate cached version as it should be. Same with either Firefox or Chrome.

    Frankly, I don’t know if the front page notice is real or merely a “ghost” notice – that is, whether it is in fact cached while saying it’s not or whether it is actually not cached and thus costing the site unnecessary loading speed.

    Any guidance appreciated.

Viewing 1 replies (of 1 total)
  • Raam Dev

    (@raamdev)

    8 years, 9 months ago

    @saintandrews If you’re not logged in and you see that note at the bottom of the page source, that would indicate that Comet Cache thinks you’re logged in. (Note that those HTML comments that Comet Cache adds are never cached, so if you’re seeing an HTML note from Comet Cache in the page source, that’s a dynamically generated note at the time the page was being loaded, even when loading a cached file.)

    The most common reason for this is the presence of a cookie in your browser that gets stored by WordPress when leaving a comment on a post. When you leave a comment on a post (as a not-logged-in user), WordPress writes a cookie to your browser that puts you in a “semi-logged-in” state. You’re not actually logged in, but you’re not completely logged out either. (This is how you can post a comment on a site that requires moderation, but still see your comment show up with “Your comment is awaiting moderation” above it—WordPress is identifying you by reading that cookie that was stored in your browser when you posted the comment).

    If someone posts a comment on a WordPress site, Comet Cache treats that visitor as logged-in and doesn’t cache requests by that user (unless Logged-In User caching is enabled—a Pro-only feature).

    However, since you said that other pages on the site appear to be cached normally, that would tell me there’s something else going on, most likely some sort of conflict related to your theme and/or another plugin you’re running. See this article for suggestions.

    There’s more discussion on the WP Sharks community forum here.

Viewing 1 replies (of 1 total)

The topic ‘Comet Cache not caching WordPress front page’ is closed to new replies.