Lay Theme v3.3.7 - Borlabs Cookie Box doesn't disappear anymore
-
Hey Andreas,
thats right. Neither Version 3.3.7 was working with Borlabs nor 3.3.8. Its a bit difficult.. -
This post is deleted!
-
-
hey when reporting a bug please always post a link to your website
looking into this now -
Sure, but not with a bug that causes the entire site to stop working. is it possible to reproduce this issue with your own setup?
btw thanks to timg, he already asked borlab, here's the answer out his thread
"Die Ursache ist verkorkstes JavaScript vom Theme. In anderen Themes gibt es eine Option die AJAX Transition zu deaktivieren, das geht hier wohl leider nicht. Beim Klick auf einen Link wertet das JavaScript vom Theme unseren Link nicht korrekt aus und wirft einen Fehler. Wir kรถnnen hier nichts machen, die Entwickler des Themes sind verantwortlich, bitte wende dich mit einem Error Report an sie, damit sie ihr JavaScript korrigieren und das href-Attribut richtig auswerten."
Also they send me the error report, which they are getting: https://pastebin.com/GtgGsjAc -
This is also happening when using the Borlabs content blocker. Clicking on the content blocker to allow the content triggers the same error. Are there any pointers on how to make this compatible? It seems like the laytheme JS is catching the click event in a way that creates a conflict here.
I am trying to implement content blocking with laytheme and borlabs and this is a dead end at the moment. I have created a seperate post on this issue. ANy pointers are much appreciated.MM
-
Dear @michaelmaeder
I have recently replied on this Thread:
http://laythemeforum.com:4567/topic/6887/bug-with-borlab-shortcodes/3Best wishes ๐
Richard
Before you post:
- When using a WordPress Cache plugin, disable it or clear your cache.
- Update Lay Theme and all Lay Theme Addons
- Disable all Plugins
- Go to Lay Options โ Custom CSS & HTML, click "Turn Off All Custom Code", click "Save Changes"
This often solves issues you might run into
When you post:
- Post a link to where the problem is
- Does the problem happen on Chrome, Firefox, Safari or iPhone or Android?
- If the problem is difficult to explain, post screenshots / link to a video to explain it