Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Tijmen Smit

    (@tijmensmit)

    This is the JS error that comes up.

    Timestamp: 14/04/2016 21:27:32
    Error: Error: Syntax error, unrecognized expression: .site-header a[href*=#]:not([href=#])
    Source File: https://greenjujukitchen.com/wp-includes/js/jquery/jquery.js
    Line: 2

    It’s related to WP updating the jQuery library to 1.12, and a JS file from your theme ( if you disabled all plugins and it still breaks, then it has to come from the theme ) using this a[href*=#]:not([href=#] code, while it should be a[href*=’#’]:not([href=’#’] ( there are ” around the # ).

    The code without the ” around the # worked with older jQuery versions, but not anymore with the one that ships with WP 4.5 ( This is not a bug in WP, it should have been ‘#’ from the beginning, but it always worked without it ).

    If you for a second switch back the default WP theme, then it will very likely start to work again. If this happens you will either have to contact the theme author, and ask him to fix it, or if you’re comfortable with code, then you can just search through the theme files for a[href*=#]:not([href=#], and change it to a[href*=’#’]:not([href=’#’] yourself.

    You can read more about it here and here ( assuming you have FB ).

    Thread Starter samanthaenglander

    (@samanthaenglander)

    Thanks so much for your response! I’m moderately comfortable with code, so would like to try and address this myself. However, when I look at that source file, I’m not actually seeing that expression in it, are you? Do you mind letting me know if I’m missing something here? I would expect to find it near the beginning if it’s Line 2…? Sorry if I sound super novice right now.

    Plugin Author Tijmen Smit

    (@tijmensmit)

    The jQuery file shows the error, but the code that makes jQuery show the error in the first place comes from another file.

    The only way you can find this file is by searching through the files in your theme folder for a[href*=#]:not([href=#], or a part of it like href=#.

    Thread Starter samanthaenglander

    (@samanthaenglander)

    Thanks so much! I found two files in my theme’s folders with that expression and updated them to have the ” around the #s. It’s still not working, however. I was wondering if you could have another look and see if it’s still presenting the same error? I’ve also put in a ticket with my theme’s developer to see if they can pinpoint which files I need to change/update.

    Thanks so much for your excellent and timely help.

    Plugin Author Tijmen Smit

    (@tijmensmit)

    The error is the same.

    Is there a file in the folder where you found the file to edit that has .min in the file name? So if you for example editing js-scripts.js, is there a js-scripts.min.js? If so, then it’s likely the .min file is loaded.

    The error is the still the same. You can check it yourself in the browser as well.

    If there’s a .min version, then what you can do is first make a backup of the .min, then open the code one you edited, copy the content and minify the code on a site l ike this. Then copy the minified code, and paste in in the .min file.

    Samantha, I’m guessing you’re using Avada theme — I just went through this exact process myself the last couple of days, with the same error message. Avada has a fix specifically for this issue here:

    https://theme-fusion.com/knowledgebase/avada-3-9-3-fix-wordpress-4-5-compatibility/

    Just download that ZIP and overwrite the JS files it contains in your theme’s folder, and things should start working. Alternatively you could upgrade Avada to its latest version, but I understand that may not be possible if you’ve made previous modifications.

    Thread Starter samanthaenglander

    (@samanthaenglander)

    Hi grex22! I really appreciate your taking the time to help out! Unfortunately, I’m using the Rosa theme. Seems multiple developers caused the same issue ?? But I was in touch with that developer and they said I can expect a patch within a week. So fingers crossed! Thanks again for reaching out to help!

    Darn! I was taking a shot in the dark, but either way it sounds like you’ll be taken care of soon with a patch in the next week. Best of luck!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Neither stores nor map showing’ is closed to new replies.