Plugin Support
qtwrk
(@qtwrk)
Guest Mode, Mobile Cache , Webp replacement , JS/CSS minify , JS/CSS combine
these options will need to be disabled if you want to use APO
Thread Starter
sbence
(@sbence)
Hi,
thank you for your answer! Thats a lot, as I disabled inside Cloudflare the minify settings. Can I ask what happens if I don’t disable them? As this could hurt the performance to my knowledge, no?
Thanks for the answer!
Best,
Bence
Plugin Support
qtwrk
(@qtwrk)
you will hit issue like CSS/JS lost
our plugin will minify/combine JS/CSS with a md5-hashed file name , like /wp-content/litespeed/css/xxxxxxx.css , but this name could be changing depends on file content, by that saying , if CF cached page with old CSS links , and you did a purge , then old CSS files will be removed and generate new file with name new , then the old link will become 404 error
Thread Starter
sbence
(@sbence)
Hi, thanks for explaining!
Doesn’t this greatly decrease the performance?
Plugin Support
qtwrk
(@qtwrk)
sort of, yeah , that’s why we don’t recommend to run our plugin with APO
Thread Starter
sbence
(@sbence)
In the beginning I wanted to use Quic.cloud CDN, but the monthly limit is very small, are there any recommendations then?
Plugin Support
qtwrk
(@qtwrk)
you can keep use CF, but just don’t enable APO , use it as static CDN
Thread Starter
sbence
(@sbence)
I tried that first, when I did that the homepage was cached in a ways, that it didn’t show me that I was logged in, while I was, it was cached incorrectly.
Plugin Support
qtwrk
(@qtwrk)
please check the http response header , looking for x-litespeed-cache and cf-cache-status header
If you purge server side cache, APO is supposed to detect it and invalidate old files and cache new ones at the edge. You can also purge server cache then Cloudflare’s cache to resolve this with APO.
