Wordpress LScache Plugin: Localise Resources feature is broken
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, I discovered that my FB pixel was no longer sending any data. After much investigation it turns out that any script that is listed in the Localise Resources is returning a 404 when the local url is referenced. Ive tested this with scripts from a range of companies, FB, Twitter, Google, etc. Ive logged the issue in Github: https://github.com/litespeedtech/lscache_wp/issues/462 Im posting this for anyone whos wondering why features provided by 3rd party scripts are not working. This topic was modified 6 months, 2 weeks ago by redbullpeter. yes, sometimes the remote resources forbids local application to retrieve it , then it will ended up broken or 404 this is something we are still working on it. @CacheCrawler ? The issue isnt limited to FB or Google. I tested it with Twitter, Hotjar, tiktok and my own dev server. All had the same issue. So Ive been pulling my hair because my Jetpack Stats stopped working after activated LS Cache, and it appears that this is the cause? Ive disabled the localization feature, but wouldnt it be nice if LS Cache had a built-in exception list to automatically exclude resources that are known to break when theyre localized? Thanks, glad that I found this thread, Alexander.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference