Uncaught TypeError: Cannot read properties of undefined (reading ‘w’)

  • Resolved jukkasalm

    (@jukkasalm)


    1 month, 3 weeks ago

    lazysizes.min.js?x23565&ver=720:1 

    Uncaught TypeError: Cannot read properties of undefined (reading 'w')
    at lazysizes.min.js?x23565&ver=720:1:6864
    at l (lazysizes.min.js?x23565&ver=720:1:6897)
    at HTMLDocument. (lazysizes.min.js?x23565&ver=720:1:7017)
    at L (lazysizes.min.js?x23565&ver=720:1:10180)
    at Object.Ae as updateElem
    at ce (lazysizes.min.js?x23565&ver=720:1:13324)
    at he (lazysizes.min.js?x23565&ver=720:1:14361)
    at me (lazysizes.min.js?x23565&ver=720:1:14560)

    I’ve had this error message in the console for a while now, for every page. I checked the old versions of the plugin and pinpointed it to version 7.2.0, that’s when that error got introduced.

    What changed in that version that could be causing it? The site is running Docker on AWS, images are offloaded to S3 with Offload Media if that makes a difference. I don’t use Easy IO.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    Thanks for reporting that, a lot changed in 7.2 though, as the script was completely reworked at that point.

    It’s a bit difficult to match up the error, as character 6864 in the original source has nothing to do with a variable named ‘w’. I would recommend the following:

    1. Make sure you do not have anything altering lazysizes.min.js. That is, turn off any plugins that would minify JS. The file should be exactly 15,853 characters long.
    2. If the issue persists, set the SCRIPT_DEBUG constant in your wp-config.php, and see what the error shows then. We should have a proper line number to reference then (assuming nothing else is trying to minify JS still).
    3. Add the site URL where we can see the issue in action.
    Plugin Author nosilver4u

    (@nosilver4u)

    Forgot to say, the exact line in wp-config.php should be this:

    define( 'SCRIPT_DEBUG', true );

    Plugin Support adamewww

    (@adamewww)

    Hi @jukkasalm

    As we haven’t heard anything about this in a while, I’m going to resolve this thread. However, if you have further questions, please feel free to open a new one.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.