CiviCRM 4.7.23 release

Veröffentlicht
2017-08-03 10:18
Written by
jamienovick - member of the CiviCRM community - view blog guidelines
CiviCRM August release is here: CiviCRM v. 4.7.23 is released!
 
 

RELEASE NOTES:

Big thanks to Andrew Hunt from AGH Strategies for putting up together release notes for this version. 
The release notes for 4.7.23 can be accessed  here
 
Please note this version includes:
 
  1. Changes to database schema 
  2. API changes 
  3. Configuration changes 
  4. Fixes for installation/upgrade process to a previous version 
  5. New features 
  6. Bug fixes
 
 

SPECIAL THANKS:

 
Complete list of 4.7 contributors (it's a huge team!) can be found here.
 
 

WHAT'S NEW IN CIVICRM 4.7.23 

 

  •  Core CiviCRM updates:
  1. Improve handling of overdue activities More details. 
  2. Enable Farsi (fa_IR), Serbian (sr_RS), Ukrainian (uk_UA) in the languages option group so that we can install in those languages More details.
  3. Import, add 'Primary' as an address location More details
  4. Add filter - activity date and status on search criteria of activity listing More details. 
 
  •  CiviCase
  1. Allowed statuses per case-type More details. 
  2. Case multi/single client settings More details.
 
  • CiviContribute 
  1. Use civicontribute permission for contribution recur.cancel More details. 
  2. Include human readable contribution's custom field label in token widget for Thankyou letter More details.
  3. Add in password type field availability and apply to payment processor fields More details. 

 

  • CiviMember

Add submit credit card membership link on membership form More details.

 

  • Drupal integration 

Support Drupal aliases for event links in Views More details. 

 

In addition to this list, this release includes over 50 bug fixes and improvements. 
 
 
 

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