I have problems regarding the mobile navigation. When you open the website on a mobile device and the "burger"- menu appears, you cannnot open the navigation. In the console the following error appears:
Uncaught Error: Syntax error, unrecognized expression: .image-box, .vc_gitem-zone a.not(.clone .image-box):not('.fancybox-item, .fancybox-nav') at Function.bc.error (jquery.min.js:2) at bh (jquery.min.js:2) at bp (jquery.min.js:2) at bp (jquery.min.js:2) at Function.bc [as find] (jquery.min.js:2) at HTMLDocument.dispatch (jquery.min.js:2) at HTMLDocument.h (jquery.min.js:2)
I don´t installed the new version of the SCHON Template for my client.
As I have checked the source code of the site, I found that the jQuery script has beed loaded twice. The script should always be loaded from WordPress itself by default. Here is a screenshot of the other one I found: https://cl.ly/87b698179bbf.
I believe this is the cause of the problem. Please remove the custom script as marked in the screenshot above, clear all the cache, and test it again. It should help.
Dear support team,
I have problems regarding the mobile navigation. When you open the website on a mobile device and the "burger"- menu appears, you cannnot open the navigation. In the console the following error appears:
Uncaught Error: Syntax error, unrecognized expression: .image-box, .vc_gitem-zone a.not(.clone .image-box):not('.fancybox-item, .fancybox-nav')
at Function.bc.error (jquery.min.js:2)
at bh (jquery.min.js:2)
at bp (jquery.min.js:2)
at bp (jquery.min.js:2)
at Function.bc [as find] (jquery.min.js:2)
at HTMLDocument.dispatch (jquery.min.js:2)
at HTMLDocument.h (jquery.min.js:2)
I don´t installed the new version of the SCHON Template for my client.
Thank you for you help.
Greetings Christina
Hello Christina,
As I have checked the source code of the site, I found that the jQuery script has beed loaded twice. The script should always be loaded from WordPress itself by default. Here is a screenshot of the other one I found: https://cl.ly/87b698179bbf.
I believe this is the cause of the problem. Please remove the custom script as marked in the screenshot above, clear all the cache, and test it again. It should help.
Regards,
Paul