Friday, May 5, 2017 - 08:50
Written by
Another month, another version release of CiviCRM! Let’s take a look at the latest improvements.


Thanks to Andrew Hunt from AGH Strategies, we have release notes all put together in one place for you here


Complete list of 4.7 contributors (it's a huge team!) can be found here. Thanks to everyone who made this happen!



  •  Core CiviCRM updates:

A new option allows for generated PDFs and other document files to be automatically attached to their corresponding activities, saving you a few clicks.

  •  CiviCase

Case subjects are now editable, allowing you to rename cases – or just fix your typos

Cases can now be merged or restored from trash using the API

  • CiviContribute
When processing a credit card from the front or back end, the last four digits of the card number along with the card type are now stored on the financial transaction.

Two new columns and filters on the Bookkeeping Report: contribution ID and financial account owner. 

  • CiviEvent

This change increases the coverage of hook_civicrm_selectWhereClause to include selecting events.


  •  CiviMail

Mailing reports now can display the subject line in addition to the internal mailing name. 

  • CiviMember

Auto-renew options on contribution pages now appear or freeze according to the selected membership type's settings for auto-renew.

And as always, we’ve made dozens of small improvements and bug fixes, to give you a smoother experience overall.



If you are installing CiviCRM 4.7 from scratch, please use the corresponding automated installer instructions: users:: Prior to 4.7, CiviCRM forced to send out receipt emails regardless of configuration. From 4.7 onwards this will not happen and you should log into your interface and configure whether you want to send out receipts (in addition to those sent by CiviCRM).

Lybunt report users:: Some fields that were previously mandatory on Lybunt are now optional. On new reports they are on by default but you might need to check the fields you want are selected for existing reports.



If your site is highly customized with special code or theming for CiviCRM you will want to upgrade a test copy first and test your customizations. For everyone else, follow these simple steps to get yourself up and running with 4.7.
Filed under


Just a general detail that's a bit unusual and didn't make it into the announcement -- this release is the first one signed with a new GPG key. The new GPG key uses stronger crypto (4096-bit RSA vs 1024-bit DSA).

They key is identified as 7A1E75CB (6181 9CB6 62DA 5FFF 7918  3EF8 3801 D1B0 7A1E 75CB). You can find it on the public keyserver (hkps:// or .

Is anyone able to give an update as to how far progressed we are with achieving compatability/support for running on PHP7?  This info would be much appreciated.

There are a number of live 7.0 sites & we consider it to be stable. Php 7.1 still seems to have a couple of quirks & less sites (but still 86)