Published
Thursday, March 9, 2017 - 07:03
Written by
CiviCRM v. 4.7.17 and 4.6.27 are now released! 

RELEASE NOTES:

Andrew Hunt from AGH Strategies did amazing job as usual putting up together release notes for this version. 
Please find release notes for 4.7.17 here
 
SPECIAL THANKS:
 
Complete list of 4.7 team can be found here. Thanks to everyone who made this happen!
 
WHAT'S NEW IN CIVICRM 4.7.17
 
  •  Core CiviCRM updates:
Using the API to search for activities involving a specific contact is simplified and standardized across the assignee, source, and target, plus the generic contact_id parameter. More details here.
The Extension.download API still defaults to downloading and installing an extension, but a new parameter install can be set to FALSE in order to download without installing. PR details are here
A new drag-and-drop interface allows for editing, nesting, and coloring tags for tag manager. Some details are here.
Added the opportunity to specify which tables to revert for a logged change. More details are here.
 
  •  CiviContribute

The civicrm_financial_trxn table now contains fields to store credit card type (e.g. Visa, MasterCard, etc.) and the last four digits of the card number, if available. The fields are not yet used by any functions. More details here

The Contribution Summary report now has an option to display the title of the corresponding financial transaction batch. Details

 
  •  CiviEvent

CiviCRM now says "Sorry" when you attempt to register for an event where registration is closed. Task details

  •  CiviMail 

If you fail to set a domain in the Mail Accounts and send a message through CiviMail, a log message will note the situation. More details

  •  Backdrop integration 

CiviCRM for Backdrop now has a default layout for administration pages. PR details: here and here.

NEW INSTALLATIONS
 
If you are installing CiviCRM 4.7 from scratch, please use the corresponding automated installer instructions:
 

 

Authorize.net users:: Prior to 4.7, CiviCRM forced Authorize.net to send out receipt emails regardless of Authorize.net configuration. From 4.7 onwards this will not happen and you should log into your Authorize.net interface and configure whether you want Authorize.net 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.

UPGRADING TO 4.7

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
randomness