Downloads
Release notes
Please review carefully. This release introduces important changes:
* experimental wrappers for CSV import/export
* civicrm-api: process the cron jobs using the JobManager facility (the recommended way to use the cron is now 'drush @your-site-alias civicrm-api Job execute').
* implement hook_provision_apache_vhost_config() to restrict access to /files/civicrm (logs, templates, uploaded files) - if you have custom CSS/JS, you should place them in a Drupal module.
* support for CiviCRM 4.2: #1688346: Update bootstrap code for 4.2 (by totten)
* support for Drupal 6 in CiviCRM 4.1
* in >= 4.1, do not create the civicron user anymore since the cron does not require it (see #1689520: creation of cron drupal user account)
* better support (or tolerance) for older versions of CiviCRM (1.x and 2.x)
* #1461610: Upgrade from Civi 3x to 4x fails : refactoring to move some verify operations to Deploy, run civicrm-upgrade-db only on deploy, not verify. (with samuelsov of Koumbit)
* use module_enable() to enable civicrm, not drush_pm_enable(). seems to work better with provision 2.x (with omega8cc)
* we no longer fork the civicrm.settings.php.tpl file, using the standard one (this was forked a long time ago, when the civicrm.settings.php.tpl didn't have a variable for the "site key", but this has not been the case for some time now, so no need to fork).
* the civicrm cache clear function was removed (now in 'drush cc'), see blog post by Owen Barton, who also provided many upstream patches to improve the CiviCRM drush module). See also: #1556622: CiviCRM drush module breaks on non-civicrm platforms (sqlc, cron, etc).
Acknowledgements: thank you to Joe Murray (JMA consulting), Samuel Vanhove & Antoine Beaupré (Koumbit), Christopher Gervais (ergonlogic), Jamie McClelland (Progressive Technology Project), omega8cc, Owen Barton (CivicActions) and Tim Otten (CiviCRM) for their contributions.
Your contributions are important. If you would like to continue seeing this module improve, please consider participating in the issue queue (review bugs, provide support), contribute patches, hire the module maintainer for contract work or donate.