Jason Penney

<p>A number of the javascript libraries distributed with WordPress are also<br />
hosted on Google’s <a href="http://code.google.com/apis/ajaxlibs/" rel="nofollow ugc">AJAX Libraries API</a>.<br />
This plugin allows your WordPress site to use the content distribution<br />
network side of Google’s AJAX Library API, rather than serving these files from your WordPress install directly.</p>
<p>This provides numerous potential performance benefits:</p>
<ul>
<li>increases the chance that a user already has these files cached</li>
<li>takes load off your server</li>
<li>uses compressed versions of the libraries (where available)</li>
<li>Google’s servers are set up to negotiate HTTP compression with the requesting browser</li>
</ul>
<p>For a more detailed look see Dave Ward’s <a href="https://web-beta.archive.org/web/20101216143500/encosia.com/2008/12/10/3-reasons-why-you-should-let-google-host-jquery-for-you/" rel="nofollow ugc">3 reasons why you should let<br />
Google host jQuery for<br />
you</a>.</p>
<h4>Supported Libraries and Components</h4>
<ul>
<li><a href="http://dojotoolkit.org/" rel="nofollow ugc">Dojo</a></li>
<li><a href="http://jquery.com/" rel="nofollow ugc">jQuery</a></li>
<li><a href="http://ui.jquery.com/" rel="nofollow ugc">jQuery UI</a></li>
<li><a href="http://mootools.net/" rel="nofollow ugc">MooTools</a></li>
<li><a href="http://www.prototypejs.org/" rel="nofollow ugc">Prototype</a></li>
<li><a href="http://script.aculo.us/" rel="nofollow ugc">script.aculo.us</a></li>
<li><a href="http://code.google.com/p/swfobject/" rel="nofollow ugc">swfobject</a></li>
</ul>
<h4>Links</h4>
<ul>
<li><a href="http://jasonpenney.net/wordpress-plugins/use-google-libraries/" rel="nofollow ugc">Use Google Libraries Home</a></li>
<li><a href="http://github.com/jpenney/use-google-libraries/issues" rel="nofollow ugc">Issue Tracker</a></li>
<li><a href="http://github.com/jpenney/use-google-libraries" rel="nofollow ugc">GitHub Repository</a></li>
<li><a href="https://wordpress.org/support/plugin/use-google-libraries" rel="ugc">Support Forum</a></li>
</ul>
<h3>Incompatible Plugins</h3>
<h4>Better WordPress Minify</h4>
<p>Better WordPress Minify version 1.2.2 does not yet support<br />
protocol-relative URLs, but <a href="https://wordpress.org/support/topic/conflict-with-use-google-libraries-152" rel="ugc">the next release is supposed to correct<br />
this</a>.</p>
<h4>Gravity Forms</h4>
<p>I’ve had reports of Gravity Forms breaking UGL, but I don’t have<br />
access to Gravity Forms, so I’m not sure what’s going on.  If you need<br />
Gravity Forms you might need to disable UGL, or it might be fine, I’m<br />
not really sure.</p>
<h4>WP-Minify</h4>
<p>WP-Minify doesn’t yet support protocol-relative URLs.  Add<br />
‘//ajax.googleapis.com/’ as a JS and CSS exclusion.</p>
<h3>Incompatible Themes</h3>
<h4>K2</h4>
<p>I’ve had scattered reports that UGL is stepping out of the way when<br />
using K2.</p>
<h3>A Request</h3>
<p>If you’re going to flag the plugin as “broken” in the WordPress Plugin<br />
Directory, please try and <a href="https://wordpress.org/tags/use-google-libraries?forum_id=10" rel="ugc">let me know <em>what</em> is<br />
broken</a>.<br />
I’m not a mind reader.</p>
<h3>Technical Details</h3>
<p><strong>Use Google Libraries</strong> uses the following hooks (each with a priority of 1000).</p>
<h4>wp_default_scripts</h4>
<p><strong>Use Google Libraries</strong> compares it’s list of supported scripts to those<br />
registered, and replaces the standard registrations <code>src</code> with ones that<br />
point to Google’s servers.  Other attributes (like dependencies) are left<br />
intact.</p>
<h4>script_loader_src</h4>
<p><strong>Use Google Libraries</strong> removes the <code>ver=x.y.z</code> query string from the URL<br />
used to load the requested library <em>if</em> it is going to load the library from<br />
    ajax.googleapis.com.  Otherwise the URL is left unaltered.  This both<br />
improves the chances of the given URL already being cached, and prevents<br />
<strong>script.aculo.us</strong> from including scripts multiple times.</p>
<p>If jQuery is enqued <strong>Use Google Libraries</strong> will inject a bit of<br />
javascript before the next enqueued script enabling jQuery’s <a href="http://docs.jquery.com/Core/jQuery.noConflict" rel="nofollow ugc">noConflict mode</a> as it would<br />
with the standard WordPress version.</p>
<h3>References</h3>
<p>Parts of this plugin (specificly, the dropping of the micro number,<br />
which has since been removed for better caching performance) were<br />
inspired by John Blackbourn’s<br />
<strong><a href="http://lud.icro.us/wordpress-plugin-google-ajax-libraries/" rel="nofollow ugc">Google AJAX Libraries</a></strong>,<br />
which has very similar goals to this plugin.</p>
<h3>Future Plans</h3>
<ul>
<li>add ability to disable protocol relative URLs</li>
<li>add ability to disable on frontend and/or admin</li>
</ul>


Use Google Libraries

you will be received 5/5 stars, once it's updated and functioning as used to be. thanks...

edit: thanks for updating :) 

please update it

Allows your site to use common javascript libraries from Google's AJAX Libraries CDN, rather than from WordPress's own copies.

Takayuki Miyauchi

Okamoto Hidetaka

AMIMOTO

DigitalCube Inc.

wokamoto

Bartosz Gadomski

John Blackbourn

Hinaloe

jepser

Sander van Dragt

<p>This is simple plugin that clear all cloudfront cache if you publish posts.<br />
You can easy use CloudFront in front of WordPress.</p>
<h3>Fixtures</h3>
<ul>
<li>
<p>wp_is_mobile()<br />
Check device viewer type by CloudFront header.<br />
Now supports <code>HTTP_CLOUDFRONT_IS_MOBILE_VIEWER</code> and <code>HTTP_CLOUDFRONT_IS_TABLET_VIEWER</code>.</p>
</li>
<li>
<p>preview url<br />
In preview page, plugin add <code>post_date</code> query to avoid CloudFront cache.<br />
And set <code>wordpress_loginuser_last_visit</code> cookie for avoid CloudFront cache too.</p>
</li>
</ul>
<p>The <code>wordpress_loginuser_last_visit</code> cookie will be removed if user sign out.</p>
<h4>Invalidation(Clear Cache) Page URL</h4>
<p>This plugin send following page url to CloudFront Invalidation API.</p>
<ul>
<li>TOP page URL</li>
<li>Published Post Page URL</li>
<li>Category Archive Page URL</li>
</ul>
<h3>AWS IAM Policy Example</h3>
<pre><code>{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "cloudfront:GetDistribution",
                "cloudfront:ListInvalidations",
                "cloudfront:GetStreamingDistribution",
                "cloudfront:GetDistributionConfig",
                "cloudfront:GetInvalidation",
                "cloudfront:CreateInvalidation"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}
</code></pre>
<p><strong>Note:</strong> The <code>cloudfront:GetInvalidation</code> permission is required for viewing detailed invalidation information. If this permission is not granted, the detail view feature will be disabled gracefully without affecting other plugin functionality.</p>
<h3>Adding your configuration through env vars</h3>
<p>The plugin can be configured by defining the following variables:</p>
<ul>
<li><code>AWS_ACCESS_KEY_ID</code></li>
<li><code>AWS_SECRET_ACCESS_KEY</code></li>
<li><code>C3_DISTRIBUTION_ID</code></li>
</ul>
<p>You can put these variables like the code into the wp-config.php</p>
<pre><code>php
define( 'AWS_ACCESS_KEY_ID', '' );
define( 'AWS_SECRET_ACCESS_KEY', '' );
define( 'C3_DISTRIBUTION_ID', '' );
</code></pre>
<h3>Cookie</h3>
<p>This plugin set a Cookie named <code>wordpress_loginuser_last_visit</code> to the user.<br />
It prevents CDN caching when the user is previewing his posts or contents.<br />
Once logging out from Dashboard, plugin removes this cookie from user.</p>
<h3>7.1.0</h3>
<ul>
<li>[Feature] Add invalidation detail view with modal popup showing invalidation paths, caller reference, and status</li>
<li>[Fix] Fix invalid path returned for post type without archive page</li>
</ul>
<h3>7.0.1</h3>
<ul>
<li>[Update] Improved AWS API call processing for better security and PHP 8.x compatibility</li>
</ul>
<h3>7.0.0</h3>
<ul>
<li>[Breaking Change] Remove AWS SDK dependency and implement custom HTTP CloudFront API client</li>
<li>[Update] Add comprehensive invalidation logging with c3_log_invalidation_list filter</li>
<li>[Update] Add configurable CloudFront region and HTTP timeout settings</li>
</ul>
<h3>6.1.6</h3>
<ul>
<li>[Fix] Fixed PHP 8 syntax errors by adding nullable type hints</li>
<li>[Fix] Fixed deprecation warnings about creation of dynamic properties in Invalidation_Service.php</li>
<li>[Fix] Fixed deprecation warnings about creation of dynamic properties in Cron_Service.php</li>
<li>[Fix] Fixed PHP 7.4 syntax errors in test files</li>
</ul>
<h3>6.1.5</h3>
<ul>
<li>[Fix] Changed to install the AWS SDK using composer instead of aws.phar.</li>
</ul>
<h3>6.1.4</h3>
<ul>
<li>[Update] Support post_type_archive_link</li>
</ul>
<h3>6.1.3</h3>
<ul>
<li>[Fix] Lost filter c3_invalidation_items From v6.0.0</li>
</ul>
<h3>6.1.2</h3>
<ul>
<li>[Fix] php version compare issue</li>
</ul>
<h3>6.1.1</h3>
<ul>
<li>[Fix] Plugin deactivation issue</li>
</ul>
<h3>6.1.0</h3>
<ul>
<li>[Update] Flush cache by post_ids</li>
</ul>
<h3>6.0.0</h3>
<ul>
<li>[Breaking Change] Re-write entire code</li>
<li>[Update] Add <code>c3_log_cron_invalidation_task</code> filter to show cron job Logs</li>
<li>[Update] Add <code>c3_aws_sdk_path</code> filter to change or remove bundled AWS SDK path</li>
</ul>
<h3>5.5.1</h3>
<ul>
<li>[Update] Replace the top level menu with a Settings submenu</li>
</ul>
<h4>5.5.0</h4>
<ul>
<li>[Update] Can use defined variables for AWS Credentials</li>
</ul>
<h4>5.4.2</h4>
<ul>
<li>[Bug fix] Set cookie path in preview page</li>
</ul>
<h4>5.4.1</h4>
<ul>
<li>[Bug fix] Undefined Paths index in invalidation query cron event</li>
</ul>
<h4>5.4.0</h4>
<ul>
<li>[Update] Update preview fix plugin</li>
</ul>
<h4>5.3.4</h4>
<ul>
<li>[Bug fix] Small bug fix</li>
</ul>
<h4>5.3.3</h4>
<ul>
<li>[Change SDK] replace sdk</li>
</ul>
<h4>5.3.2</h4>
<ul>
<li>[Bug fix] Use EC2 role if using as AMIMOTO Managed hosting</li>
</ul>
<h4>5.3.1</h4>
<ul>
<li>[Add filter] Can select AWS SDK version by filter</li>
</ul>
<h4>5.3.0</h4>
<ul>
<li>[Update SDK] Use AWS SDK v3 when you using php 5.6 or later</li>
</ul>
<h4>5.2.1</h4>
<ul>
<li>[For AMIMOTO Managed] bug fix to run by WP-CLI</li>
</ul>
<h4>5.2.0</h4>
<ul>
<li>[Add filter] We can disable to register wp-cron that retry request invalidation.</li>
<li>[Readme] Update readme to see IAM Policy example.</li>
</ul>
<h4>5.1.0</h4>
<ul>
<li>[Update preview fixture] Set cookie to avoid CloudFront cache if user sign in</li>
<li>[Update preview fixture] Unset cookie for avoide CloudFront cache if user sign out</li>
</ul>
<h4>5.0.0</h4>
<ul>
<li>Support CloudFront viewer params on <code>wp_is_mobile()</code>.(4.9.0 or later)</li>
</ul>
<h4>4.4.0</h4>
<ul>
<li>Fix small bug</li>
<li>Add some feature for AMIMOTO Managed hosting user</li>
</ul>
<h4>4.3.1</h4>
<ul>
<li>Fix cron interval</li>
<li>add filters <code>'c3_invalidation_interval</code>, <code>c3_invalidation_cron_interval</code>, <code>c3_invalidation_item_limits</code>.</li>
<li>update default invalidation interval & items.</li>
</ul>
<h4>4.3.0</h4>
<ul>
<li>Schedule cron event if you published many post at the same time</li>
</ul>
<h4>4.2.1</h4>
<ul>
<li>Fix ‘c3_credential’ filter position</li>
</ul>
<h4>4.2.0</h4>
<ul>
<li>Support AMIMOT Dashboard</li>
</ul>
<h4>4.1.0</h4>
<ul>
<li>Show Invalidation Logs</li>
</ul>
<h4>4.0.3</h4>
<ul>
<li>Auto Deploy by Travis</li>
</ul>
<h4>4.0.2</h4>
<ul>
<li>Add WP-CLI param check ( wp c3 flush)</li>
<li>change transient_key</li>
</ul>
<h4>4.0.1</h4>
<ul>
<li>Bug fix ( conflict Nephila Clavata )</li>
</ul>
<h4>4.0.0</h4>
<ul>
<li>Support AWS SDK Version3</li>
<li>Remove action hook -> ‘c3_add_setting_before’<br />
use ‘c3_after_title’ filter hook instead.</li>
<li>Remove action hook -> ‘c3_add_setting_after’<br />
use ‘c3_after_auth_form’ filter hook instead.</li>
</ul>
<h4>3.0.0</h4>
<ul>
<li>Include CF Preview Fix plugin</li>
<li>Rename</li>
</ul>
<h4>2.4.3</h4>
<ul>
<li>Fix Catch Exception BUG</li>
</ul>
<h4>2.4.2</h4>
<ul>
<li>Fix CLI BUG</li>
</ul>
<h4>2.4.1</h4>
<ul>
<li>Fix CLI BUG</li>
</ul>
<h4>2.4.0</h4>
<ul>
<li>Add WP-CLI Command ( Update Settings )</li>
</ul>
<h4>2.3.0</h4>
<ul>
<li>Add WP-CLI Command</li>
</ul>
<h4>2.2.2</h4>
<ul>
<li>Force Invalidation</li>
</ul>
<h4>2.2.1</h4>
<ul>
<li>Fix Typo</li>
</ul>
<h4>2.2.0</h4>
<ul>
<li>Add Filter for using EC2 Instance Role.</li>
<li>Translationable in t.w.org</li>
</ul>
<h4>2.1.1</h4>
<ul>
<li>Fix too many invalidation url error.</li>
</ul>
<h4>2.1.0</h4>
<ul>
<li>Add hook to customize invalidation URL</li>
<li>support new invalidation url, terms.</li>
<li>Manualy invalidation button added</li>
</ul>
<h4>2.0.2</h4>
<ul>
<li>Change AWS SDK</li>
<li>code refactoring by wokamoto</li>
<li>Invalidation URL</li>
</ul>
<h4>2.0.1</h4>
<ul>
<li>Change AWS SDK</li>
<li>code refactoring by wokamoto</li>
<li>Invalidation URL</li>
</ul>
<h4>1.0</h4>
<ul>
<li>Initial released.</li>
</ul>
<h3>6.1.0</h3>
<ul>
<li>[Fix] Plugin deactivation issue</li>
</ul>


C3 Cloudfront Cache Controller

This is simple plugin that clear all cloudfront cache if you publish posts.

Use Google Libraries vs C3 Cloudfront Cache Controller