jquery-migrate.min.js?ver=1.4.1:2 JQMIGRATE: Migrate is installed, version 1.4.1 VM151:1 LayerSlider initialized | core: 6.9.2-stable | WP Plugin: 6.9.2 VM151:1 Find updates and docs @ https://layerslider.kreaturamedia.com/ 9VM151:1 Uncaught TypeError: Cannot read property 'originalLayer' of undefined at a (eval at <anonymous> (layerslider.kreaturamedia.jquery.js?ver=6.9.2:13), <anonymous>:1:101860) at Object.handleEvent (<anonymous>:1:3001) (index):1 Unchecked runtime.lastError: The message port closed before a response was received.
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.
I have checked your site, but for me there is no such error under Chrome currently. And there is definitely no error like this on our demo site.
Do you still see it ? If yes, then the problem is likely localized on your end. Could be related to the browser or to an addon for example.
Please try to use a different device/desktop to test it, and please also specify on what OS/device are you experiencing this exactly.
At https://layerslider.kreaturamedia.com/ and at our site visiting under CHROME we get this error:
jquery-migrate.min.js?ver=1.4.1:2 JQMIGRATE: Migrate is installed, version 1.4.1
VM151:1 LayerSlider initialized | core: 6.9.2-stable | WP Plugin: 6.9.2
VM151:1 Find updates and docs @ https://layerslider.kreaturamedia.com/
9VM151:1 Uncaught TypeError: Cannot read property 'originalLayer' of undefined
at a (eval at <anonymous> (layerslider.kreaturamedia.jquery.js?ver=6.9.2:13), <anonymous>:1:101860)
at Object.handleEvent (<anonymous>:1:3001)
(index):1 Unchecked runtime.lastError: The message port closed before a response was received.
under chrome
Versie 77.0.3865.90 (Officiële build) (64-bits)
Hello Manga,
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.
I have checked your site, but for me there is no such error under Chrome currently. And there is definitely no error like this on our demo site.
Do you still see it ? If yes, then the problem is likely localized on your end. Could be related to the browser or to an addon for example.
Please try to use a different device/desktop to test it, and please also specify on what OS/device are you experiencing this exactly.