Large photos are lazy loaded by other generic lazy loading plugin

  • Resolved Cristi S.

    (@cristiscu)


    6 years, 6 months ago

    There are several tickets lately complaining about duplicates (in fact we see the “noscript” large images when we should not) when we use also a generic lazy loading plugin. Some people use it from JetPack, I am using the “a3 Lazy Load” plugin.

    Disabling our generic lazy loading plugin is not a fix! You should provide some solution to get them work together.

    For instance, with a3 Lazy Load I could specify img class names to be omitted. Unfortunately, your images from noscript tags have no class names. If you would provide a class name for them (same way you do with the thumbnails), we’ll not get those duplicates anymore.

    Any other constructive idea please?

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

  • Hi Cristi ??

    I apologize for any trouble! The only issue we’re currently aware of (as Lazy Load conflicts go) is the JetPack lazy load and that has been reported to the developers.

    Can you please tell me what lazy load version number for A3 Lazy Load you’re running and I can add that for the developers to review as well?

    Thanks

    Thread Starter Cristi S.

    (@cristiscu)

    Version 1.8.7 (always the latest).

    No problem, I was trying to help ??

    From what I’ve seen, A3 will create a visible large image outside the noscript area for each large hidden image. I suspect it’s just similar with JetPack.

    Cheers,
    Cristi

    We’re happy for your help Cristi! ?? I’m going to report this to the developers as well so we can look into this for you!

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Large photos are lazy loaded by other generic lazy loading plugin’ is closed to new replies.