Okay
  Public Ticket #2029562
Thumbnail pictures from sliders are not shown in chromium based browsers
Closed

Comments

  • revosoft started the conversation

    Dear all,

    since the last two or three update versions of the wp layerslider plugin the thumnail pictures are not shown in chromium browsers like Vivaldi, Iron, etc.

    In IE and Firefox the thumbnails are shown correct.

    Can you look for the problem and show me a solution?

    (klick on the frist "+" and look at the projector slider and move the mouse over the numers - in chromium browsers the thumnail pictures are not shown)


    With best regards

      Bodo Olschewski

  • [deleted] replied

    Hello Bodo,

    Thank you for getting in touch with us. My name is Attila and I'm happy to assist you today. I appreciate your patience while we've been working towards your ticket.

    This issue is also happening in other browsers for me, and there seems to be an issue with images in the slider. 

    The sources of the images are getting disrupted/changed. A static URL is placed there instead of the actual source or path of the images. This was most likely done by an image preloader/optimizer/lazy loader plugin or method on your installation. Please try to look for anything similar on your installation that could be affecting the images, and temporary disable it to see if that helps.

  • revosoft replied

    Hi Attila,


    when I disabled lazyload in wprocket, the thumbnails are also shown in chromium browsers.

    The crazy thing is, that it happens only with normal sliders, not with popup sliders. The thumbnails from popup sliders are shown correct with active lazyload in wprocket.

    Do you have any experiencies with incomaptibilty problems between layerslider and wprocket ?

    (at the moment I disable lazyload, but that can be negative for my rankings)

    With best regards

     Bodo Olschewski

  • [deleted] replied

    Unfortunately lazy load methods could easily result in problems like this if they are not careful, as they interfere with the images and their accessibility.

    If you are planning to keep using wprocket's lazy load, I'd recommend to exclude LayerSlider from its target list, so this does not happen. 

    You could also contact the wprocket team to see if they offer any solution to this issue generated by their lazy load.