jquery error after WP 4.5 update

Hi,

I am not seeing that error in my firebug error console.
Please clear your browser history

I switched back to main Evolve theme and it went away. Tried some other themes though (not child themes) and it reappeared.

I couldn’t use the Evolve custom css in the customizer (wouldn’t save) until I turned off the latest JetPack.

I guess everyone updated plugins after WP 4.5 so there’s bound to be a few that need some kinks worked out.

Thank you, Dennis, for the quick response. This is my first WP site and somehow I thought it would be easier.

You are welcome.

It easier to use a HTML website, than using WordPress.
Other than software issues on a WordPress site, you may also encounter server setup or server resources issues.

keep you list of plugins small and it should be easier to manage.

Thank you

WordPress uses the jQuery migrate script to ensure backwards compatibility for any plugins or themes you might be using which use functionality removed from newer versions of jQuery.

With the release of WordPress 4.5, it appears they have upgraded the version of jQuery migrate from v1.2.1 to v1.4.0 – Having a quick scan through the code reveals that v1.4.0 logs that the script is loaded regardless of whether or not the migrateMute option is set and in both the uncompressed and minified versions.

The only way to remove the notice is to ensure all your plugins/theme code don’t rely on any old jQuery functionality, and then remove the migrate script. There’s a plugin out there to do this, but it’s quite a simple method that can just be placed in your theme’s functions file or similar:

add_action( 'wp_default_scripts', function( $scripts ) {
    if ( ! empty( $scripts->registered['jquery'] ) ) {
        $jquery_dependencies = $scripts->registered['jquery']->deps;
        $scripts->registered['jquery']->deps = array_diff( $jquery_dependencies, array( 'jquery-migrate' ) );
    }
} );

Please note that this is not considered best practice for WordPress development and in my opinion the migrate script should not be removed just for the sake of keeping the developer console clean.

source