RELEASE NOTES:
SPECIAL THANKS:
- Changes to database schema
- API changes
- New features
- Bug fixes
WHAT'S NEW IN CIVICRM 4.7.25
- Core CiviCRM updates:
- Log in or register to post comments
RELEASE NOTES:
- Changes to database schema
- API changes
- New features
- Bug fixes
SPECIAL THANKS:
- Core CiviCRM updates:
- Updated upgrade message text...
Compatibility with PHP 5.3 will end in December 2017, and compatibility with PHP 5.4 will end in March 2018. These changes follow a number of discussions and a multi-year deprecation process. The current recommended version is PHP 5.6.
Discussion
According to php.net, PHP v5.5.x became "end of life" in July 2016. This means that the official publishers of PHP no longer support v5.5.x -- if there are security issues in the PHP runtime, the PHP project won't provide advisories or fixes. They recommend that all PHP users upgrade. (That's just the security side of the equation -- upgrading to a newer PHP also brings access to better libraries and design-patterns.)
But... for small organizations using CiviCRM, upgrading their servers to a newer version of PHP would be an expense. So CiviCRM has continued to support PHP 5.5 (declining to...
Read moreThe 4.7.24 release is scheduled for the first Wednesday of September. Ordinarily, there would be an announcement about the release-candidate (RC) in mid-August, but we're doing something a bit different this time around -- extending the RC to a full month, which mean the RC is available now at http://download.civicrm.org/latest. Testing out the RC is a great way to ensure that your systems will continue to work in the next release. Let me talk about how this change helps.
The Background
Quality-control for a new release is a team sport. It relies on reporters and developers performing thoughtful analysis when they identify a problem or improvement. It relies on developers writing code which anticipates errors, improves test-coverage, and follows recognizable conventions. It relies on infrastructure running automated tests. It relies on reviewers understanding the problem-domain and questioning assumptions. It relies...
Read more- 4 comments
- Log in or register to post comments
RELEASE NOTES:
- Changes to database schema
- API changes
- Configuration changes
- Fixes for installation/upgrade process to a previous version
- New features
- Bug fixes
SPECIAL THANKS:
This release has fixes for some issues reported in the previous 4.7.21 release. We recommend upgrading to this latest version.
Complete list of issues fixed in this release is available from here.
Bugs fixed:
Core CiviCRM
-
CRM-20561 Load Net_SMTP, Auth_SASL, Net_Socket via Composer (10622)
This resolves an SMTP authentication issue by updating a patch for compatibility with the a newer release of
Net_SMTP. -
CRM-20829 Install requirements fail because of port string (10626)
This fixes a bug where...
Please note that release 4.7.21 and 4.6.29 are security releases. Please see below links to the security advisories:
- CIVI-SA-2017-01 Pingback URL not encrypted
- CIVI-SA-2017-02 Privilage escalation via leaked key
- CIVI-SA-2017-03 Cross site scripting in the recently viewed block
- CIVI-SA-2017-04 Incorrect escaping for "On Behalf Of" block
- ...
RELEASE NOTES:
SPECIAL THANKS:
WHAT'S NEW IN CIVICRM 4.7.20
- Core CiviCRM updates:
RELEASE NOTES:
SPECIAL THANKS:
WHAT'S NEW IN CIVICRM 4.7.19
- Core CiviCRM updates:
A new option allows for generated PDFs and other document files to be automatically attached to their corresponding activities, saving you a few clicks.
- CiviCase...
- 3 comments
- Log in or register to post comments
CiviCRM Entity 2.0-beta7 has been released.
Pick it up now at the Drupal.org Project Page
Changes since beta6:
Add Rules action Assign Contact to Group
Add Rules action Remove Contact from Group
Add Integration for IM entity
Add Integration for Website entity
Add integration for Contribution Recur
Add Rules event for CiviCRM Price Set Field 'After Successful CC Transaction'
CiviCRM Price Set Field , improved support for price fields with multiple checkboxes
Fix issues with CiviCRM Core Contribution Recur Views integration
Enable CiviCRM Entity Reference field on parent entity 'add', Inline Entity Form Single widget, for Contacts...
