This month’s version of CiviCRM comes packed with delicious goo. Speaking generally, everything now works a little bit better. To find out the particulars, read on…
Big thanks to Andrew Hunt from AGH Strategies for putting up together release notes for this version.
The release notes for 4.7.20 can be accessed here
Complete list of 4.7 contributors can be found here
WHAT'S NEW IN CIVICRM 4.7.20
You can now search for contacts and add a Relationship to an Individual directly from those search results.
Administrators can now designate the status for activities created by inbound emails to accounts. Each account may have a different activity status.
When sending an email to a contact, you can set that email as belonging to a campaign, making it easier to keep track of campaign activities.
Contribution pages automatically contain the email address field. This gives site admins more control: in the past, the email address would appear ahead of any profiles. Now, if the field is in one of the profiles included on the page, it in the profile. Otherwise, it appears before the profiles.
Tracking the timings of mailings from users in different timezones can be problematic. Now, the database schema for new installations is altered to record the Unix timestamp for the times when CiviMail messages are created, scheduled, sent, and cancelled, so that timings can be recorded consistently.
Views can now filter contacts by the name of an individual's current employer.
If an import file has two rows with the same value for External Identifier, the affected rows are now skipped. This fixes the previous behavior which would present a fatal error interrupting the whole import process.
You can now have a title field with up to 225 characters on civicrm_batch table. This resolves a bug where the system threw a fatal error when the batch name was more than 64 characters.
Forwarded reply messages now have the appropriate headers to indicate that the server is resending a message from another sender.
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.