Raam Dev

@jeriksson As per the WordPress Support Forum Guidelines, we’re not allowed to discuss or provide support for Pro products here. You’ll need to use our community forum or open a ticket.

add_filter(‘zencache_disable_auto_wipe_cache_routines’, ‘__zencache_disable_auto_clear_wipe_cache_routines’, 10, 0);
add_filter(‘zencache_disable_auto_clear_cache_routines’, ‘__zencache_disable_auto_clear_wipe_cache_routines’, 10, 0);

If you’re using Comet Cache, those should be using comet_cache instead of zencache.

Second i have routine to clear home page + assosiated category and tag archives for each post that gets published. Both home page clear and category clear works, the tag archives are not cleared though on initial publish of new post!

I’d need to see that routine before I can offer any more advice to troubleshoot. Since you’re using the Pro version of Comet Cache, please open a thread on our community forum or open a support ticket and include the custom code that you’re using so that I can take a closer look.

• This reply was modified 9 years, 9 months ago by Raam Dev.

Comet Cache caches things based on the Request URI received by PHP. If you’re seeing other domains appearing in your cache directory, that would indicate that your web server is not properly rewriting those requests to the proper domain (using something like an .htaccess file) or that your web server is misconfigured in some way. In either case, I highly recommend contacting your web hosting company about this to have them fix it.

Comet Cache supports caching multiple domains in the way you’re seeing because some site owners use mapped domains, where they use multiple domain variations for a single site. If you want to tell Comet Cache to ignore all requests except those coming from a specific hostname, you could add something like the following to your wp-config.php file (replace www.example.com and example.com with your domain):

if ( $_SERVER['SERVER_NAME'] !== 'example.com' || $_SERVER['SERVER_NAME'] !== 'www.example.com' ) {
     define('COMET_CACHE_ALLOWED', false);
}

I found that the pre-update version managed to update okay; but I found that the post-update version was showing this error:

@whitelamp So you’re saying that after you restored the site from a backup and then updated Comet Cache to the latest version, everything worked fine?

Can you tell me which version of PHP you’re running and whether or not PHP OPCache is enabled?

I get no css on mapped domains and 502 gateway errors. As soon as I disable the plugin everything functions normal.

@fla0 Are there any clues in your web server log files that might explain what’s generating the 502 gateway error?

Can you tell me which version of PHP you’re running and whether or not PHP OPCache is enabled?

@teknofilo When I checked bottom of the source of that page, I see 4 blank lines. This is common when you’re running or integrating with something else (such as CloudFlare) that might be stripping out HTML Comments from your page. See this KB article: What if I just see blank lines at the bottom?

@dblinks @eskapism Thanks for the report! The latest version of Comet Cache Lite (hosted here on ww.wp.xz.cn) doesn’t actually use Chart.js (it’s only used in the Pro version), however the latest Comet Cache update added a Pro-only feature to the Lite version and as part of that work Chart.js was unnecessarily enqueued. I’ve filed a bug report to get this fixed for the next Comet Cache release.

@andrew1977 Hey Andrew, a 500 Error sounds like a web server error, so the web server logs would be the best place to look for clues. The only thing that Comet Cache does that might cause issues with the web server is write to the .htaccess file (assuming you’re running the Apache web server). However, this is not something new in the latest version — I can’t think of any changes in the latest release that would cause problems with the web server. Also, Comet Cache never touches the .htaccess file unless you’ve specifically enabled an option in the plugin to do so.

So, the two places I would look are your .htaccess file (if you have one), to see if there might be something corrupt in there that’s causing the web server to throw a 500 error; and your web server log files, to see more details about what exactly is causing the 500 error. If you’re not sure where that log file is, or if you don’t have access to it, your web hosting company should be able to help you.

The same filters to empty the cache whenever a plugin is updated will be triggered if you perform remote updates by using JetPack control panel or systems like InfiniteWP, right?

Yes, any time a plugin is updated — no matter where it’s updated from — the old plugin will be deactivated and the new version of the plugin activated, at which time the activated_plugin hook will fire and the cache will be cleared.

The latest version of Comet Cache (v160917, released today) includes changes related to this GitHub issue. Please see the full changelog:

Bug Fix: Fixed a bug where upgrading from v160521 would result in the Client-Side Cache option being reset to the default (disabled). If you enabled the Client-Side Cache at some point, now is a good time to double-check that it’s still enabled. This bug fix also improves the reliability of all version upgrade routines that Comet Cache runs during upgrades. See Issue #807.