@epipo I do not notice that error.
In the plugin logic option there is a field to enable the “debug mode”. Could you enable it and check again?
What version of Safari are you running? Any addon?
Nicola
Thanks Nicola,
I’ve enabled the debug mode but I still have the error without any more information than before. I’m running Safari 11.1.1 with no addons.
-
This reply was modified 7 years, 11 months ago by
Etienne.
@epipo same site as before?
What output do you get in the javascript console, with the “navigator.cookieEnabled” command?
Is there any cookie with the name like “CookiePreferences-studiodpe.com”? If yes, what is its value?
– Yes, same site as before (studiodpe.com).
– navigator.cookieEnabled returns false.
– There a no cookies named CookiePrefrences-studiodpe.com.
-
This reply was modified 7 years, 11 months ago by Etienne.
@epipo sorry for the delay.
The problem is that the browser does not accept cookies, as you can see from the result of the “navigator.cookeEnabled” command.
I could improve the script to avoid the raising of that error, but the kit will not work on browsers that do not accept cookies.
No worries, thanks for your answer! Yes that makes sense that it’s not working if cookies are disabled by browser.
I like to keep the console clean when I develop a website so maybe the error could be displayed only when debug mode is activated? What do you think?
I understand you: a warning is ok, but it should be generated by the kit, not by the browser for an unhandled exception! That is exactly what I mean with “I could improve the script to avoid the raising of that error” 🙂
Ok, sounds perfect to me. Thank you for your work!
-
This reply was modified 7 years, 10 months ago by Etienne.
