v3.5 used a new way to do CSS/JS optimization. If you have those options ON, you may need to check them one by one to figure out which one caused the issue. Usually the exclude option will finally fix this issue.
@hailite Thanks for the update. I went back to LSCache 3.4, this site is live and I can’t play around with optimization exclusions and have all the important pages (faceted events, faceted maps) not work.
Not very happy that now our cache plugin also needs to be tested for breaking stuff between releases, TBH.
We are trying to minimize the impact between major releases. However, CSS/JS optimization improvement is always tough to make. I am happy to help if you need.
You can find me from our slack, or WP’s official slack @litespeed.
Tested LCcache 3.5.1 on a local site with facetwp yesterday… using the same js excludes as LSCache 3.4.x, facetwp stops showing facet selections as soon as JS concatenation is enabled. Is 3.5 more aggressive in changing how files are loaded, even for excluded files?
@philbee
Do you mind to give v3.5.1-rc3 a try? In this version, I added a backward compatibility option JS Combine External and Inline default to OFF, which will give the sites which has been optimized in v3.4.2 better compatibility. That is to say, hopefully you won’t see any page layout broken when upgrading from v3.4.2 to v3.5.x anymore.
You can easily try it by LiteSpeed wp-admin menu Toolbox -> Beta Test, then type the latest commit link listed on https://github.com/litespeedtech/lscache_wp/commits/master . The v3.5.1-rc3 commit link is https://github.com/litespeedtech/lscache_wp/commit/f52ff583712ab748edf3366e74152473bc954671
TIA.
Plugin Support
qtwrk
(@qtwrk)
Hi,
I’m going to mark this topic “Resolved”, due to lack of activity.
If you still need help, please feel free to re-open it.
Best regards,
