How to replace regular jquery calls with CDN calls from Google?

I will like to implement a few of the boilerplate template features in one of my instance WordPress.

I am trying to figure out how to exchange the regular jquery calls below

Read More
<script type='text/javascript' src='http:/.../wp-includes/js/jquery/jquery.js?ver=1.4.4'></script>
<script type='text/javascript' src='http://.../wp-includes/js/jquery/ui.core.js?ver=1.8.9'></script>

to this:

<!-- Grab Google CDN's jQuery, with a protocol relative URL; fall back to local if necessary -->
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.5.1/jquery.js"></script>
<script>window.jQuery || document.write("<script src='js/libs/jquery-1.5.1.min.js'>x3C/script>")</script>

Related posts

Leave a Reply

3 comments

  1. You should be loading jQuery with wp_enqueue_script('jquery') – that way, you won’t end up with multiple instances if plugins try to load it too.

    To use Google CDN, place this in your functions.php;

    wp_deregister_script( 'jquery' );
    wp_register_script(
        'jquery',
        'https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js', 
        null, // Dependencies - none
        null  // Version - use null to prevent WP adding version argument "?ver" in URL
    );
    

    Update: Personally, and I know this sounds like a cop-out, but I wouldn’t bother checking the CDN. Google is just so damn reliable, and it’s more than likely it’s already in the user’s browser cache anyway (so many sites use Google’s CDN).

    However, in my duty to answer, you have one of two options;

    1. Check server side with a remote get, and if it fails, serve the local copy (expensive and not recommended)
    2. Run a script client-side that checks for jQuery, and prints the fallback if necessary

    The trouble with 2) is that you need to inject this script right after jQuery, and before any other plugins that depend on it fire their scripts. The only way I know you can do this is to ‘listen’ for jQuery, then output the JavaScript on the next call.

    The magic? Drop this in your functions.php;

    /**
     * Print fallback script right after jQuery is printed from queue.
     *
     * @param   string $src
     * @return  string
     */
    function wpse_12448_fallback_jquery( $src, $handle = null ) {
        static $run_next = false;
    
        if ( $run_next ) {
            // Defaults to WP bundled jQuery, but you should use your own that
            // matches the version loaded via CDN.
            $local = includes_url( 'js/jquery/jquery.js' );
    
            echo <<<JS
    <script>window.jQuery || document.write( '<script src="$local"></script>' );</script>
    
    JS;
            $run_next = false;
        }
    
        if ( $handle === 'jquery' )
            $run_next = true;
    
        return $src;
    }
    
    add_action( 'wp_head', 'wpse_12448_fallback_jquery', 2 );
    if ( ! is_admin() )
        add_filter( 'script_loader_src', 'wpse_12448_fallback_jquery', 10, 2 );
    

    For those in the know, this is also hooked to wp_head right after wp_print_scripts would have fired, in case there were no more scripts to print after jquery (the function does it’s work on the next call, rather than the instance it is called with jQuery).

  2. For WordPress 4.5.0 + : wp_add_inline_script() #

    function jquery_enqueue_with_fallback() {
        wp_deregister_script( 'jquery' );
        wp_register_script( 'jquery' , '//ajax.googleapis.com/ajax/libs/jquery/3.1.1/jquery.min.js', false, '3.1.1', true );
        wp_add_inline_script( 'jquery', 'window.jQuery||document.write('<script src="'.esc_url(get_template_directory_uri()).'/libs/js/jquery.js"></script>')' );
        wp_enqueue_script( 'jquery' );
    }
    add_action( 'wp_enqueue_scripts' , 'jquery_enqueue_with_fallback' );
    

    Note : Change the version and your own local jQuery source.

  3. Two things to keep in mind about this answer:

    • Never do this in a plugin or theme for release.
    • WordPress plugins rely on the correct version of jQuery being provided, that’s why I’m not using jQuery 3 and not hardcoding version numbers. Instead I’m letting WordPress set the version number for the version loaded form the CDN.

    “`

    add_action( 'init', function(){
        //Only act if in admin
        if (  ! is_admin()) {
            //set protocol dynamically
            if( is_ssl() ){
                $protocol = 'https';
            }else {
                $protocol = 'http';
            }
    
            /** @var WP_Scripts $wp_scripts */
            global  $wp_scripts;
            /** @var _WP_Dependency $core */
            $core = $wp_scripts->registered[ 'jquery-core' ];
            $core_version = $core->ver;
            $core->src = "$protocol://ajax.googleapis.com/ajax/libs/jquery/$core_version/jquery.min.js";
    
            ///Use jQuery migrate if WP_DEBUG
            if ( WP_DEBUG ) {
                /** @var _WP_Dependency $migrate */
                $migrate         = $wp_scripts->registered[ 'jquery-migrate' ];
                $migrate_version = $migrate->ver;
                $migrate->src    = "$protocol://cdn.jsdelivr.net/jquery.migrate/$migrate_version/jquery-migrate.min.js";
            }else{
                /** @var _WP_Dependency $jquery */
                $jquery = $wp_scripts->registered[ 'jquery' ];
                $jquery->deps = [ 'jquery-core' ];
            }
    
        }
    
    
    }, 11 );
    

    “`

    Notice that I’m still using WordPress’ dependency management system. Also, sets HTTPS vs HTTP using is_ssl() to avoid mixed content errors, and lets WordPress dictate version number.