Support

September 2, 2020 at 2:42 pm

Hi there,

This is happening becuase of the version of jQuery you have active on the site

Looking at the page source I can see you are using the jQUery Updater plugin to switch to a different version of jQuery than what ships with WordPress (3.5.1 to be exact). You’ll need to disable that plugin for the calendar to function as expected.

September 9, 2020 at 1:51 am

When you say they don’t work, in what way? What happens?

Loading the latest version of jQuery in place of the version shipped with WordPress is the ‘wrong’ way to fix this, for details on why see:

https://pippinsplugins.com/why-loading-your-own-jquery-is-irresponsible/

I can see you’re using visual composer, try adding the calendar shortcode to the default editor, does it work then?

September 10, 2020 at 4:11 am

The calendar uses JavaScript to display on the page, any JavaScript error being thrown on the page will cause the calendar to fail as once there is a JS error no other JS can run after it.

I can see that the espresso-calendar placeholder divs are loading on the page and the scripts are added, meaning the shortcode is parsing as expected but the JS is failing.

If you open the above page and then open Chrome Dev Tools (or similar) and look in the console you’ll see this JavaScript error:

jquery.js?ver=1.12.4-wp:2 Uncaught Error: Syntax error, unrecognized expression: .mobile_menu > ul > li.has_sub > span.mobile_arrow, .mobile_menu > ul > li.has_sub > h3, .mobile_menu > ul > li.has_sub > a[href*=#]
    at Function.ea.error (jquery.js?ver=1.12.4-wp:2)
    at ea.tokenize (jquery.js?ver=1.12.4-wp:2)
    at ea.select (jquery.js?ver=1.12.4-wp:2)
    at Function.ea [as find] (jquery.js?ver=1.12.4-wp:2)
    at n.fn.init.find (jquery.js?ver=1.12.4-wp:2)
    at new n.fn.init (jquery.js?ver=1.12.4-wp:2)
    at n (jquery.js?ver=1.12.4-wp:2)
    at initMobileMenu (default.min.js?ver=5.5.1:1)
    at HTMLDocument.<anonymous> (default.min.js?ver=5.5.1:1)
    at i (jquery.js?ver=1.12.4-wp:2)

Working through the stack trace it shows the error is from the initMobileMenu function in the default.min.js which lives in:

/wp-content/themes/hazel/js/default.min.js

The part of the error that sticks out to me is this a[href*=#], it should be a[href*="#"]

A quick Google search for the exact error you’re getting on the site leads to here:

https://stackoverflow.com/questions/63404124/new-version-of-jquery-is-saying-i-have-a-syntax-error-when-there-is-none

Which highlights exactly the same problem and it’s something your theme author needs to fix, you can manually edit the above to fix it, but if the theme author hasn’t fixed it the next time you update the the theme the same will happen.

September 10, 2020 at 7:24 am

You’re most welcome, I’m glad it’s working.