Install
Works with Drupal: 7.xUsing Composer to manage Drupal site dependencies
Downloads
Release notes
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:
- drush ap-diagnosis: will present site administrators with a full info/ok/warning/error report specific to Acquia Purge and its working environment, confirming things that are good and explaining things that aren't good.
- status report: is fully ported over to use the diagnostic tests underneath. Acquia Purge will only expose 1 item to the status report in good conditions but adds all warning and error message. Explanations are also added here.
- watchdog log: will see all "error" level issues being logged whenever they occur.
- protecting purges: end-users will be notified directly when "error" level issues occur, as purging will be halted and items remain in the queue till the problem is fixed.
With the diagnostic checks built-in I can recommend everybody to upgrade their module and to check if their site is running optimally, in addition to a smoother experience. With the diagnostic tests deciding whether purging can continue at all it might happen to you that the site that was purging fine before, now refuses to continue: check your status report or "drush ap-diagnosis" to find out why and how to improve your configuration.
Feedback welcome,
Niels