Changed supported version to < WP 4.8<\/p>"},"ratings":{"1":6,"2":1,"3":1,"4":1,"5":38},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0","1.0.5","1.0.6","1.0.6.1","1.0.7","1.0.7.1","1.0.9","1.0.9.1","1.0.9.2","1.1","1.1.0.1","1.1.2","1.2","1.2.1","1.5","1.5.1","1.5.2","1.5b1","1.6","1.6.1","1.6.2","1.6.2.1","1.6.2.2"],"block_files":[],"assets_screenshots":[],"screenshots":[],"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[3863,150,229,202,247],"plugin_category":[54,59],"plugin_contributors":[78096],"plugin_business_model":[],"class_list":["post-390","plugin","type-plugin","status-publish","hentry","plugin_tags-cdn","plugin_tags-google","plugin_tags-javascript","plugin_tags-jquery","plugin_tags-performance","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-jczorkmid","plugin_committers-jczorkmid"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/use-google-libraries.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
A number of the javascript libraries distributed with Wordpress are also \nhosted on Google's AJAX Libraries API<\/a>.\nThis plugin allows your Wordpress site to use the content distribution \nnetwork side of Google's AJAX Library API, rather than serving these files from your WordPress install directly.<\/p>\n\n This provides numerous potential performance benefits:<\/p>\n\n For a more detailed look see Dave Ward's 3 reasons why you should let\nGoogle host jQuery for\nyou<\/a>.<\/p>\n\n Better WordPress Minify version 1.2.2 does not yet support\nprotocol-relative URLs, but the next release is supposed to correct\nthis<\/a>.<\/p>\n\n I've had reports of Gravity Forms breaking UGL, but I don't have\naccess to Gravity Forms, so I'm not sure what's going on. If you need\nGravity Forms you might need to disable UGL, or it might be fine, I'm\nnot really sure.<\/p>\n\n WP-Minify doesn't yet support protocol-relative URLs. Add\n'\/\/ajax.googleapis.com\/' as a JS and CSS exclusion.<\/p>\n\n I've had scattered reports that UGL is stepping out of the way when\nusing K2.<\/p>\n\n If you're going to flag the plugin as \"broken\" in the WordPress Plugin\nDirectory, please try and let me know what<\/em> is\nbroken<\/a>.\nI'm not a mind reader.<\/p>\n\n Use Google Libraries<\/strong> uses the following hooks (each with a priority of 1000).<\/p>\n\n Use Google Libraries<\/strong> compares it's list of supported scripts to those \nregistered, and replaces the standard registrations Use Google Libraries<\/strong> removes the If jQuery is enqued Use Google Libraries<\/strong> will inject a bit of\njavascript before the next enqueued script enabling jQuery's noConflict mode<\/a> as it would \nwith the standard WordPress version.<\/p>\n\n Parts of this plugin (specificly, the dropping of the micro number,\nwhich has since been removed for better caching performance) were \ninspired by John Blackbourn's \nGoogle AJAX Libraries<\/a><\/strong>, \nwhich has very similar goals to this plugin.<\/p>\n\n Google has stated that they intend to keep every file they've hosted \navailable indefinitely, so you shouldn't need to worry about them \ndisappearing.<\/p><\/dd>\n Firstly, if you are using a caching plugin, flush the cache or\ntemporarily disable it to be sure it's not doing anything. That said,\nI've done my best to make Use Google Libraries<\/strong> gracefully step out\nof the way when things are not as expected. While not, perhaps,\ngiving you the greatest benefit it helps ensure you site doesn't just\nflat out stop working.<\/p>\n\n In general, anything that calls wp_register_script and\/or\nwp_eneque_script before 'init' causes trouble for Use Google\nLibraries<\/strong>. I've made an effort to force it to try and run anyhow,\nso please report any issues with this. If you have 'WP_DEBUG'\nenabled, a message will be logged letting you know this is happening.<\/p>\n\n Please see the section on Incompatible Plugins<\/strong> and\nIncompatible Themes<\/strong> for specific information.<\/p><\/dd>\n The same way you use them when Use Google Libraries isn't installed using \n'wp_enqueue_script'. In fact you should develop your theme or plugin without\nUse Google Libraries being enabled at all, then test it both ways.<\/p><\/dd>\n Assuming some other plugin or theme isn't the cause, Use Google Libries does \nit's very best to ensure your site behaves as it should when using the stock \nWordPress scripts. If WordPress is asking for a version of a script that \nGoogle isn't hosting, then it will continue to use the WordPress supplied \nversion.<\/p><\/dd>\n No. Use Google Libraries doesn't do that because it would almost certainly \nbreak WordPress. Even if it didn't, the less 'version specific' URLs supported \nby Google's CDN set a short term 'Expires' header, so there wouldn't be much\npoint.<\/p><\/dd>\n\n<\/dl>\n\n\n Implemented a pair of\nsuggestions<\/a>\nfrom Peter Wilson<\/a>.<\/p>\n\n\n
Supported Libraries and Components<\/h4>\n\n
\n
Links<\/h4>\n\n
\n
Incompatible Plugins<\/h3>\n\n
Better WordPress Minify<\/h4>\n\n
Gravity Forms<\/h4>\n\n
WP-Minify<\/h4>\n\n
Incompatible Themes<\/h3>\n\n
K2<\/h4>\n\n
A Request<\/h3>\n\n
Technical Details<\/h3>\n\n
wp_default_scripts<\/h4>\n\n
src<\/code> with ones that \npoint to Google's servers. Other attributes (like dependencies) are left \nintact.<\/p>\n\nscript_loader_src<\/h4>\n\n
ver=x.y.z<\/code> query string from the URL\nused to load the requested library if<\/em> it is going to load the library from\n ajax.googleapis.com. Otherwise the URL is left unaltered. This both \nimproves the chances of the given URL already being cached, and prevents \nscript.aculo.us<\/strong> from including scripts multiple times.<\/p>\n\nReferences<\/h3>\n\n
Future Plans<\/h3>\n\n
\n
use-google-libraries<\/code> folder to the \/wp-content\/plugins\/<\/code> folder.\n\nActivate Use Google Libraries<\/strong> through the 'Plugins' menu in WordPress.\n\nEr... That's it really.\n\n\n\n
use-google-libraries<\/code> folder to the \/wp-content\/plugins\/<\/code> folder.\n\nActivate Use Google Libraries<\/strong> through the 'Plugins' menu in WordPress.\n\nEr... That's it really.<\/dd>\n1.6.2.3<\/h4>\n\n
\n
1.6.2.1<\/h4>\n\n
\n
1.6.2<\/h4>\n\n
\n
1.6.1<\/h4>\n\n
\n
1.6<\/h4>\n\n
\n
1.5.2<\/h4>\n\n
\n
is_ssl<\/code> rather than custom check (only for\nWordPress < 3.5)<\/li>\n1.5.1<\/h4>\n\n
\n
is_ssl<\/code> check.<\/li>\n<\/ul>\n\n1.5<\/h4>\n\n
\n
wp_remote_head<\/code> to query that the replacement URL is actually\nhosted by google. If it's not, then the WordPress supplied version will be \nused.<\/li>\n1.2.1<\/h4>\n\n
\n
1.2<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.0.1<\/h4>\n\n
\n
1.1<\/h4>\n\n
\n
1.0.9.2<\/h4>\n\n
\n
1.0.9.1<\/h4>\n\n
\n
1.0.9<\/h4>\n\n
\n
1.0.7.1<\/h4>\n\n
\n
1.0.7<\/h4>\n\n
\n
1.0.6.1<\/h4>\n\n
\n
1.0.6<\/h4>\n\n
\n
1.0.5<\/h4>\n\n
\n
\n