Releases for Acquia Purge

This is a bugfix release for Acquia Purge.

Changelog

Issues: 4 issues resolved.
Changes since 8.x-1.3:

Bug

• #3303739 by er.garg.karan: Acquia Purge Recommendations assumes Shield is active
• Ensure non-cachable pages aren't building Acquia cache tags. (#26)

Misc

• Add php 7.4 constraint to module's composer.json. (#23)
• Add PHP 8.2 Tests (#24)

Add a summary here

This is an incremental bugfix, providing better support for Acquia's CDN service.

This is the last version of Acquia Purge that is compatible with Drupal 8.

Features since 8.x-1.1:

I'm excited to announce version 8.x-1.1-beta1 of the Acquia Purge module, which raises the level of code quality drastically, improves logging and adds private-beta CDN support for Acquia Platform CDN.

If no issues arise, this version becomes 8.x-1.1.

Installation

This version of Acquia Purge adds new functionality and is therefore still in beta.

Hello everyone,

Here at Acquia we're very happy to announce version 8.x-1.0-beta3 of the acquia_purge module for Drupal 8, the first release open for use to all of our clients. The module is still considered beta but 17 weeks of thorough testing and feedback gathering have confirmed that it works and does what it should.

I'm happy to announce version 8.x-1.0-beta2 of the Acquia Purge module for Drupal 8, the second release in the private beta phase. Progress is good and we have seen the first technical challenges on a few clients, leading to further improvements in this release. This version depends on purge 8.x-3.0-beta7 and won't work without it, so please update to 8.x-3.0-beta7.

Direct upgrade impact

• Cron processing is enabled by default now which will benefit many sites running on AJAX-only queue processing. If you are already running drush ap-process from a manual cron job, this change will work introduce more processing points and not have negative side-effects, but it can be turned off if necessary.

New Features

With excitement I'm announcing 8.x-1.0-alpha1 of the Acquia Purge module, which is theoretically able to purge URLs and tags against Acquia Cloud.

It is my pleasure to announce version 7.x-1.2 of the Acquia Purge module, this is the result of a month of testing with 7.x-1.2-beta1 which resulted in just 5 bug fixes. Therefore this release is regarded as stable and the recommended version going forwards.

This minor bugfix update fixes:

1. #2334285 Update #7103 failed with a PDO exception

Please see version 7.x-1.0's release notes: https://www.drupal.org/node/2333749

Second beta after 7.x-1.0-beta1 was released three months ago and saw its adoption increase up to 365 installation as of today's writing, that's one happy user for each day of the year. This is a mixed feature and bugfixes release but by far the biggest effort has been put into stabilizing the way it operates, smoothing out user interface parts and code quality. In-project documentation have also received their maintenance updates.

This is a very first backport attempt to serve Drupal 6 users, its the function equivalent of the upcoming 7.x-1.0-beta1. Locally everything works as it does in the D7 version, but this can not be regarded stable until we had much broader test feedback. Feel free to give it a try on your installation.

Third alpha release that polishes the previous release in terms of end-user experience and for site administrators. With the addition of a brand new diagnostic self-test system right into the core of the module it will be much easier for site administrators to detect wrong settings, incompatibilities and usage scenarios that caused our customers instabilities in the past.

High-level list of changes compared to 7.x-1.0-alpha2:

• Code cleanup to match pareview and coder.
• 2104641: fix the issue in parallel requesting-mode where the curl resource was removed from the curl_multi resource while it was already removed, removes PHP errors from your logs.
• User experience: 2014461: hide the "please wait" progress container via CSS until the JS is loaded and showing it, reduces confusing scenarios where the message is shown but nothing happens.
• User experience: the end user messaging in the progressbar is now much less technical.
• Domain detection: will now exclude the "acquia-sites.com" domain once other domains have been found, this will speedup zero-configuration installation as less domains speed up purging.
• The new diagnostics system:

Second alpha release that is a continuation of the earlier adoption of Drupal's queuing API but with further - yet experimental - changes in the underlying HTTP processing to ensure better stability when used in combination with many balancers, domains or just many purges.

Some of the important changes include:

• Drastic reduce of the burden put on the queue API and lowered item payload.
• Dynamic calculation of resources and how many HTTP requests can be done per step.
• Parallel issuing of HTTP requests, 6 at a time. Drastically speeds up purging.
• Low-level preparation for HTTPS support, not usable yet but paves the path for support.
• Drush ap-forget has been reimplemented and is now much, much faster, works under high queue loads.
• Behavior change: copying your database across environments now means that purges continue, even if they have wrong URLs. Use "drush apf" to clear the queue.
• API change: acquia_purge_purge_path() and ..paths NO LONGER take $domains as second parameter, this in order to simplify API usage and better separation of concerns.