LiteSpeed Technologies

Hi @greencode

Could you check the permissions for the .htaccess file? Sometimes, the permissions may be altered such that the file is not writable for security reasons. In these situations, we cannot write to the file.

Yes, that is the last proper hook to add a purge tag.

Hi @infokurs

Raul from Fast Velocity Minify will be adding LiteSpeed Cache support in the coming days, hopefully that will fix the interaction.

Cheers,
Kevin

Perfect, thanks!

Ah, someone just asked about your plugin!

If you’d like, we can validate your modifications and add your plugin to our list of compatible plugins when it’s available.

Let us know if you run into any problems!

Cheers,
Kevin

We’ll look into it!

Cheers,
Kevin

Hi @alignak

Our list of third party functions are in litespeed-cache/includes/class-litespeed-cache-tags.php

If you are looking to purge everything on the site, you can do

if (class_exists('LiteSpeed_Cache_Tags')) {
    LiteSpeed_Cache_Tags::add_purge_tag('*');
}

However, if you’d like, you can also tag pages with an identifier so that you can take advantage of the smart purge feature.

When you know a page has a certain feature, you can tag it. E.g. a gallery plugin might know a page has gallery id 4. They would do:

if (class_exists('LiteSpeed_Cache_Tags')) {
    LiteSpeed_Cache_Tags::add_cache_tag('g.' . get_gallery_id()); // adds g.4
}

Then later, when they need to purge:

if (class_exists('LiteSpeed_Cache_Tags')) {
    LiteSpeed_Cache_Tags::add_purge_tag('g.' . get_gallery_id());
}

Let me know if you have any more questions about this! We have a wiki article here, but I can also answer any questions here.

Cheers,
Kevin

Hi Richard,

Our plugin operates by hooking into the WordPress and WooCommerce processing.

I’m not sure how technical I can get with this, but any time posts (which products are counted as) are edited/saved, or the WooCommerce ‘woocommerce_after_checkout_validation’ action hook is triggered, the plugin will purge the related product.

It looks like they have a free version, so we’ll look into that plugin to see if we can spot anything. I’ll let you know if we find anything out or if we need more information from you.

Cheers,
Kevin

Hi @cybmeta

Thanks for the kind words!

If you are willing to share with us any stats that you were able to gather, we are very interested in seeing them. Please send us an email if you can!

Cheers,
Kevin

@hieutnm,

Apologies, thought we replied to this.

Unfortunately, the actions required to fix the issue requires WHM access, not cPanel. The easiest way to get this resolved is to request that the server admin submit a ticket to our ticketing system. We will be able to work with them to get this resolved ASAP.

Cheers,
Kevin

If you have the capability to, please check the server cache root setting. Those headers usually mean that the cache was unable to store the cache entry.

If you are with a shared host, please contact your hosting provider to do the check. This is the relevant wiki article: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:common_installation#web_server_configuration

Let me know if there are any questions about this!

Kevin

Hi @hieutnm

Your .htaccess ruleset contains different rules than normal WordPress, so I’m not 100% sure about all the rules that you will have to move.

That said, The LiteSpeed Cache rules must be before the WordPress rules that involve url rewriting, specifically:

RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

If you have nothing against it, you could try moving the entire BEGIN/END WordPress section to the bottom of the .htaccess and see how that works for you.

As always, before making any changes, please make a backup of your current .htaccess.

Let me know how it goes,
Kevin

Thanks for the kind words!

Let us know if you run into any issues!

Cheers,
Kevin

What happens if you try to downgrade to 1.0.14.1?

If it works, could you send an email to the email listed on the plugin description? Include a link to this thread so we have some context as to what the issue is.

If it does not work, it is likely due to a change in another plugin, and we cannot assist with that.

I don’t see anything specifically that will set the browser cache. Could you DEACTIVATE LiteSpeed Cache and see if the browser cache works?

If DEACTIVATING LiteSpeed Cache does not change anything, try adding the following rules to your .htaccess file:

ExpiresByType text/css                  "access plus 1 year"
ExpiresByType application/javascript    "access plus 1 year"