Raam Dev

Hi @misstandme, it looks like you’re using Independent Publisher 2, which actually has its own support on WordPress.com and is separate and a bit different from the theme hosted here on www.ads-software.com.

Please ask for help with Independent Publisher 2 here: https://wordpress.com/theme/independent-publisher-2/support

@t0pforex Apologies for the very delayed reply. I just took a look at the code and it looks like that 100×100 version is getting set here.

I’ve created an issue on GitHub to track this issue and get it fixed for the next release: https://github.com/raamdev/independent-publisher/issues/314

@t0pforex Do you have a link to a page where this is happening?

Thanks for the 5-star review, @smitpatadiya! ??

Thanks for the 5-star review, @kevinkovadia! ??

Hi @sterndata,

We have an article here that covers that: https://cometcache.com/kb-article/how-can-i-exclude-the-home-page-from-being-cached/

You can use ^/$ (which is regular expression for starts with and ends with /, which would be the home page).

Hi @ianatkins,

The “failed to open dir: Too many open files” message is related to your hosting environment, so you’ll need to check with your web hosting company to see what can be done to increase the number of files that can be open at the same time. This article has some more information that may be helpful: https://stackoverflow.com/a/14749074

Looks like Comet Cache is clearing the site cache on order update, is it possible to disable this.

In Comet Cache Pro you can disable the automatic clear/wipe routines, however this is not recommended. The cache is cleared automatically when specific events occur specifically to ensure that an out-of-date cache file does not get served to a visitor. For example, if your site shows the quantity of an item available, you would want the quantity to change for future visitors whenever someone purchases the item. If the cache was not cleared automatically, the wrong quantity may be shown.

My recommendation would be to check with your web hosting company to increase the number of files that can be open at any given time.

@the-moose Yes, please see Comet Cache → Plugin Options → URI Exclusion Patterns

@bereshka Thank you very much for sharing your solution here. I’m glad to hear you solved the problem. ??

@hb101 I checked your site and it looks like you’re still using Comet Cache and the site appears to be loading fine.

If you’re still having trouble, I recommend trying to deactivate Comet Cache to see if that solves the problem. If it does not solve the problem, then you know it’s not Comet Cache that’s causing the problem.

Hi @lucasbustamante,

OPCode caching is part of PHP itself, so you would need to enable in the PHP configuration. It’s not something that a plugin like Comet Cache can enable.

If Comet Cache detects that OPCode caching is enabled in PHP, it will automatically clear the OPCode cache when you click the Clear Cache button. In the Pro version, there’s a separate button to clear only the OPCode cache.

I’m sorry to hear that you were not satisfied.

Browser Caching is actually something that needs to be enabled at the web server level, so Comet Cache’s Leverage Browser Caching feature simply adds the necessary rules to your .htaccess file to enable browser caching in your web server.

Here’s the code that Comet Cache adds; you can just copy and paste this into your .htaccess file to enable browser caching:

# Enable browser caching.
FileETag mtime size

<IfModule expires_module>
  ExpiresActive on
  ExpiresDefault "access plus 1 week"
</IfModule>

@valuewordpress this is not possible at this time, but I think it’s a great idea and I’ve created a feature request here so that we can hopefully get this worked into a future release: https://github.com/websharks/comment-mail/issues/348

Many of the visual editor and page builder plugins that I’ve seen for WordPress have their own caching systems built-in that store pre-generated CSS/JS files either inside the cache directory or inside the uploads directory. That often causes problems when there’s another caching plugin enabled (it’s not a problem unique to Comet Cache).

Unfortunately this is something the page builder plugins would need to take into consideration. It’s possible they’re changing their own internal cache without hooking into actions that would normally cause the installed caching plugin to clear its entire cache. That might result in a cached page referencing a now-deleted CSS/JS file that the page builder plugin had cached, thereby causing visual elements on the page to look broken until the cache is manually cleared.

Comet Cache hooks into dozens of actions throughout WordPress Core to listen for various events that would warrant an automatic clearing of the cache, things like save_post and edit_post. It also hooks into various actions that fire when themes are changed, updated, etc. A plugin that creates its own cache should be firing one of these well-known hooks so that anything else (such as Comet Cache or another page caching plugin) that listens for those important events knows that it should also clear its cache.

@valuewordpress Thank you for the report.

With the Lite (free) version of Comment Mail, you only have access to the Simple Templates, which don’t have all of the strings translated.

With the Pro version of Comment Mail, you can use the Advanced Templates that include PHP and do have all of the strings translated.

I opened a GitHub issue to hopefully get this fixed in a future version: https://github.com/websharks/comment-mail/issues/347

In the meantime, you can edit the text directly in Comment Mail → Site Templates → Comment Form Subcr. Options.