Raam Dev

@menathor Hey 🙂

You asked, “is it beneficial for Comet Cache to cache streaming media”, to which I was responding that Comet Cache does not cache streaming media… in fact, it doesn’t touch static resources at all. If you have a media directory on your server, there’s no way to tell Comet Cache to exclude that directory because Comet Cache only sees WordPress posts/pages. It does not ‘see’ static files on the server because it’s a WordPress caching plugin, that hooks into the WordPress caching system. The URI Exclusion patterns will only work with URLs that WordPress is serving. (If you link directly to a media file, your web server is serving that file, not WordPress.)

So, to answer your question, Comet Cache won’t have any effect on, or interfere with, your media files.

I hope this clarifies things a bit!

@nineplanetsllc Right, that’s not actually a stacktrace at all. It sounds like your web server doesn’t have the XDebug extension installed (many don’t, as it’s really only something that’s needed for development and not for production servers).

I’ve gone ahead and opened a GitHub issue for this so that we can investigate:
https://github.com/websharks/comet-cache/issues/910

That report is a false-positive. Comet Cache and Comet Cache Pro are fully compatible with PHP 7 and they’re being used on many production sites running PHP 7 (including our own sites).

The PHP Compatibility Checker is reporting false info. Comet Cache Lite was whitelisted by the plugin, but Comet Cache Pro, which runs on the same codebase as the Lite version, was not whitelisted because it’s a commercial plugin.

Please see the full report here: https://ww.wp.xz.cn/support/topic/false-positive-comet-cache/

@sheldon-64 If you’re not seeing this issue on other sites hosted on the same server, that’s a good thing, as that issue is usually due to a problem on the server where Comet Cache is unable to properly clean up files.

Since you’re not seeing the problem with other sites on the same server, that points to, as you said, a likely plugin conflict. Please see this article for details on what we recommend in this case.

@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.

Hey @albertoita,

We have a GitHub issue open to track this here:
https://github.com/websharks/comment-mail/issues/267

All updates as far as progress on this issue will be reported there, so that’s the best place to stay up-to-date and show your vote for this feature. I’ve mentioned this thread on that GitHub issue.

I don’t have anything in the way of a timeline at the moment, but I do see this being worked on sooner rather than later. 🙂