Very frequently, I believe it could be every ~1h (1h was the shortest amount of time I noticed that it loads all pages again) the cache is purged without any actions, scheduled actions or even without a trace in logs.

After enabling logs with advanced debug level, there is nothing related in Debug log and purge log is completely empty (it populates with manual actions, but I’m clearing it before proceeding with test).

– Site is currently in development and there is no traffic (and orders that could somehow triger purge).
– TTLs are default, so for public pages 1 week
– Auto-updated are disabled
– Latest LiteSpeed cache plugin version

This wasn’t a case with WP Fastest Cache, but I would really like to stick with LiteSpeed as it performs much better except this issue.

Any ideas?

Is it possible to convert my custom shortcode into an ESI block?

function display_random_text() {
    // Array of texts
    $texts = [
        "Text 1",
        "Text 2",
        "Text 3",
        // Add more texts here
    ];

    // Randomly pick a text
    $random_text = $texts[array_rand($texts)];

    // Return the text
    return $random_text;
}

add_shortcode('random_text', 'display_random_text');

After the cache expires can I run the crawler?

Would running the crawler right after the cache expires re-cache all my pages, post, categories and tags?

I’ve purged the cache, UCSS, CCSS, purge ALL, uninstalled the plugin, reinstalled it, and nothing works. Even when programmed for one year (31557600s), the HTML still reflects only one week (7 days = 604800s).

Here some images:
Setup
html
PageSpeed

Has anyone experienced something similar or have any suggestions on how to resolve this issue?

I appreciate any help in advance!

1. Default TTL is 0, that does mean that keys in Redis Cache never expire or that object caching is running but having no effect? Based on this answer https://www.ads-software.com/support/topic/wp_redis_maxttl/ I would assume 0 means forever
2. Assumtion: If TTL is set to e.g. a week which is you standard recommendation for first tests what does that mean? The underlying DB is in my case MYSQL. If there is a select on the DB and TTL is a week the data will be stored for a week in object cache before expiring. If data is changed this is done via Redis object cache before it gets to DB and Redis is tracking the change (if client requires that based on https://redis.io/docs/manual/client-side-caching/) so there is no possiblity of changed data which is missed by the cache? Which means the only disadvantage of high TTL is memory usage and maybe speed if cache is to big? Is that assumption right or wrong?
3. Default setting is to exclude plugins and themes. Is it a bad idea in general to cache that or is it just for safety reasons because you don’t know how plugins / themes would behave in this context?

We have a couple of custom RSS feeds. After activating LiteSpeed Cache, these feeds are no longer refreshed for our users. Updates can take a couple of days, and I’ve tested with three different RSS clients. The feeds are configured to update hourly, LiteSpeed Cache’s TTL for feeds are set to 0 seconds (disabled), and ‘/feed/’ is an LiteSpeed Cache excluded URI. Does anyone have an idea of what could cause this issue?

These are the affected feeds:

https://nikkasystems.com/feed/sakbub-jobs

https://nikkasystems.com/feed/sakbub-events

Link to site: https://lovebug.beauty/
Report number: YIFWPQGL
Link to Lighthouse test: https://www.webpagetest.org/result/230614_AiDcGF_95/
Link to Screenshot from Lighthouse test: https://lbv1.domainactivation.com/mw459.jpg
Instructions to reproduce the issue: Simply enter Lovebug.beauty into the Lighthouse entry box at https://www.webpagetest.org/lighthouse and press Start Test button.

Thank you,
Julien

report number: JYKLJXGL

first of all, the crawler was working until 3 days before but after that I show this status in crawler section of plugin : the crawler is disabled. I asked it from hosting provider and they say everything is ok in server side.

another problem is short age of cache! I set 1 week TTL for public cache (none logged-in), and pages will be cached if visitors see that or crawler (before above issue) crawled those. when I check pages immediatly, it shows x-litespeed-cache: hit in chrome console, but after short time (sometimes less than 5 minutes, sometimes more and it’s up to 2 hours!) it shows x-litespeed-cache: miss.

I also check this in this site: https://check.lscache.io/

I disabled auto update and also purge all if a plugin or a theme updates and i don’t edit pages or data when I want to check this. it’s a simple woocomerce website and I don’t use some dynamic related widget for example “user recently viewed products” and something like this.

please help me.
thanks …

report number: JYKLJXGL

According to GTmetrix, all my files have a Cache Policy of “none” – even though the following code (this is just a snippet of it) was written into my .htaccess by W3TC:

<IfModule mod_mime.c>
    AddType text/css .css
</IfModule>

<IfModule mod_expires.c>
    ExpiresActive On
    ExpiresByType text/css A15768000
</IfModule>

Neither does this work, when I type in the following code by hand:

<IfModule mod_expires.c>
    ExpiresActive On
    ExpiresByType text/css "access 1 month"
</IfModule>

However, when I write this into .htaccess, it is mostly recognized:

<filesMatch ".(ico|pdf|flv|jpg|jpeg|png|gif|svg|js|css|swf)$">
    Header set Cache-Control "max-age=84600, public"
</filesMatch>

BUT: While this works on .png and .jpg files, this only changes the TTL for .js files I have in my list of “Never minify the following?JS?files”. The minified .js files still have a TTL of “none”.

Can I do anything to fix that? Or does this require a plugin update in the future? Or is it GTmetrix fault and everything works as it should?