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.
This is the first actual release of purge that fully supports Drupal 10. Note some Javascript tests no longer work due to classy being removed. This will be fixed in a subsequent release but should not affect the normal usage of this module.
This is a emergency release because 8.x-3.1 caused two major issues. Firstly, the deprecation of FilterResponseEvent::isMainRequest() introduced fatal errors on many support D8 and D9 releases and secondly, a unintended hard dependency was put onto the dynamic page cache module, which is now implicitly being checked.
Please test 8.x-3.2 with the same rigor as I recommended for 8.x-3.1.
I'm happy to announce version 8.x-3.1 of the Purge module for Drupal 8 and 9, the first stable release since nine beta releases. The Purge project now reports 19093 installations at this point which makes it high time for a stable to be released.
While this is mostly a bugfix release, the change for issue 2976480 reduces the occurences of Cache Tag headers are rendered on responses and that could mean a change for some installations, proper prior testing is recommended.
Exactly 6 years, 2 months, 19 days since the first commit for the D8 version of purge, I'm extremely excited to present the first stable release of the project - version 8.x-3.0. Not only brings this stable version a guarantee of functional stability, it also brings much anticipated security coverage.
This release carries very little functional difference compared to -beta8, but marks the module as fully Drupal 9-ready and brings a vast amount of quality and test improvements along with it.
Long overdue release for Purge carrying various API changes and Drush 9 support as main feature. This release is the last beta before the codebase is deemed fully stable (and as a result, API changes will stop to happen).
Please don't upgrade blindly and test your preexisting setup well.
Please run drush cr to accommodate for the various API changes!
Hereby I'm happy to release version 8.x-3.0-beta5 of the Purge module, a project in development for over two years and getting closer to the point where it can be used in production environments. Usage statistics have rapidly climbed in the last couple of weeks and brought us into the 500 installations range, which is quite high for a beta module.
Fixed \Drupal\purge\Plugin\Purge\Queue\StatsTracker::destruct() which was potentially writing the buffer multiple times.
Fixed \Drupal\purge\Plugin\Purge\Invalidation\ImmutableInvalidationBase::getState() - Catch combination states where one or more purgers added NOT_SUPPROTED but other purgers added states as well.
commit 10baf1d7ea6888dd1843b3b9246b527ff425971d
Author: Niels van Mourik <>
Date: Fri Mar 11 14:44:50 2016 +0100
The service 'purge.queue.txbuffer' becomes public, the acquia_purge module depends on it.
Purge version 8.x-3.0-beta1 - codename Hello World!
The modular external cache invalidation framework.
The Purge module for Drupal 8 enables invalidation of content from external caches, reverse proxies and CDN platforms. The technology-agnostic plugin architecture allows for different server configurations and use cases. Last but not least, it enforces a separation of concerns and should be seen as a middleware solution.
* Dropping hard dependency on Expire module.
* Dropped support for Acquia Cloud. Used Acquia Purge instead. http://drupal.org/project/acquia_purge
* Fixed curl issues for PHP 5.3.18+
* Dropping hard dependency on Expire module.
* Dropped support for Acquia Cloud. Used Acquia Purge instead. http://drupal.org/project/acquia_purge
* Fixed curl issues for PHP 5.3.18+
Bugfix release. Fixing various minor issues including:
Issue #1299776: Sending purge request should retain url path and query string.
Issue #1502915 by hernani,jaydub: Purge multiple domains
Issue #1760408 by heddn: Invalid error logic and logging
Issue #1551232 by pbull,asgorobets: proxy_url_base is not set when using ah purge method
Bugfix release. Fixing various minor issues including:
Issue #1299776: Sending purge request should retain url path and query string.
Issue #1502915 by hernani,jaydub: Purge multiple domains
Issue #1760408 by heddn: Invalid error logic and logging
Issue #1551232 by pbull,asgorobets: proxy_url_base is not set when using ah purge method
New branch for the next series of releases of Purge for D7. Will not be stable for quite some time so stick to the 7.x-1.x branch for you production sites.
A release candidate with a few bugfixes since the 1.4 release:
- Issue #1362990 by jaydub: Bug in watchdog.
- Issue #1299776 by djbobbydrake: Sending purge request via purge method should retain url query string.
- Issue #1327216 by mauritsl,msonnabaum,chx,mongolito404: Fixed Thousands of calls to curl_multi_exec
- Issue #1403072 by jaydub: Fixed bad variable passed to watchdog
Please give it a spin and report any issues you encounter.
First release candidate for a stable version of Purge for Drupal 7.x. No new features from the 6.x-1.x branch, just a straight port. Please give it a spin and report any issues.
Bug fix release:
- Issue #1292338 by chhay: Token mismatch in watchdog purge error message
- Issue #1327216 by mauritsl: Fix for thousands of calls to curl_multi_exec
- Added support for Acquia Hosting services.
- Added form validation and error detection in the configuration forms.
- Minor syntax and coding style fixes.
Refactoring for Nginx and future platform support and better error handling.
Issue #1048000: Basic Nginx support.
Issue #1050320: Error handling and watchdog improvements.