Localise Resources feature is broken

  • Resolved redbullpeter

    (@redbullpeter)


    3 years, 11 months ago

    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.

    I’ve tested this with scripts from a range of companies, FB, Twitter, Google, etc.

    I’ve logged the issue in Github: https://github.com/litespeedtech/lscache_wp/issues/462

    I’m posting this for anyone who’s wondering why features provided by 3rd party scripts are not working.

    • This topic was modified 3 years, 11 months ago by redbullpeter.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support qtwrk

    (@qtwrk)

    3 years, 11 months ago

    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.

    Thread Starter redbullpeter

    (@redbullpeter)

    3 years, 11 months ago

    @qtwrk – The issue isn’t limited to FB or Google. I tested it with Twitter, Hotjar, tiktok and my own dev server. All had the same issue.

    Alexander S. Kunz

    (@antermoia)

    3 years, 8 months ago

    So I’ve been pulling my hair because my Jetpack Stats stopped working after activated LS Cache, and it appears that this is the cause?

    I’ve disabled the localization feature, but wouldn’t it be nice if LS Cache had a built-in exception list to automatically exclude resources that are known to break when they’re localized?

    Thanks, glad that I found this thread,
    Alexander.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Localise Resources feature is broken’ is closed to new replies.