WP 4.5 makes your plugin not working

What’s the url? Are you using any caching plugins? If so, make sure to flush the cache. The plugins works fine for me on a clean 4.5 install.

https://www.inspirehealthclubs.com

I am sorry but how do you “flush the cache?” You mean clear cache on browser?

WP Super Cache is off. I cleaned browser cache and history. Still nothing.

Caching plugins usually have an option to flush the cache they created.

There is a jQuery error, but it doesn’t say much where it comes from.

Timestamp: 13/04/2016 13:14:59
Error: Error: Syntax error, unrecognized expression: [href=#]
Source File: https://inspire.edcreative.us/wp-includes/js/jquery/jquery.js?ver=1.12.3
Line: 2

Can you for a second disable all other plugins and switch back to a default WP to see if it still breaks? If not, can you enable the other plugins one by one and see which plugin causes it to break.

Okay can you try test jquery on your end again and see if it will tell you exactly whats wrong?

I have tested WP 4.5 on two domains with the latest WPSL version, but I don’t get any errors.

The error can can come from other plugins as well. Once a JS error happens, it will break all the others scripts that follow, thats why you should try to disable other plugins, and switch back to a default theme for a second to make sure it comes from the store locator plugin.

The timing for this is kind of bad though. I will be traveling to Spain soon, so I don’t have a lot of time to look into this the next 24hrs.

Okay I took care of it.

The theme I used is Avada. They provided an emergency fix for WordPress 4.5 compatibility and it looks like it is working. It appears to be a javascript error, due to WordPress updating jQuery libraries. This cause site elements to stop working.

Yeah it looks like any theme and plugin you use with WordPress need to update their compatibility, especially javascripts.

Thanks

Can confirm that Avada theme previous to version 3.8.3 and earlier will cause this issue. It has nothing to do with WP Store Locator, but this was also how I came across this issue.