Thursday, March 8, 2018 - 10:22
Written by
Greetings, CiviCRM community!
We are glad to announce the March CiviCRM release is now ready to download. 


Big thanks to Andrew Hunt from AGH Strategies for putting up together release notes for this version. 
The release notes for 4.7.31 can be accessed here.


Complete list of 4.7 contributors (it's a huge team!) can be found here. Thanks to everyone involved!
This version includes:
  1. Database schema changes
  2. API changes
  3. Configuration changes
  4. Fixes for installation and upgrade issues
  5. New features 
  6. Bug fixes



  •  Core CiviCRM updates:

A variety of changes have been made to the email addresses available as the "From" address for system messages. The Organization Address and Contact Info form no longer has a field for selecting the From email address--this is now editable by choosing a default on the From Email Addresses page.
The PDF letter task now allows selecting the from email address.

You can also now choose whether to add the logged-in contact's email address to the list of from email addresses. If users' addresses are from other domains, they can have deliverability problems if the domain uses SPF or DMARC. More details.

Now activity notifications will not send from the source contact's email address if the site is not set to allow emails from the logged-in contact. More details.
Profiles can now be given a public title to display on frontend forms that is distinct from the name for internal purposes. More details
The Multibyte String PHP function support is now a requirement for installing CiviCRM. More details.
File fields are no longer suppressed when batch editing data using a profile, and if the field currently has a file, the form displays its name. More details.  
The profile quick editor now allows setting the cancel and submit button text. More details.
Auto-complete fields in a profile can now be edited when batch editing data. More details.
  • CiviCampaign

The Walk / Phone List Report now can be sorted by street name, street number, and whether the street number is odd or even. More details.

  • CiviCase

The Case Dashboard, My Cases dashlet, and All Cases dashlet now use DataTables to display results. This allows easy sorting and filtering of results among other improvements. More details.

When changing the status of a case, you now have the option to update the status of all linked cases. More details.

Contacts selected from search results can now be added in bulk with a selected case role to a selected case. More details.

  • CiviContribute
The iATS payment processor is now included in core CiviCRM. More details
A payment processor's configuration is now checked as part of the validation of the payment processor configuration form. More details
The list of available payment processors is now fetched once rather than several times per contribution page load. More details.
When viewing a contribution or membership with a recurring contribution, there is now a link to view the recurring contribution. More details.
  • CiviMail
A new option on the Mailing Opened Report toggles displaying all open events and all recipients who have opened the message. More details
  • CiviMember

Members with autorenewal enabled can now edit the recurring contribution to change the amount or number of installments. They will be warned that the recurring contribution is linked to a membership. More details.

Icons for membership autorenewal now use the Font Awesome library, and a new icon indicates memberships that were set to autorenew but have a canceled recurring contribution. More details.
A few Drupal & WordPress integration improvements are also included in the release.
Please refer to the release notes for complete list of changes! 


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