Raam Dev

@sunset-cowboy We do most of our Comet Cache development testing on PHP 7 and haven’t seen this issue. Could you try uploading a phpinfo.php file to the site with the following inside and then visit that file in your browser to verify that you’re actually running PHP 7?

<?php
phpinfo();

@bb3lions @mduh My only guess is that you’re both using something older than PHP 5.3, as that’s the version where the __DIR__ magic constant was introduced. The comet-cache.php file is very simple: It just loads plugin.php, but it does so using a magic constant to figure out the full path to that file:

__DIR__/plugin.php

Comet Cache requires PHP 5.4+ and there’s a version check that prevents Comet Cache from crashing when you’re running something older than PHP 5.4, but that version check happens inside plugin.php, which is too late to catch the fact that the __DIR__ magic constant might cause a fatal error if you try installing on something older than PHP 5.3.

I’ll open a GitHub issue so that we can get this fixed in the next version, but if you could confirm that you’re running something older than PHP 5.3, that would help confirm this.

@futtta Comet Cache uses 0775 for permissions when creating the cache directory; see https://github.com/websharks/comet-cache/blob/160521/src/includes/traits/Plugin/InstallUtils.php#L356

See also: http://permissions-calculator.org/decode/0775/

It sounds to me like the web server in question is misconfigured (or recently had its configuration changed).

@flyfisher842 Thanks for the update! I’m glad you got this resolved. 🙂

@raamdev I asked about Comet Cache Pro because Logged-In User caching is a Pro-only feature and it sounds like you’re seeing logged-in users being cached. Even if you were, the Pro-only Logged-In User caching feature does not apply to the WordPress Login Page—there is no scenario that I can think of with Comet Cache where the login page would ever be cached.

Were you using a different caching plugin before Comet Cache? If so, maybe that caching plugin generated the cache file that includes your username.

If not, can you tell me the exact path to the cache filename where you found your username? (e.g., wp-content/cache/...) The full path to the filename will help.

@bobinoz We’ve been having some trouble reproducing the issue described in the GitHub issue you linked to, and that’s making it difficult to pinpoint what the cause is. However, your report makes 3 cases of this so far, so it’s definitely an issue.

If you could leave a comment on the GitHub issue with a list of your active plugins, that would be a huge help. My only guess at this point is that there’s another plugin conflicting with Comment Mail, because we haven’t been able to reproduce the issue in a clean WordPress install with only Comment Mail running.

I’ll also add a link back to this thread in the GitHub issue.