1. Home
  2. Blogs
  3. Blogs

CiviCRM 5.16.0 release

Published
2019-08-08 03:37
Written by
dev-team
CiviCRM version 5.16.0 is now out and ready to download.
 

RELEASE NOTES:

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

SPECIAL THANKS:

The complete list of 5.16.0 contributors (it's a huge team!) can be found here. Thanks to everyone for making this release happen!
 
 
This version includes:
 
  1. API changes
  2. New features
  3. Configuration changes
  4. Fixes to bugs
  5. Fix problems installing or upgrading to a previous version

 

WHAT'S NEW IN CIVICRM 5.16:

  •  Core CiviCRM updates:

Allow extensions to define CSS themes / Add a configuration setting for when to load custom CSS  (CRM-18792 / dev/core#378: 14551 and 12929)
Adds an option to the "Display Preferences" settings form to allow users to more finely tune when CiviCRM's css is loaded. On WordPress and Joomla two options are available the "Backend Theme" and "Frontend Theme", on Drupal and Backdrop, the administration screen "Display Preferences" presents a singular "Theme" option.
 
Better support for hookable menubar colors (14944)

More colors in the menu, including the base color, highlight color, and text color, can be modified with hooks.

 
Add a configuration setting for when to load custom CSS (initial work for dev/core#378: 14876)

A new function, CRM_Utils_System::isFrontEndPage(), indicates whether a page is considered "front-end".

Menubar - Improve flexibility & remove hardcoded values (14924)

The menu no longer relies on hardcoded pixel dimensions to determine mobile appearance, and it replaces references to the ID selector crm-container with the class selector of the same name (which is used more broadly).

This also resolves dev/core#1127.

Buttons inconsistencies (dev/core#347: 14136 and 14509) Adds support for "button" elements in CiviCRM ajax popup forms in addition to the input type=button/submit and the "a class=button". This is a first step towards cleaning up button handling from a theming perspective. Adds buttons to 'Cleanup caches and update paths' in standard way

 

  • CiviEvent

URL support for some params in event search (14477)

Adds Event Search URL support for the params: sort_name, participant_status_id, participant_register_date_low, participant_register_date_high, and participant_register_date_relative. Date format is a string of numbers YmdHIS (ex: 20180101).

Add checklist-model angular module (14634)

Adds the angular checklist-model library required by form builder.

 

 

  • CiviContribute 

Reduce deadlocks on inserting custom data by only using 'ON DUPLICATE' when it is not a new row (14605)

Reduce deadlocks when processing contributions with custom data. This specifically makes the custom data insert SQL more efficient.

Fix url support for receive_date_high & receive_date_low (14594 and 14611)

As a part of a general standardization movement, adds Url support on the contribution search form for the following fields: receive_date_high, receive_date_low, contribution_cancel_date_high, contribution_cancel_date_low and invoice_number=9. Deprecates and continues to support the start date being passed to contribution search as "start=2018-01-01".

 

This release also includes a number of bug fixes and other improvements, so please check the complete list of changes by following this link.

 

NEW INSTALLATIONS

If you are installing CiviCRM 5.16.0 from scratch, please use the corresponding automated installer instructions:
 
 
Filed under
Release announcements