Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Install
Works with Drupal: 8.xUsing Composer to manage Drupal site dependencies
Alternative installation files
Download acquia_purge-8.x-1.0-beta2.tar.gztar.gz
26.73 KB
MD5: ab240eb22e9580e3f3fa1ab315edf26e
SHA-1: de1af35073d49147060f99e9fae10033253e9baa
SHA-256: a7914a81c6e74e70cda9586e93e9f1196ddf071375e29cdb9ef88386f9da6643
Download acquia_purge-8.x-1.0-beta2.zipzip
37.71 KB
MD5: 5cade0da58042f537919b8c0431298d0
SHA-1: 686e297009269ec5eb67ec9cd10072d008175df0
SHA-256: a624800be89e1ee76e2fd1e3eea8d405cb46821c3bad91b4b942cdd5e06df3db
Release notes
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
.
Regressions and/or upgrade impact
- Upgrading users are expected to run
drush cr
to prevent getting:Drupal\Component\Plugin\Exception\PluginException: Plugin (acquia_purge_cloud) instance class
.
New Features
- NEW exciting diagnostic which detects basic HTTP authentication using
shield
or lines in.htaccess
. Caches its results for two hours to prevent disk reads, with a crystal clear message. - Implementation ported to Guzzle, showing great stability improvements.
- Gigantically improved error logging and debug capabilities. Using
drush p-debug-en
you can now quickly enable all of Purge's debug streams and usedrush p-invalidate
to test Acquia Purge's internal behavior, as much request and response info is logged as possible. Don't ever do this for longer than a minute on production systems!
Fixes / Improvements
- Merged
AcquiaCloudCheck
intoAcquiaPurgeCheck
to have less diagnostics floating around. - Wildcard invalidations against HTTPS paths are now simply issued as HTTP as Varnish still matches this and reduces the risk on connection/cert errors drastically.
- Tags are now always grouped by sets of 15 tags to prevent headers from getting too long.