Uncaught Error: Syntax error, unrecognized expression: unsupported pseudo: regex - Support

Hey CommunityHousing,

Please enable SCRIPT_DEBUG.
– https://wordpress.org/support/article/debugging-in-wordpress/#script_debug

Best regards,
Nikko

February 3, 2020 at 4:25 am #1180785

Done:

jquery-migrate.js?x66868:47 
console.trace
migrateWarn @ jquery-migrate.js?x66868:47
get @ jquery-migrate.js?x66868:62
AviaBrowserDetection @ avia.js?x66868:74
(anonymous) @ avia.js?x66868:3
i @ jquery.js?x66868:1
fireWith @ jquery.js?x66868:1
ready @ jquery.js?x66868:1
J @ jquery.js?x66868:1

jquery.js?x66868:1 
Uncaught Error: Syntax error, unrecognized expression: unsupported pseudo: regex
    at Function.ea.error (jquery.js?x66868:1)
    at PSEUDO (jquery.js?x66868:1)
    at va (jquery.js?x66868:1)
    at ea.compile (jquery.js?x66868:1)
    at ea.select (jquery.js?x66868:1)
    at Function.ea (jquery.js?x66868:1)
    at Function.jQuery.find (jquery-migrate.js?x66868:290)
    at jQuery.fn.init.find (jquery.js?x66868:1)
    at jQuery.fn.init.jQuery.fn.find (jquery-migrate.js?x66868:677)
    at jQuery.fn.init.n.fn.init (jquery.js?x66868:1)
ea.error @ jquery.js?x66868:1
PSEUDO @ jquery.js?x66868:1
va @ jquery.js?x66868:1
ea.compile @ jquery.js?x66868:1
ea.select @ jquery.js?x66868:1
ea @ jquery.js?x66868:1
jQuery.find @ jquery-migrate.js?x66868:290
find @ jquery.js?x66868:1
jQuery.fn.find @ jquery-migrate.js?x66868:677
n.fn.init @ jquery.js?x66868:1
jQuery.fn.init @ jquery-migrate.js?x66868:241
n @ jquery.js?x66868:1
(anonymous) @ avia.js?x66868:194
each @ jquery.js?x66868:1
each @ jquery.js?x66868:1
$.fn.avia_activate_lightbox @ avia.js?x66868:193
$.avia_utilities.avia_ajax_call @ avia.js?x66868:10
(anonymous) @ avia.js?x66868:9
i @ jquery.js?x66868:1
fireWith @ jquery.js?x66868:1
ready @ jquery.js?x66868:1
J @ jquery.js?x66868:1

shortcodes.js?x66868:11
Uncaught TypeError: $.AviaTooltip is not a constructor
    at HTMLDocument.<anonymous> (shortcodes.js?x66868:11)
    at i (../jquery.js:1)
    at Object.fireWith [as resolveWith] (../jquery.js:1)
    at Function.ready (../jquery.js:1)
    at HTMLDocument.J (../jquery.js:1)

February 3, 2020 at 10:10 am #1180804

Hi CommunityHousing,

I apologize for not noticing beforehand but the version of Enfold you’re using is already outdated.
Please consider updating your site to the latest version of Enfold.
Please create a backup first and try to create a staging site (basically a clone of your site, placed on a subdomain) and do the updates there first so you won’t risk your live site, if all is good you can proceed on updating your live site.
Here’s an article that you can follow for creating a staging site: https://themeisle.com/blog/wordpress-staging-site/

Best regards,
Nikko

February 4, 2020 at 1:07 am #1181115

I was hoping to avoid that.
It’s a big job I was hoping to avoid.

February 4, 2020 at 4:19 am #1181131

Hi CommunityHousing,

I think it will be a bigger issue in the future since Enfold isn’t updated but the version of your WordPress is the latest version.
Enfold 4.0.7 was made when WordPress was still version 4.x but WordPress has already upgraded to version 5 which is a major version.
I tried to suppress the issue but it shows another error after fixing one, you can try the following:
– To suppress this issue:

Uncaught Error: Syntax error, unrecognized expression: unsupported pseudo: regex

go to wp-content > themes > enfold > js > avia.js remove this codes (line 999 and 1000):

a:regex(href, .vimeo\.com/[0-9]) ,

– To suppress this issue:

Uncaught TypeError: $.AviaTooltip is not a constructor

go to wp-content > themes > enfold > js > shortcodes.js find these codes (line 36-39):

new $.AviaTooltip({'class': "avia-tooltip", data: "avia-tooltip", delay:0, scope: "body"});
		
//creates icon element tooltip
new $.AviaTooltip({'class': "avia-tooltip avia-icon-tooltip", data: "avia-icon-tooltip", delay:0, scope: "body"});

replace with:

new $.AviaTooltip();
		
//creates icon element tooltip
new $.AviaTooltip();

Best regards,
Nikko

February 7, 2020 at 1:01 am #1182201

Thank you, I think we’re going to bite the bullet and upgrade.
Can I straight upgrade from 4.0.7 to 4.7.2 or is there a recommended safe upgrade path?

February 7, 2020 at 1:35 am #1182210

Upgrade went smoothly.
Just did a manual update and no isses.
thanks

February 7, 2020 at 3:37 am #1182220