Using with W3 Total Cache
-
Is it possible to use this cache plugin for pages – but also use W3 Total Cache for minifying and combining js and css files?
Thanks
-
Hi Lisa
Thanks for your reply. I just tried installing LiteSpeed Cache. I deactivated page cache in W3 Total Cache first – and deleted the cache. When I activated LiteSpeed Cache plugin unfortunately it does not appear to be working.
Pages are slower loading and I’m not seeing ‘<!– Page generated by LiteSpeed Cache on 2017-07-31 15:56:52 –>’ at the foot of pages.
Is there anything else I need to do?
Thanks
Did you see any message when you visit wp-admin lscache setting?
I see this message:
‘Please disable/deactivate any other Full Page Cache solutions that are currently being used. LiteSpeed Cache does work with other cache solutions, but only their non-page caching offerings—such as minifying css/js files. For this scenario only, please uncheck “Check Advanced Cache” in LiteSpeed Cache settings.’
I tried disabling W3 Total Cache. It makes no difference, so it looks like something else is stopping the LiteSpeed plugin from working.
Please check after you disabled other full page cache plugins if you still have their
wp-content/advanced-cache.phpfile or not. Lscache check full page cache plugins by that file’s owner.Actually, it’s good that you see that message. It indicates that W3 Total Cache is working as expected, and that LSCWP has noticed it.
Go ahead and re-enable W3 Total Cache, and then you need to tell LSCWP not to use the Advanced Cache file: navigate to LiteSpeed Cache > Settings > Advanced and un-check the
Include advanced-cache.phpbutton. We don’t need to use that file, if W3 Total Cache wants it.Now, go back to your website, reload the page a few times, and view source to see if that
<!– Page generated by LiteSpeed Cache on 2017-07-31 15:56:52 –>message appears now.If not, let us know!
-
This reply was modified 8 years, 9 months ago by
LiteSpeed Lisa. Reason: typo
Hi
Thanks for the info. Unfortunately It still does not work. I’ve raised it with my hosting provider in case they need to tweak something at their end.
If you want you can create a ticket so we can login to your server and wp-admin to figure out why.
I’m still not seeing the message <!– Page generated by LiteSpeed Cache on 2017-07-31 15:56:52 –> in source, however running pingdom speed tools reveals the site is as fast as with W3 Total Cache enabled and response headers give the following:
Response Headers200
dateTue, 29 Aug 2017 22:20:40 GMT
content-encodinggzip
versionHTTP/1.1
x-powered-byW3 Total Cache/0.9.5.4
x-litespeed-cachehit
status200
alt-svcquic=”:443″; ma=2592000; v=”35,37,38,39″
content-length7443
pragmano-cache
serverLiteSpeed
varyAccept-Encoding
content-typetext/html; charset=UTF-8
cache-controlno-store, no-cache, must-revalidate, post-check=0, pre-check=0
accept-rangesbytesl
ink<https://www.site.com/wp-json/>; rel=”https://api.w.org/” <https://www.site.com/>; rel=shortlinkexpiresThu, 19 Nov 1981 08:52:00 GMT -
This reply was modified 8 years, 9 months ago by
The topic ‘Using with W3 Total Cache’ is closed to new replies.