Okay
  Public Ticket #1314913
layerslider critical error
Closed

Comments

  • Esteve started the conversation

    Hi,

    The Layerslider plugin is loaded and displayed as usual when it is first laoded on the home page (http://www.comscience.fr/). Then if you go to web another page with the same slider (i.e. : the related URL above : http://www.comscience.fr/page-de-test/) or come back to the home page after visiting any other pages: the Layerslider plugin is no longer displayed.

    I tried with an empty page or disabling some plugins (i.e. super cache) but got the same result. This issue seems to appear only with this premium slider. It is probably due to a special 3D effect.

    Find enclosed a screenshot of this problem.

    Thank you for your quick answer.

    Best regards,

    Gaël

  • [deleted] replied

    Hello Gaël,

    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.

    The problem is that your site uses Ajax to load new content. When you click on a menu element, the page's actual content gets deleted from the DOM, including the source code generated by the slider. And when you navigate back to the same page, the functions earlier used by slider are still there, stored in the memory, and they are pointing to the original elements, and not to the new elements loaded by the Ajax method.

    What you should do to work around this is, when you navigate away from a page that contains LayerSlider, you save the LayerSlider's original source code, then destroy LayerSlider. After that when you navigate back to the page that contained LayerSlider, you load the saved source code to the DOM, and finally you initialize the slider.

  • Esteve replied

    Hello Attila,

    Thank you for yoiur answer. 

    In other words and because I would be sure to well understand what you wrote - I have two options. 

    1/ Disable ajax transition or 2/ copy raw html code (build by layerslider) directly into the page

    Best,

    Gaël

  • [deleted] replied

    The easier and more simple approach would be to disable the Ajax loading - if you are able to do it - to bypass this error/conflict.

    The other solution would require heavier coding knowledge unfortunately.

  • Esteve replied

    Hi, Ok, thanks.

    Gaël