Wont stop caching even after wordpress plugin deleted, cache purged.

P

Pierre Balian

Member
#1
#1
Hello,

We are having the weirdest issue. Today the LSCache wordpress plugin was updated. Not sure that is related to the issue we are having.

We updated some content and tested, it wasn't changing on the frontend. Of course if we are logged in as an administrator we can see the change on the frontend.

I tried the purge all cache button in the wordpress plugin.
I tried purging the page by id with the plugin,
I deleted the plugin, deleted its .htaccess file entries, deleted the advanced-cache.php file from wp_content.

Next I updated litespeed to the latest version. Now there is a new wordpress cache management section in the litespeed admin. I scanned for wordpress sites, it showed the problematic site as being enabled.

So I disabled it.

After all of these changes we still got a cache hit in the response headers and no frontend change.

HTTP/2.0 200 OK
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html; charset=UTF-8
x-pingback: https://www.donatellis.com/xmlrpc.php
Link: <https://www.donatellis.com/wp-json/>; rel="https://api.w.org/", <https://www.donatellis.com/?p=466>; rel=shortlink
Content-Encoding: gzip
Vary: Accept-Encoding
Date: Tue, 06 Sep 2016 16:35:48 GMT
Accept-Ranges: bytes
Server: LiteSpeed
x-litespeed-cache: hit
Content-Length: 9118
X-Firefox-Spdy: h2

Do you have any idea what is going on, and what I can do to fix this?
 
N

NiteWave

Administrator
#3
#3
assume the storage directory is /tmp/lscache
you can try delete all folders/files under it by
#rm -rf /tmp/lscache/*

see if "x-litespeed-cache: hit" still there ?

storage directory in cache policy page is server level directory. above just a quick tests.
also there are virtual host level cache storage root. for example in WHM/cPanel server, default is /home/user/lscache.

in one word, the cache is stored under cache root directory as linux/unix file, if the cache file is deleted, you won't see "x-litespeed-cache: hit".

just a quick reply, giving some extra info.
 
P

Pierre Balian

Member
#4
#4
Hello NiteWave,

Sorry for the late response. Our updates started displaying after the cache expired on its own, and we had other stuff going on so it wasn't a priority.

We just made some updates to another website on our server, and ran into the same problem.

I just cleared the cache per your instructions, the only difference is our cache directory is /tmp/diskcache

Immediately after clearing the cache via shell we can now see our changes, but we do still show a cache hit!
 
You must log in or register to reply here.
Top