acquia_purge 7.x-1.0-beta2

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.

Important changes compared to 7.x-1.0-beta1:

• [FEATURE] the Manual Purge-form: is a new administration interface that could be found at admin/config/development/performance/manualpurge and is aimed at system administrators that quickly need a few paths purged in cases of emergency or during test phases. The form allows direct purges to occur but is only accessible by users holding the administer site configuration-permission. Much testing and feedback has been done by the community approving the new feature (2140037, 2140035, 2140033, 2179265)
• [FEATURE] Cache Expiration 7.x-2.0-beta2 support: has been added to accommodate users wanting to use the 7.x-2.0-beta2 from expire, which allows much more granular control over what's getting purged or not. This should help users fight against overzealous and needless purges that sometimes occur in combination with migrations and other things.
• [POLISH] Many documentation updates: to README.txt, FAQ.txt and smaller improvements to comply with coder and pareview across the codebase.
• [POLISH] UI improvements: have found their way into certain area's to make things easier for users, for instance AP's status is now also reported on Cache Expiration 7.x-2.0-beta2's configuration page as other smaller changes.
• [CHANGE] Cache Expiration removed settings : certain settings from the expire module have shown to cause severe issues in combination with Acquia Purge, most notably the Include base URL in expires setting in version 7.x-1.0-beta1 of expire but also the debugging mode of expire 7.x-2.x has been disabled to not cause issues. These settings are now disabled, hardcoded and hidden from the interface to cause users any issues. Especially the former might break a few setups in combination with Domain Access and therefore requires further testing, users not relying on Domain Access should not see any differences.
• [CHANGE] "Report cache purges"-setting removed: The setting 'Report cache purges' allowed site administrators to control the visual appearance of the purging progressbar but the problem that had slipped in along the course of module development was that there was also a 'Purge notification'-permission with equal meaning. The configuration setting has been dropped in favor of fully controlling the progressbar using that permission, which will cause the progressbar to always show up for uid 1.
• [CHANGE] AJAX Purging parallelization : In previous releases the user who changed something saw the progressbar and his/her browser was responsible for finishing the queue, not anymore. This behavior often caused the unwanted side-effect of a user closing his browser and continuing to own the cleaning of the queue. Now all logged in users will "fight the queue" till it has been emptied, disable the progressbar if it creates unwanted visual effects.
• [BUGFIX] Don't detect ELB-domains: when the module is running in zero-configuration mode (not hardcoding domains in settings.php. The ELB domain name can't be purged and doesn't need be.
• [BUGFIX] Drush ap-process, ap-purge: now check for critical error conditions through the diagnostic system before working, safeguarding operation better.
• [BUGFIX] 2049235: fixed Acquia Purge's progressbar showing up in the Media browser popup.

This release does require a little bit of testing than usually required but the changes done are intended to simplify and further stabilize the project before we release an official stable 7.x-1.0 version. Feedback gathered the coming weeks and months will flow into the next stable and I'll be very conservative when it comes to new changes or features from this point.

Feedback welcome,

Niels