Published
2018-04-09 06:57
Greetings, CiviCRM community!
The April release of CiviCRM is now ready to download. This is a normal monthly release, but the version numbering has changed to 5.0.0.
RELEASE NOTES:
Big thanks to Andrew Hunt from AGH Strategies for putting up together release notes for this version.
The release notes for 5.0.0 can be accessed here.
SPECIAL THANKS:
Complete list of 5.0 contributors (it's a huge team!) can be found here. Thanks to everyone involved!
This version includes:
- API changes
- Configuration changes
- Fixes for installation and upgrade issues
- New features
- Bug fixes
WHAT'S NEW IN CIVICRM 5.0.0:
The focus for this month's release has been on bug fixes but there are a few improvements notably
- It's now possible to set an end date for a membership override
- It's now possible to batch update cases
- new send SMS permission
And for developers
- Guzzle now ships with core
- Most entities support custom fields at the api level now.
- new redirect hook added
-
Core CiviCRM updates:
More entities now support custom fields.
This change moves us closer to the goal of being able to define custom data on 'any entity'. It takes us from a limited list of entities that work to a longer list of ones that still don't work. More details here.
Added auto-scroll-up functionality between steps in a wizard-driven workflow. More details here.
Minimum PHP version changed to 5.5.
This change bumps up the minimum version to follow the schedule laid out in https://civicrm.org/blog/totten/end-of-zombies-php-53-and-54. More details available here.
Fixed template structure issues. Read more here.
CKEditor Advanced Options - Added better validation of options.
In the "Advanced Options" of the CKEditor Configurator, API options can be selected. This tweaks the UI to prevent the same option from being selected twice, which would not make sense. Read more here.
Improved changelog search panel UI. More details here.
- CiviCase
Added batch update via profile to cases.
This change adds a "Update Multiple Cases" option to search tasks and allows you to batch update multiple cases in the same way as other entities. More details here.
- CiviContribute
Replaced payment details block with editable payment list on 'Edit Contribution' form (11748) (preliminary work). More details here.
Fixed transaction template.
Updated transaction template to make them match other templates for consistency. More details here.
- CiviMail
Implemented Send SMS permission.
This change adds a permission to Send SMS. More specifically, it: Adds the Send SMS permission to CRM_Core_Permissions::getCorePermissions, ensures that all navigation menu entries ('Find SMS' and 'New SMS') respect the new permission, Ensures that all paths (civicrm/sms/send, civicrm/activity/sms/add, civicrm/mailing) respect the new permission, Only show 'Outbound SMS' action from the action menu on the contact screen to users with the send SMS permission, and only shows 'SMS - schedule/send' from the advanced search actions to users with the send SMS permission. More details.
Added 'huge' class to html textarea to match plaintext textarea
This change makes it so that the HTML Format input and the Plain Text Format input On the Message Template editor screen match. More details.
Enhancements to "FROM email addresses" (continues previous work)
Help text now adjusts according to whether the logged-in user's email is allowed as a From address option. More details here.
-
CiviMember
Allow overriding membership status temporarily until specific date (11722 and 11622)
When overriding a membership status this change provides extra options to allow a temporary status override.
Instead of having a checkbox called (Override Status?) in membership add/edit/renew form, it is replaced with a select box that allow the user to choose one of three options: No, Override Permanently or Override until selected date.
If the first option is selected, then the membership will behave as if the old (Override Status?) is unchecked, which means that the membership is subject to membership status rules.
If the 2nd option is selected, then the membership will behave as if the old (Override Status?) is checked, which mean that the membership status is overridden and is not subject to the membership statues rules.
If the 3rd option is selected, then a new field will appear allowing the user to choose a date, in this status, the membership will behave similar to option 2, but when today date is equal or less than the selected date, then the "Update Membership Statuses" scheduled job will automatically convert its status back to No, which means that the membership status is overridden temporarily only for the selected date and after that it will revert back and be subject to membership status rules.
Please refer to the release notes for complete list of changes!
NEW INSTALLATIONS
If you are installing CiviCRM 5.0 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 5.0
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 the upgrade steps to get yourself up and running with the latest version.
Filed under
