WordPress.org

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.

1.1.2

• Updated jQuery UI to work with WordPress 3.1rc1

1.1.0.1

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

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.

1.0.9.2

• Hopefully fix issue with plugin loading for some users

1.0.9.1

• Added Incompatible Plugins and Incompatible Themes sections to the README

1.0.9

• more https detection
• inline jQuery.noConflict()

1.0.7.1

• fix previous fix (whoops!)

1.0.7

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

1.0.6.1

• moved location of the Changelog section in the README

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

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 worry that you'll keep loading an old version.