Releases for CDN

Official release from tag: 6.x-2.6

Release notes

Changes since 6.x-2.5:

• #1893170 by c4doug | martinjbaker: Fixed Patch file fails with Drupal 6.28.
• #1557928 by Wim Leers: Don't require CSS aggregation to be enabled when the AdvAgg module is enabled
• #1634932 by Wim Leers: CSS aggregation with HTTPS + clear cache: CDN's CSS cache not actually cleared
• Fixed #1576458: PHP Error: Function Redeclare
• #1572794: Move constant declarations to their own file
• Fixed #1552456: CDN module says there's a problem with the configuration, while it may be deliberate
• Fixed #1593930 by mstrelan and Wim Leers: cdn_get_domains() is broken for auto-balancing when using protocol-relative domains: fix + tighten tests
• Fixed #1623252: Only rewrite image links when they have the same file extension as the image's
• Problem with cdn_admin_other_settings_form_validate() and cdn_pick_server()
• After install: erroneous call to variable_get()
• #1549582: Problem with CDN CSS aggregation with multiple stylesheets with same filename

Official release from tag: 7.x-2.5

Release notes

For details, see the changelog below. High-level changes:
- new: Automatically distribute certain filetypes over multiple CDNs (with unit tests) — makes the parallel_css module obsolete
- new: Support rewriting file URLs in blocks (D7-only)
- new: Cache Audit support
- fix: Create different CSS aggregation files for HTTP and HTTPS
- fix: UFI mapping not correctly applied (now with unit tests)
- UX: Warn users that CSS aggregation should be enabled
- UX: Warn users when using Far Future expiration with a static file server or same-server-subdomains

If you're using Origin Pull and the Far Future expiration option and you're still on version 2.2, upgrade ASAP: SA-CONTRIB-2012-022 - CDN - Information disclosure!

Important!
You have to rebuild your menus (only if you're upgrading from version 2.2), so that the new Far Future URLs actually work, plus you have to clear the CSS cache (even if you're already on version 2.3) so that the file URLs in the CSS files (usually to images, but also fonts, for example) are updated to use correct Far Future URLs.
You can do that:
- with Drush: drush cc menu && drush cc css+js.

Read more

Official release from tag: 6.x-2.4

Release notes

Many small bug fixes, most relating to Far Future expiration, but on D6 the Fallback mechanism (which is only used when you haven't applied the Drupal core patch and aren't using Pressflow/Cocomore). Very important: Far Future expiration is now disabled by default, because some users were experiencing problems with it. Those problems should now all be a thing of the past though!
Small new feature: revamped per-page statistics. Better documentation for Far Future expiration (it requires CSS aggregation to be enabled!). And … finally the first unit tests (only on D7 though, but significant portions of code are identical, so it's useful for D6 as well to some degree)!

If you're using Origin Pull and the Far Future expiration option and you're still on version 2.2, upgrade ASAP: SA-CONTRIB-2012-022 - CDN - Information disclosure!

Important!
You have to rebuild your menus (only if you're upgrading from version 2.2), so that the new Far Future URLs actually work, plus you have to clear the CSS cache (even if you're already on version 2.3) so that the file URLs in the CSS files (usually to images, but also fonts, for example) are updated to use correct Far Future URLs.
You can do that:
- with Drush: drush cc menu && drush cc css+js.

Read more

Official release from tag: 7.x-2.3

Release notes

Many small bug fixes, some new features (overridden Drupal core's CSS aggregation to alter image URLs, DNS prefetching, CORS support, new UFI method) and a security fix.

If you're using Origin Pull and the Far Future expiration option, upgrade ASAP: SA-CONTRIB-2012-022 - CDN - Information disclosure!

Important!
You have to rebuild your menus, so that the new Far Future URLs actually work, plus you have to clear the CSS cache so that the file URLs in the CSS files (usually to images, but also fonts, for example) are updated to the new style.
You can do that:
- with Drush: drush cc menu && drush cc css+js.
- just through Drupal's UI: submitting the modules page and clicking "Clear all caches" at admin/config/development/performance in D7

Changes since 7.x-2.2:

Read more

Official release from tag: 6.x-2.2

Release notes

Version 2.1 was already very stable. This release fixes all known bugs.

Major new functionality:
- Far Future expiration support
- Advanced Help support
- hook_cdn_blacklist(): modules can now blacklist files that should not be served from a CDN

Changes since 6.x-2.1:

Read more

Official release from tag: 7.x-2.0-beta1

Release notes

Initial port of the CDN module to Drupal 7. All functionality has been ported. An upgrade path is provided.

This should be fairly stable. Feedback is of course very much welcomed.

Official release from tag: 6.x-2.0

Release notes

The goal for 2.0 is simple: make the CDN module kick ass. This will be done in three ways:

1. ✓ significant expansion of functionality
2. ✓ awesome UI
3. ✓ excellent documentation, including high-quality screencasts

(Screencasts are yet to be made.)

Upgrade notes
(Can also be found in UPGRADE.txt.)

Upgrading from CDN integration 1.x to 2.x requires applying a new core patch. Alternatively, there is now a new type of CDN integration that does not require a core patch, instead it relies on the theme layer to alter file URLs. It is slower and won't be able to alter *all* file URLs, but it is easier to use. When the module detects that the patch is not applied, it will automatically fall back to this mechanism.
Also note that the core patch is already included in Pressflow!

The recommended steps to update your Drupal site are:
1) Copy the 1.x core patch (patches/drupal6.patch) to the Drupal root directory.
2) Revert the 1.x core patch:

3) Disable CDN integration at admin/settings/cdn.
4) Update the CDN integration module code.
5) Copy the 2.x core patch (patches/drupal6.patch) to the Drupal root directory.
6) Apply the 2.x core patch:

7) Re-enable CDN integration at admin/settings/cdn. Read more

Official release from tag: 6.x-2.0-rc5

Release notes

The goal for 2.0 is simple: make the CDN module kick ass. This will be done in three ways:

1. ✓ significant expansion of functionality
2. ✓ awesome UI
3. excellent documentation, including high-quality screencasts

IMPORTANT NOTE:
The Drupal core patch has changed in beta 6 (not in this RC)! So, before updating, revert the patch of beta 3 (or from beta 2, if you're upgrading from beta 2). Then update the code. Then apply the new patch.

Changes since DRUPAL-6--2-0-RC4:

• Fixed #956778: Fallback mode always enabled at admin/settings/cdn* and admin/reports/status
• Slight performance improvement in cdn_file_url_alter().
• Fixed #956164: Eval'd PHP code version of cdn_pick_server() not working + improve docs

Official release from tag: 6.x-2.0-rc3

Release notes

The goal for 2.0 is simple: make the CDN module kick ass. This will be done in three ways:

1. ✓ significant expansion of functionality
2. ✓ awesome UI
3. excellent documentation, including high-quality screencasts

IMPORTANT NOTE:
The Drupal core patch has changed in beta 6 (not in this RC)! So, before updating, revert the patch of beta 3 (or from beta 2, if you're upgrading from beta 2). Then update the code. Then apply the new patch.

Changes since DRUPAL-6--2-0-RC2:

• Fixed #942668: Fallback mechanism despite running Pressflow
• #948422: Minimize the amount of code loaded on each page: move hook_requirements() to the .install file
• #948454: Minimize the amount of code loaded on each page even further