With the upgrade from layerslider 7.5.3 to 7.6.1 our map made with layerslider stopped working in some areas. My personal machine and a couple of servers no longer can see the layerslider/map. It is fine on many other machines but I don't know how many can't see it. There is also no error displayed. It is also true for all browsers.
The only indication of any problem is witht he old IE11. It says:
LayerSlider: Multiple jQuery issueIt looks like that another plugin or your theme loads an extra copy of the jQuery library causing problems for LayerSlider to show your sliders. Please navigate from your WordPress admin sidebar to LayerSlider -> Options -> Advanced and enable the "Include scripts in the footer" option.
I tried what this said, but that doesn't help. Attached is what it looks like for me. Presumably, it may be visible for you. What things can I try or other data would be helpful for troubleshooting. Or, can I downgrade to 7.5.3 without breaking anything (would need the zip). I did this "kindof" by going to an older snapshot of the server but there could have been a WP upgrade as well then so multiple variables may be in place.
Thank you for getting in touch with us. My name is George and I'm happy to assist you today. I appreciate your patience while we've been working towards your ticket.
I've checked your site with Chrome, Safari and Firefox. For me, the slider is working fine. This issue can be caused by cache/optimizer plugin. If you are using any of these plugins, please make sure to clear/purge cache files. That should solve your issue.
The IE11 error message is from a different issue which will be fixed in the next release of LayerSlider.
That is the case for my colleagues as well. I had just noticed that the older version was able to be downloaded from my purchase portal and I just changed to 7.5.3 and can confirm that the map works OK for me with that version. So, it is something with 7.6 and my systems. I am not running any optimizer plugins on that site. It would also seem, if that was the case, it should be true for everyone.
One thing to note, though I even uninstalled it to test the theory, is that all three of these locations have avast antivirius installed. Also, though, my wife's system has this and hers was fine. It is a strange thing. If it was just my system I would be OK with that, but since I could also replicate it with a few servers, that also is strange. Maybe we wait until the next release comes out and see if that goes OK unless you have some other thoughts.
LayerSlider should work well with Antivirus-protected systems. There was an issue at GoDaddy web hosting company some releases ago: they mistakenly detected a file in LayerSlider as malware in some clients' websites, but this issue was solved almost immediately. Could you please open the web inspector of your browser and see if there are any JavaScript errors on your site?
Sorry for the long delay. Since I had to revert back to a pervious version and this is on our production environment I needed to take some time for snapshots/etc. in order not to mess something up and time has been tight this last week.
I can confirm it was perfectly fine on 7.5.3 but then when I did the plugin update the layerslider the map went away again. It was updated to It is updated right now to the latest of 7.6.7.
I went ahead then and downloaded 7.6.0 and that also is affected. So, it seems there was some major change between 7.5 and 7.6 that is causing this.
There are a number of warnings on the page. The only error I see is this:
It was there still, though, with 7.5.3 so I don’t think it is the cause.
I have tried to disable all of the plugins I thought could be a conflict (other than wordfence security which doesn’t allow me to do) but that hasn’t helped. There are some others that I don’t think would be the case (forms tools that aren’t on the page).
I know it is really hard to diagnose when you can’t recreate the error. The only thing is there must have been a coding/library change between 7.5 and 7.6 and maybe that would give a clue to what might be a conflict. We are using wordpress Network – so multiple sites on one instance.
I can see that the latest version is running on your website. Do you still have the same issue with 7.6.7? Because I cannot reproduce this issue, there are no JavaScript errors on your site, and the slider is working fine for me.
Yes, this is the latest. As I said, it is just a few systems, not all that are experiencing this - my own machine and two server machines. Was there a technology change between 7.5 and 7.6?
Honestly I don't know what can cause this issue. On these machines, the operating system is the same? And the slider fails in all browsers, but only on these machines?
Yes, there are 3 different machines and it is the same (2 are Windows Server ) and my Windows 10 machine. All browsers are affected. From the same network, other computers work. With 7.5.3 everything works. Moving to 7.6.x (without any other plugin changes in WP) the layerslider doesn't show up.
I guess for now we should just close it unless I can figure out some other way to get you data about it. The challenging thing is that I am one of the website managers, though we don't edit the layerslider that often.
Could you, please take a screenshots on one of the affected machines in all browsers with an opened browser console where I could see the possible JavaScript errors? Maybe that could help me to find out what happened.
I probably can't pull off doing all due to time constraints, but could try one. You will see the screenshot at the bottom of the ticket for what it looks like in Firefox. I did notice this in the console relating to layerslider:
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. layerslider.utils.js:13:57660
I have this error from another plugin (my GDPR compliance one):
Below are all of the warnings (in case any of this helps):
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. www.eunc.edu Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. layerslider.utils.js:13:57660 Feature Policy: Skipping unsupported feature name “accelerometer”. www.eunc.edu Feature Policy: Skipping unsupported feature name “autoplay”. www.eunc.edu Feature Policy: Skipping unsupported feature name “clipboard-write”. www.eunc.edu Feature Policy: Skipping unsupported feature name “encrypted-media”. www.eunc.edu Feature Policy: Skipping unsupported feature name “gyroscope”. www.eunc.edu Feature Policy: Skipping unsupported feature name “picture-in-picture”. www.eunc.edu Feature Policy: Skipping unsupported feature name “accelerometer”. www.eunc.edu Feature Policy: Skipping unsupported feature name “autoplay”. www.eunc.edu Feature Policy: Skipping unsupported feature name “clipboard-write”. www.eunc.edu Feature Policy: Skipping unsupported feature name “encrypted-media”. www.eunc.edu Feature Policy: Skipping unsupported feature name “gyroscope”. www.eunc.edu Feature Policy: Skipping unsupported feature name “picture-in-picture”. www.eunc.edu Uncaught SyntaxError: expected expression, got '<' cmplz_run_script https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1 t https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1 cmplz_enable_category https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1 cmplz_set_blocked_content_container https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1 conditionally_show_banner https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1 https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1 www.eunc.edu:1 Feature Policy: Skipping unsupported feature name “accelerometer”. complianz.min.js:1:8673 Feature Policy: Skipping unsupported feature name “autoplay”. complianz.min.js:1:8673 Feature Policy: Skipping unsupported feature name “clipboard-write”. complianz.min.js:1:8673 Feature Policy: Skipping unsupported feature name “encrypted-media”. complianz.min.js:1:8673 Feature Policy: Skipping unsupported feature name “gyroscope”. complianz.min.js:1:8673 Feature Policy: Skipping unsupported feature name “picture-in-picture”. complianz.min.js:1:8673 Feature Policy: Skipping unsupported feature name “accelerometer”. jquery.min.js:2:65891 Feature Policy: Skipping unsupported feature name “autoplay”. jquery.min.js:2:65891 Feature Policy: Skipping unsupported feature name “clipboard-write”. jquery.min.js:2:65891 Feature Policy: Skipping unsupported feature name “encrypted-media”. jquery.min.js:2:65891 Feature Policy: Skipping unsupported feature name “gyroscope”. jquery.min.js:2:65891 Feature Policy: Skipping unsupported feature name “picture-in-picture”. jquery.min.js:2:65891 Cookie “_ga_8DWX0M1P3M” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:158:1015 Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:158:1015 Cookie “_ga_WS138ZVBEH” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:156:1015 Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:156:1015 Cookie “LAST_RESULT_ENTRY_KEY” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite www-embed-player.js:473 Cookie “TESTCOOKIESENABLED” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 4 base.js:7193 Partitioned cookie or storage access was provided to “” because it is loaded in the third-party context and dynamic state partitioning is enabled. Cookie “remote_sid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 base.js:7193 Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:34:486 Cookie “_gid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:34:486 Cookie “_gat” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:34:486 Cookie “LAST_RESULT_ENTRY_KEY” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite base.js:7193
Could you, please temporarily disable the GDPR plugin (and make sure that complianz.min.js is not loading on your site) and try it again? Because the first message about layerslider.utils.js is only a warning and that should not cause an issue like this.
Could you, please create a temporary wp-admin access for me? If you don't mind, I would like to check the plugins and settings in the wp-admin interface to see if I can find what could be causing this error.
I was able to log in and I've opened Firefox with your website. The slider is now working for me. Did you change anything? How can I reproduce the issue?
That is so very strange! I logged in as well with the same username/password and still don't see it. There must be something blocking it in my personal machine and somehow that is also passing on to the RDP connection - though that is also very strange.
I am more convinced this is unique to me. Feel free to close this ticket and not worry about it. If I figure it out, I'll go back in and update it (or if you want to keep it open that is also fine. I'm traveling starting today for the next 2 weeks so probably won't look at it much, if all, during those days.
Now I understand what caused the issue. In the previous release of LayerSlider there was a bug: the slider thought that it was running on a mobile device if the device had a touch screen (even on a normal laptop). And I bet that your slider has the "Hide on mobile devices" feature enabled. ;-)
Yes, that is the case because in that case we display a different menu. But, the content management software we are using is looking for device size and since it wasn't the right size it didn't display that other menu (which would have also been confusing, though. It is interesting that the RDP sessions carried that information over to them.
With the upgrade from layerslider 7.5.3 to 7.6.1 our map made with layerslider stopped working in some areas. My personal machine and a couple of servers no longer can see the layerslider/map. It is fine on many other machines but I don't know how many can't see it. There is also no error displayed. It is also true for all browsers.
The only indication of any problem is witht he old IE11. It says:
LayerSlider: Multiple jQuery issueIt looks like that another plugin or your theme loads an extra copy of the jQuery library causing problems for LayerSlider to show your sliders. Please navigate from your WordPress admin sidebar to LayerSlider -> Options -> Advanced and enable the "Include scripts in the footer" option.
I tried what this said, but that doesn't help. Attached is what it looks like for me. Presumably, it may be visible for you. What things can I try or other data would be helpful for troubleshooting. Or, can I downgrade to 7.5.3 without breaking anything (would need the zip). I did this "kindof" by going to an older snapshot of the server but there could have been a WP upgrade as well then so multiple variables may be in place.
Please Advise.
Alan
Attached files: layerslidernotvisible.JPG
Hello Alan,
Thank you for getting in touch with us. My name is George and I'm happy to assist you today. I appreciate your patience while we've been working towards your ticket.
I've checked your site with Chrome, Safari and Firefox. For me, the slider is working fine. This issue can be caused by cache/optimizer plugin. If you are using any of these plugins, please make sure to clear/purge cache files. That should solve your issue.
The IE11 error message is from a different issue which will be fixed in the next release of LayerSlider.
Best Regards,
George | Kreatura Dev Team
Hi George,
That is the case for my colleagues as well. I had just noticed that the older version was able to be downloaded from my purchase portal and I just changed to 7.5.3 and can confirm that the map works OK for me with that version. So, it is something with 7.6 and my systems. I am not running any optimizer plugins on that site. It would also seem, if that was the case, it should be true for everyone.
One thing to note, though I even uninstalled it to test the theory, is that all three of these locations have avast antivirius installed. Also, though, my wife's system has this and hers was fine. It is a strange thing. If it was just my system I would be OK with that, but since I could also replicate it with a few servers, that also is strange. Maybe we wait until the next release comes out and see if that goes OK unless you have some other thoughts.
Alan
Hello Alan,
Thank you for your fast reply.
LayerSlider should work well with Antivirus-protected systems. There was an issue at GoDaddy web hosting company some releases ago: they mistakenly detected a file in LayerSlider as malware in some clients' websites, but this issue was solved almost immediately. Could you please open the web inspector of your browser and see if there are any JavaScript errors on your site?
Best Regards,
George | Kreatura Dev Team
Hi George,
Sorry for the long delay. Since I had to revert back to a pervious version and this is on our production environment I needed to take some time for snapshots/etc. in order not to mess something up and time has been tight this last week.
I can confirm it was perfectly fine on 7.5.3 but then when I did the plugin update the layerslider the map went away again. It was updated to It is updated right now to the latest of 7.6.7.
I went ahead then and downloaded 7.6.0 and that also is affected. So, it seems there was some major change between 7.5 and 7.6 that is causing this.
There are a number of warnings on the page. The only error I see is this:
Uncaught SyntaxError: expected expression, got '<'
It was there still, though, with 7.5.3 so I don’t think it is the cause.
I have tried to disable all of the plugins I thought could be a conflict (other than wordfence security which doesn’t allow me to do) but that hasn’t helped. There are some others that I don’t think would be the case (forms tools that aren’t on the page).
I know it is really hard to diagnose when you can’t recreate the error. The only thing is there must have been a coding/library change between 7.5 and 7.6 and maybe that would give a clue to what might be a conflict. We are using wordpress Network – so multiple sites on one instance.
Thoughts?
Alan
Hello John,
I can see that the latest version is running on your website. Do you still have the same issue with 7.6.7? Because I cannot reproduce this issue, there are no JavaScript errors on your site, and the slider is working fine for me.
Best Regards,
George | Kreatura Dev Team
Yes, this is the latest. As I said, it is just a few systems, not all that are experiencing this - my own machine and two server machines. Was there a technology change between 7.5 and 7.6?
We are constantly adding new features, fixing bugs and trying to optimize the plugin: https://layerslider.com/release-log/
Honestly I don't know what can cause this issue. On these machines, the operating system is the same? And the slider fails in all browsers, but only on these machines?
Best Regards,
George | Kreatura Dev Team
Yes, there are 3 different machines and it is the same (2 are Windows Server ) and my Windows 10 machine. All browsers are affected. From the same network, other computers work. With 7.5.3 everything works. Moving to 7.6.x (without any other plugin changes in WP) the layerslider doesn't show up.
I guess for now we should just close it unless I can figure out some other way to get you data about it. The challenging thing is that I am one of the website managers, though we don't edit the layerslider that often.
Could you, please take a screenshots on one of the affected machines in all browsers with an opened browser console where I could see the possible JavaScript errors? Maybe that could help me to find out what happened.
Best Regards,
George | Kreatura Dev Team
I probably can't pull off doing all due to time constraints, but could try one. You will see the screenshot at the bottom of the ticket for what it looks like in Firefox. I did notice this in the console relating to layerslider:
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. layerslider.utils.js:13:57660
I have this error from another plugin (my GDPR compliance one):
Uncaught SyntaxError: expected expression, got '<' cmplz_run_script https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
t https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
cmplz_enable_category https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
cmplz_set_blocked_content_container https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
conditionally_show_banner https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
<anonymous> ht
Below are all of the warnings (in case any of this helps):
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. www.eunc.edu
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. layerslider.utils.js:13:57660
Feature Policy: Skipping unsupported feature name “accelerometer”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “autoplay”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “clipboard-write”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “encrypted-media”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “gyroscope”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “picture-in-picture”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “accelerometer”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “autoplay”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “clipboard-write”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “encrypted-media”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “gyroscope”. www.eunc.edu
Feature Policy: Skipping unsupported feature name “picture-in-picture”. www.eunc.edu
Uncaught SyntaxError: expected expression, got '<'
cmplz_run_script https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
t https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
cmplz_enable_category https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
cmplz_set_blocked_content_container https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
conditionally_show_banner https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
https://www.eunc.edu/wp-content/plugins/complianz-gdpr/cookiebanner/js/complianz.min.js?ver=6.3.9:1
www.eunc.edu:1
Feature Policy: Skipping unsupported feature name “accelerometer”. complianz.min.js:1:8673
Feature Policy: Skipping unsupported feature name “autoplay”. complianz.min.js:1:8673
Feature Policy: Skipping unsupported feature name “clipboard-write”. complianz.min.js:1:8673
Feature Policy: Skipping unsupported feature name “encrypted-media”. complianz.min.js:1:8673
Feature Policy: Skipping unsupported feature name “gyroscope”. complianz.min.js:1:8673
Feature Policy: Skipping unsupported feature name “picture-in-picture”. complianz.min.js:1:8673
Feature Policy: Skipping unsupported feature name “accelerometer”. jquery.min.js:2:65891
Feature Policy: Skipping unsupported feature name “autoplay”. jquery.min.js:2:65891
Feature Policy: Skipping unsupported feature name “clipboard-write”. jquery.min.js:2:65891
Feature Policy: Skipping unsupported feature name “encrypted-media”. jquery.min.js:2:65891
Feature Policy: Skipping unsupported feature name “gyroscope”. jquery.min.js:2:65891
Feature Policy: Skipping unsupported feature name “picture-in-picture”. jquery.min.js:2:65891
Cookie “_ga_8DWX0M1P3M” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:158:1015
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:158:1015
Cookie “_ga_WS138ZVBEH” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:156:1015
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:156:1015
Cookie “LAST_RESULT_ENTRY_KEY” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite www-embed-player.js:473
Cookie “TESTCOOKIESENABLED” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 4 base.js:7193
Partitioned cookie or storage access was provided to “” because it is loaded in the third-party context and dynamic state partitioning is enabled.
Cookie “remote_sid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 base.js:7193
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:34:486
Cookie “_gid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:34:486
Cookie “_gat” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:34:486
Cookie “LAST_RESULT_ENTRY_KEY” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite base.js:7193
Could you, please temporarily disable the GDPR plugin (and make sure that complianz.min.js is not loading on your site) and try it again? Because the first message about layerslider.utils.js is only a warning and that should not cause an issue like this.
Best Regards,
George | Kreatura Dev Team
I had already done that along with most other plugins to no avail...
I did double check, though, and it didn't matter.
Could you, please create a temporary wp-admin access for me? If you don't mind, I would like to check the plugins and settings in the wp-admin interface to see if I can find what could be causing this error.
Best Regards,
George | Kreatura Dev Team
Hello John,
I was able to log in and I've opened Firefox with your website. The slider is now working for me. Did you change anything? How can I reproduce the issue?
Attached files: Screenshot 2023-01-23 at 13.38.45.png
Best Regards,
George | Kreatura Dev Team
That is so very strange! I logged in as well with the same username/password and still don't see it. There must be something blocking it in my personal machine and somehow that is also passing on to the RDP connection - though that is also very strange.
I am more convinced this is unique to me. Feel free to close this ticket and not worry about it. If I figure it out, I'll go back in and update it (or if you want to keep it open that is also fine. I'm traveling starting today for the next 2 weeks so probably won't look at it much, if all, during those days.
Thanks for looking as you can at this!
Alan
Did you try it even with logged out of wp-admin (as a normal visitor) ?
Best Regards,
George | Kreatura Dev Team
Yes, I wasn't even logged in, I just went straight to the page as it looks like you did...
This is really strange, I am so sorry about this.
Best Regards,
George | Kreatura Dev Team
Good news. I just applied the latest layerslider update, and it works now! Don't know why, just be thankful it is!
Thanks
Alan
Hmmm... are you using a laptop/display with touch screen?
Best Regards,
George | Kreatura Dev Team
yes, my laptop has a touch screen.
Now I understand what caused the issue. In the previous release of LayerSlider there was a bug: the slider thought that it was running on a mobile device if the device had a touch screen (even on a normal laptop). And I bet that your slider has the "Hide on mobile devices" feature enabled. ;-)
Best Regards,
George | Kreatura Dev Team
Yes, that is the case because in that case we display a different menu. But, the content management software we are using is looking for device size and since it wasn't the right size it didn't display that other menu (which would have also been confusing, though. It is interesting that the RDP sessions carried that information over to them.
layerslider not open.
Attached files: not working.jpg
Hello,
This is someone else's ticket. Please open a new separate ticket for this case.
Best Regards,
George | Kreatura Dev Team