Wordpress LScache Plugin: Thrive Comments load intermittently
Last Updated on: Wed, 15 Apr 2026 00:00:02 Howdy! I have a very intermittent issue going on for months and I dont know where to start with tracking down the cause. It seems that periodically, the comments on my blog posts stop loading. I am using the Thrive Comments plugin. As soon as I disable the LiteSpeed caching plugin, the comments work fine. I have almost everything disabled that can be disabled in the Litespeed plugin and it still acts up. But unfortunately I dont know how to tell you to replicate it as I havent been able to find a pattern yet. It seems that if I clear the Litespeed cache, the comments work for a little while. I contacted Thrive Themes about this some time ago and they said the issue was on Litespeeds end and I should contact you. Thanks so much for any help you can lend in getting this working. I see that I am not the only one who has had issues with Thrive Comments and Litespeed Caching Plugin. Here is my system report number: IMPEKPTL The page I need help with: https://www.susprep.com/off-grid-misc/diary-of-a-blessed-garden-our-story-of-thanksgiving/ Hi @nickm77, This usually happens when that plugin is using WP nonce which could expire if hardcoded in that page. Did you try to disable the option Enable LiteSpeed Cache in our settings? If you can give the link which is having that issue, it could be easier for us to debug. https://i.imgur.com/539VVoE.png By this you can see there is a sub request to grab the comments. https://i.imgur.com/ohNSaFK.png here you can see it has nonce. They can consider to use our API to generate that nonce. Here is the ref: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscwp:esi_sample Thanks for your comment. Yes, if I use the disable toggle in the general settings of the Litespeed Cache plugin, then the comments load just fine. Is that what you are referring to? The links that have this issue are all of our blog posts (which are the only pages on our site with comments enabled). So the link I gave above is one that was experiencing this issue a couple days ago. But I disabled the Litespeed Plugin and as usual it works now. So Im sorry to say I dont know how to replicate this issue for you. I saw a previous post where someone else was having an issue with Thrive Comments and Litespeed Caching, and his issue would trigger after 24 hours from when the cache was purged or something like that. So I dont know, maybe it happens in a certain time frame like tha? Any ideas on how I could exclude the entire comments plugin from being cached? I thought I did, since I have almost everything in the Litespeed caching plugin turned off/disabled, but I still keep running into this. So what is my next step in trying to get to the bottom of this? By saying almost everything in the Litespeed caching plugin turned off/disabled did it include the cache enable setting we just talked? If the issue only come after 24hours, that is bcos the ttl setting is 24hours basically. You can change the ttl to 12 hours. That way nonce wont expire anymore. This is just a temporary solution. The permanent fix is to deploy ESI on that plugin side. What I was referring to is that I have the Litespeed Cache plugin enabled (on the plugins page) AND I also have the enable/disable toggle set to enable on the Litespeed Cache general settings page. But almost everything else is turned off in an effort to keep Litespeed Cache from caching the comments. Let me make sure I understand. I should set the Public Default Cache TTL to a setting less than 24 hours? Does it need to be 12 hours or could it be anything less than 24 hours (like 18 or 20 hours)? I understand that this is a temporary solution, but anything would help at this point because if I cant get this resolved I either have to get rid of Litespeed Cache or Thrive Comments, and I really like both. Thanks again for your help. Yes, you can try to set Public TTL to 12 hours. No, higher number may encounter expired nonce too. Hi, Nickm77 Let me try to explain the issue. Thrive Comments uses a nonce for security purposes. You can learn more about that in the WP Codex. Nonces are useful, but they expire after 12 hours, and this causes problems if they are included on pages that are cached for longer than that. This is why changing your TTL to 12 hours is a short-term work-around. To solve the problem permanently, Thrive Comments would need to make a small change in their code, which weve documented on our wiki. Essentially, anywhere they create a nonce, they should use our API nonce function in place of the WP function. Our function simply creates an ESI block, sets that blocks TTL to 12 hours, and then calls the WP nonce function. So for you, the comments would become an ESI block, and would expire from cache after 12 hours. The nonce would be properly handled, and you would be free to set your sites TTL to whatever you like. I hope this clears it up. Please let us know if you have any other questions! P.S. If you are unfamiliar with ESI, take a look at this blog post. (Example #2 in that post is more relevant to your application than Example #1.)
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference