Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Use Google Libraries · Version history

Use Google Libraries changelog and version history

Latest version
1.6.2.3
Nov 28, 2017 (9 years ago)
Releases
24
since 2008
In the last year
0
Tested up to
WordPress 4.7.39

Releases each year

  • 20081 release
  • 20095 releases
  • 20105 releases
  • 20112 releases
  • 20123 releases
  • 20132 releases
  • 20143 releases
  • 20151 release
  • 20172 releases

20172 releases

  1. Use Google Libraries 1.6.2.3Latest

  2. Use Google Libraries 1.6.2.2

20151 release

  1. Use Google Libraries 1.6.2.1

    • Bypass functionality when running under 4.2+ until next version to avoid breaking sites.

20143 releases

  1. Use Google Libraries 1.6.2

    • added some missing jQuery UI modules (hopefully fixes issues from support forums I couldn’t reproduce previously).

  2. Use Google Libraries 1.6.1

    • same as 1.6 (due to SVN issue with 1.6)

  3. Use Google Libraries 1.6

    • Drop support for PHP4, and WordPress < 3.4
    • clean up PHP 5.x strict issues

20132 releases

  1. Use Google Libraries 1.5.2

    • using protocol-relative URLS with WordPress >= 3.5
    • use WordPress provided is_ssl rather than custom check (only for WordPress < 3.5)
    • Detect if ‘jquery’ is a meta-script registration, and actual jQuery is loaded as ‘jquery-core’ tag (WordPress 3.6 Beta).

  2. Use Google Libraries 1.5.1

    • fix bug in is_ssl check.

20123 releases

  1. Use Google Libraries 1.5

    • using wp_remote_head to query that the replacement URL is actually hosted by google. If it’s not, then the WordPress supplied version will be used.
    • Using the Transient API to store the replacement URLS, rather than recalculating and re-querying them every load.

  2. Use Google Libraries 1.5b1

  3. Use Google Libraries 1.2.1

    • Added check for WordPress including non-standard versions of scripts (fixes WordPress 3.2.2/swfobject).
    • Fixed incorrect case in HTTPS check.

20112 releases

  1. Use Google Libraries 1.2

    • Reworked handling for cases where multiple js files are combined into one on Google’s servers. In the past this has been mostly a non-issue because the dependencies took care of it, but due to changes in the latest jQuery UI this stopped working as expected.

  2. Use Google Libraries 1.1.2

    • Updated jQuery UI to work with WordPress 3.1rc1

20105 releases

  1. Use Google Libraries 1.1.0.1

    • Re-disable script concatenation. Seemed to break widget admin page.

  2. Use Google Libraries 1.1

    • No longer disable script concatenation when using WordPress 3.0 or greater
    • Attempt to detect when another plugin or theme has called ‘wp_register_script’ and/or ‘wp_enque_script’ before ‘init’ and work around it.
    • Limited debugging output when WP_DEBUG is enabled.

  3. Use Google Libraries 1.0.9.2

    • Hopefully fix issue with plugin loading for some users

  4. Use Google Libraries 1.0.9.1

    • Added Incompatible Plugins and Incompatible Themes sections to the README

  5. Use Google Libraries 1.0.9

    • more https detection
    • inline jQuery.noConflict()

20095 releases

  1. Use Google Libraries 1.0.7.1

    • fix previous fix (whoops!)

  2. Use Google Libraries 1.0.7

    • Quick and dirty workaround for scriptaculous loading (thanks to Gregory Lam for bringing it to my attention

  3. Use Google Libraries 1.0.6.1

    • moved location of the Changelog section in the README

  4. Use Google Libraries 1.0.6

    • Disables script concatenation in WordPress 2.8, since it seems to have issues when some of the dependencies are outside of the concatenation.
    • Persists flag to load scripts in the footer in WordPress 2.8

  5. Use Google Libraries 1.0.5

    • Implemented a pair of suggestions from Peter Wilson.
    • It should detect when a page is loaded over https and load the libraries over https accordingly
    • It no longer drops the micro version number from the url. The reasons for this are twofold:
    • It ensures the version requested is the version received.
    • Google’s servers set the expires header for 12 months for these urls, as opposed to 1 hour. This allows clients to cache the file for up to a year without needing to retrieve it again from Google’s servers. If the version requested by your WordPress install changes, so will the URL so there’s no wo…

20081 release

  1. Use Google Libraries 1.0

Questions about Use Google Libraries’s releases

What is the latest version of Use Google Libraries?

1.6.2.3, released on Nov 28, 2017 (8 years ago). It’s tested up to WordPress 4.7.39.

How often is Use Google Libraries updated?

It had no release in the last year; the latest came out 8 years ago. Its first release on WordPress.org dates from November 2008.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in Use Google Libraries’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.