Commit | Line | Data |
---|---|---|
dd4b88ad AH |
1 | # Release Notes |
2 | ||
3 | These release notes are manually compiled from pull requests and Jira issues | |
4 | starting with CiviCRM 4.7.14. | |
5 | ||
6 | ## CiviCRM 4.7.14 | |
7 | ||
8 | Released December 2016 | |
9 | ||
65bccb4d AH |
10 | ### Credits |
11 | ||
12 | This release was developed by the following code authors: | |
13 | ||
14 | AGH Strategies - Andrew Hunt; Australian Greens - Seamus Lee; CiviCRM - Coleman Watts, Jitendra Purohit, Monish Deb, Tim Otten, and Yashodha Chaku; CiviDesk - Nicolas Ganivet; CiviFirst - John Kirk; Coop SymbioTIC - Samuel Vanhove; Francesc Bassas i Bullich; Fuzion - Chris Burgess and Eileen McNaughton; Ginkgo Street Labs - Tobias Lounsbury; JMA Consulting - Edzel Lopez and Pradeep Nayak; Lighthouse Consulting and Design - Brian Shaughnessy; Progressive Technology Project - Jamie McClelland; Spry Digital - Ellen Hendricks; Systopia - Björn Endres; Third Sector Design - Michael McAndrew; Thomas Schüttler | |
15 | ||
16 | Most authors also reviewed code for this release; in addition, the following reviewers contributed their comments: | |
17 | ||
18 | Artem Goncharenko; Coop SymbioTIC - Mathieu Lutfy; Dave Greenberg; Ginkgo Street Labs - Frank Gómez; JMA Consulting - Joe Murray; Korlon - Stuart Gaston; Mattias Michaux; Semper IT - Karin Gerritsen | |
19 | ||
dd4b88ad AH |
20 | ### Features |
21 | ||
22 | #### Core CiviCRM | |
23 | ||
24 | - **CRM_Utils_Check - Suggest using `[cms.root]`, etal | |
25 | ([8466](https://github.com/civicrm/civicrm-core/pull/8466))** | |
26 | ||
27 | Add a system check to see if directories and resource URLs are using the new | |
28 | path tokens—and report a message if not. | |
29 | ||
30 | - **[CRM-19533](https://issues.civicrm.org/jira/browse/CRM-19533) System check | |
31 | to see if important folders are writable | |
32 | ([9285](https://github.com/civicrm/civicrm-core/pull/9285))** | |
33 | ||
34 | If CiviCRM can’t write to certain important folders, a system check message | |
35 | should appear. | |
36 | ||
37 | - **[CRM-19463](https://issues.civicrm.org/jira/browse/CRM-19463) Get | |
38 | E2E_AllTests working on php7 | |
39 | ([9268](https://github.com/civicrm/civicrm-core/pull/9268))** | |
40 | ||
41 | Responses from SOAP requests to the API should be encoded properly to be | |
42 | compatible with PHP 7 | |
43 | ||
44 | - **[CRM-19494](https://issues.civicrm.org/jira/browse/CRM-19494) Refactoring of | |
45 | permission code ([9246](https://github.com/civicrm/civicrm-core/pull/9246))** | |
46 | ||
47 | Improve performance of contact view/edit permissions | |
48 | ||
49 | #### CiviCase | |
50 | ||
51 | - **[CRM-19552](https://issues.civicrm.org/jira/browse/CRM-19552) Case API may | |
52 | throw SQL errors when case_id not provided | |
53 | ([9308](https://github.com/civicrm/civicrm-core/pull/9308))** | |
54 | ||
55 | The Case.update API will accept the `id` parameter as case ID if `case_id` is | |
56 | missing. | |
57 | ||
58 | #### Helper Scripts | |
59 | ||
60 | - **bin/givi - Add backdrop support | |
61 | ([8944](https://github.com/civicrm/civicrm-core/pull/8944))** | |
62 | ||
63 | Support Backdrop in the givi script. | |
64 | ||
65 | ### Bugs | |
66 | ||
67 | #### Core CiviCRM | |
68 | ||
69 | - **[CRM-19472](https://issues.civicrm.org/jira/browse/CRM-19472) Export headers | |
70 | for relationships are in machine name format | |
71 | ([9187](https://github.com/civicrm/civicrm-core/pull/9187))** | |
72 | ||
73 | Fixed problem where relationship type labels were not displaying correctly in | |
74 | export files | |
75 | ||
76 | - **[CRM-19380](https://issues.civicrm.org/jira/browse/CRM-19380) Allow for | |
77 | multiple from email addresses but only one per domain | |
78 | ([9066](https://github.com/civicrm/civicrm-core/pull/9066))** | |
79 | ||
80 | - **[CRM-19122](https://issues.civicrm.org/jira/browse/CRM-19122) Group | |
81 | Organization & parent default code should be the same | |
82 | ([8751](https://github.com/civicrm/civicrm-core/pull/8751))** | |
83 | ||
84 | In a multisite instance of CiviCRM, you should be able to set the group | |
85 | organization for smart groups as well as static groups. | |
86 | ||
87 | - **[CRM-19471](https://issues.civicrm.org/jira/browse/CRM-19471) Custom | |
88 | relationships for custom contact types not available during export | |
89 | ([9259](https://github.com/civicrm/civicrm-core/pull/9259))** | |
90 | ||
91 | Fixed problem where related contacts, related via relationship types specific | |
92 | to contact subtypes, were not available in the export screen. | |
93 | ||
94 | - **[CRM-19079](https://issues.civicrm.org/jira/browse/CRM-19079) Profile edit | |
95 | permission checks bypass standard route in WP | |
96 | ([8707](https://github.com/civicrm/civicrm-core/pull/8707))** | |
97 | ||
98 | Fixed problem in WordPress where the normal permission checks and hooks were | |
99 | bypassed on profiles in edit mode. | |
100 | ||
101 | - **[CRM-19490](https://issues.civicrm.org/jira/browse/CRM-19490) Add a “short | |
102 | date” format setting to allow for localized display of dates in profile fields | |
103 | ([9253](https://github.com/civicrm/civicrm-core/pull/9253))** | |
104 | ||
105 | When date fields appear in profiles on the confirmation page of contribution | |
106 | pages, they should show the date in the localized format. | |
107 | ||
108 | - **[CRM-17616](https://issues.civicrm.org/jira/browse/CRM-17616) Moving to an | |
109 | arbitrary search page result could lead to incomplete results | |
110 | ([9266](https://github.com/civicrm/civicrm-core/pull/9266))** | |
111 | ||
112 | When viewing hundreds of rows in search results, a cache is kept of the next | |
113 | several hundred rows; this cache should be filled and sized according to the | |
114 | page being viewed. | |
115 | ||
116 | - **Minor comment fix | |
117 | ([9269](https://github.com/civicrm/civicrm-core/pull/9269))** | |
118 | ||
119 | - **[CRM-19511](https://issues.civicrm.org/jira/browse/CRM-19511) Disabled | |
120 | fields still visible in "Import Multi-value Custom Data" | |
121 | ([9274](https://github.com/civicrm/civicrm-core/pull/9274))** | |
122 | ||
123 | When importing multi-value custom data, disabled custom fields should not be | |
124 | available for import. | |
125 | ||
126 | - **[CRM-19512](https://issues.civicrm.org/jira/browse/CRM-19512) Ensure that | |
127 | language param is always passed in for navigation script url | |
128 | ([9280](https://github.com/civicrm/civicrm-core/pull/9280))** | |
129 | ||
130 | When getting a locale, there should always be a result; `en_US` is the | |
131 | fallback. | |
132 | ||
133 | - **[CRM-19528](https://issues.civicrm.org/jira/browse/CRM-19528) | |
134 | Internationalise "Select Code" on contributions page widget tab | |
135 | ([9282](https://github.com/civicrm/civicrm-core/pull/9282))** | |
136 | ||
137 | The US English words “select code” on the contribution page widget should be | |
138 | translated. | |
139 | ||
140 | - **[CRM-19313](https://issues.civicrm.org/jira/browse/CRM-19313) Can't assign | |
141 | custom group to relationships with two contact subtypes involved | |
142 | ([9287](https://github.com/civicrm/civicrm-core/pull/9287) and | |
143 | [9328](https://github.com/civicrm/civicrm-core/pull/9328))** | |
144 | ||
145 | - **[CRM-19529](https://issues.civicrm.org/jira/browse/CRM-19529) | |
146 | Upcoming/Recent Case Activities results into "Network Error" in PHP 7 | |
147 | ([9283](https://github.com/civicrm/civicrm-core/pull/9283))** | |
148 | ||
149 | - **[CRM-18953](https://issues.civicrm.org/jira/browse/CRM-18953) Better cleanup | |
150 | of news widget markup | |
151 | ([9289](https://github.com/civicrm/civicrm-core/pull/9289))** | |
152 | ||
153 | Formatting tags and style should be stripped out of news items in the CiviCRM | |
154 | News dashlet | |
155 | ||
156 | - **[CRM-19513](https://issues.civicrm.org/jira/browse/CRM-19513) Saved search | |
157 | is incorrectly using IN rather than BETWEEN for custom fields for civicrm | |
158 | group cache ([9284](https://github.com/civicrm/civicrm-core/pull/9284))** | |
159 | ||
160 | A smart group based upon a search by range should include the whole range, not | |
161 | just the extremes. | |
162 | ||
163 | - **[CRM-19540](https://issues.civicrm.org/jira/browse/CRM-19540) UFGroup API | |
164 | does not respect name parameter | |
165 | ([9295](https://github.com/civicrm/civicrm-core/pull/9295))** | |
166 | ||
167 | Creating a profile through the API should allow you to specify a machine name | |
168 | rather than have it generated from the title | |
169 | ||
170 | - **[CRM-19541](https://issues.civicrm.org/jira/browse/CRM-19541) Custom Date | |
171 | Range saved search doesn't sets default values to the input | |
172 | ([9297](https://github.com/civicrm/civicrm-core/pull/9297))** | |
173 | ||
174 | After creating a smart group, the values displayed in the search form should | |
175 | reflect the smart group criteria. Until this fix, range criteria for a date | |
176 | field weren’t filled. | |
177 | ||
178 | - **[CRM-19559](https://issues.civicrm.org/jira/browse/CRM-19559) Handling for | |
179 | postal_code missing in CRM_Contact_BAO_Contact_Utils::contactDetails() | |
180 | ([9313](https://github.com/civicrm/civicrm-core/pull/9313))** | |
181 | ||
182 | Fixed problem when Postal Code is enabled in Settings :: Search Preferences :: | |
183 | Autocomplete Contact Search it was not retrieved in Contribute, Activity, | |
184 | Member and Event batch forms. | |
185 | ||
186 | - **[CRM-19543](https://issues.civicrm.org/jira/browse/CRM-19543) api fields set | |
187 | to '0' are not passed to _civicrm_api3_api_match_pseudoconstant for validation | |
188 | ([9320](https://github.com/civicrm/civicrm-core/pull/9320))** | |
189 | ||
190 | An integer field with the value “0” should not bypass validation | |
191 | ||
192 | - **[CRM-19563](https://issues.civicrm.org/jira/browse/CRM-19563) Mappings from | |
193 | search builder saved with mapping_type_id = NULL | |
194 | ([9316](https://github.com/civicrm/civicrm-core/pull/9316))** | |
195 | ||
196 | When creating a smart group from search builder, the mapping type should be | |
197 | set as “Search Builder”, and the mapping should not appear in the | |
198 | import/export mappings list. | |
199 | ||
200 | - **[CRM-19278](https://issues.civicrm.org/jira/browse/CRM-19278) Google | |
201 | Geocoding - Errors are ignored | |
202 | ([8956](https://github.com/civicrm/civicrm-core/pull/8956))** | |
203 | ||
204 | If Google returns an error while geocoding (other than not finding any results | |
205 | for the address), the error message should be logged. | |
206 | ||
207 | #### Accounting | |
208 | ||
209 | - **[CRM-19485](https://issues.civicrm.org/jira/browse/CRM-19485) Selector issue | |
210 | on Batch trxn assignment page | |
211 | ([9211](https://github.com/civicrm/civicrm-core/pull/9211))** | |
212 | ||
213 | When the financial batch assignment list refreshes, if the select-all checkbox | |
214 | is checked, all transactions should be checked. | |
215 | ||
216 | #### CiviCampaign | |
217 | ||
218 | - **[CRM-19536](https://issues.civicrm.org/jira/browse/CRM-19536) Type is not | |
219 | defined for field campaign_id in CRM_Report_Form->whereClause() | |
220 | ([9288](https://github.com/civicrm/civicrm-core/pull/9288))** | |
221 | ||
222 | Reports should treat `campaign_id` as an integer. | |
223 | ||
224 | #### CiviCase | |
225 | ||
226 | - **Select correct activity if more than one in upcoming or recent period | |
227 | ([9011](https://github.com/civicrm/civicrm-core/pull/9011))** | |
228 | ||
229 | The upcoming case activity displayed with a case should be the one coming up | |
230 | soonest within the next 14 days. Similarly, the recent case activity should | |
231 | be the most recent one within the past 14 days. | |
232 | ||
233 | - **Remove phony fk info from case api | |
234 | ([9262](https://github.com/civicrm/civicrm-core/pull/9262))** | |
235 | ||
236 | No longer specify foreign key APIs for contact and activity IDs in the case | |
237 | API spec | |
238 | ||
239 | - **[CRM-19506](https://issues.civicrm.org/jira/browse/CRM-19506) API Regression - | |
240 | conflicting uniquename in CaseContact DAO | |
241 | ([9318](https://github.com/civicrm/civicrm-core/pull/9318))** | |
242 | ||
243 | Record the contact ID in `civicrm_case` table as `contact_id` rather than | |
244 | `case_contact_id` | |
245 | ||
246 | - **Remove accidental debug statement | |
247 | ([9292](https://github.com/civicrm/civicrm-core/pull/9292))** | |
248 | ||
249 | #### CiviContribute | |
250 | ||
251 | - **[CRM-19539](https://issues.civicrm.org/jira/browse/CRM-19539) Bug prevents | |
252 | error message to be shown on pledge contribution import | |
253 | ([9302](https://github.com/civicrm/civicrm-core/pull/9302))** | |
254 | ||
255 | Importing pledges with problems should generate meaningful error messages | |
256 | ||
257 | - **[CRM-3795](https://issues.civicrm.org/jira/browse/CRM-3795) 'Bcc' fields on | |
258 | the contribution pages behave like 'Cc' | |
259 | ([9312](https://github.com/civicrm/civicrm-core/pull/9312))** | |
260 | ||
261 | This provides some commentary on the fix, which was included in 4.7.11 | |
262 | ||
263 | - **[CRM-19561](https://issues.civicrm.org/jira/browse/CRM-19561) When using Pay | |
264 | Later with a Price Set, Contribution Details in Email Receipt are Blank | |
265 | ([9321](https://github.com/civicrm/civicrm-core/pull/9321))** | |
266 | ||
267 | Fixed problem on online contributions where pay-later contributions with price | |
268 | sets had no contribution details. | |
269 | ||
270 | #### CiviEvent | |
271 | ||
272 | - **[CRM-19535](https://issues.civicrm.org/jira/browse/CRM-19535) Workflow that | |
273 | inadvertently cancels all registrants all enabled events | |
274 | ([9291](https://github.com/civicrm/civicrm-core/pull/9291))** | |
275 | ||
276 | Fixed problem where bulk actions on participants of a disabled event instead | |
277 | take effect on participants of all enabled events. | |
278 | ||
279 | - **[CRM-19550](https://issues.civicrm.org/jira/browse/CRM-19550) Standalone | |
280 | participant/add form does not properly check for duplicates | |
281 | ([9303](https://github.com/civicrm/civicrm-core/pull/9303))** | |
282 | ||
283 | When registering a contact for an event from the backend, the form should | |
284 | prevent the registration if that contact has already been registered. | |
285 | ||
286 | - **[CRM-18594](https://issues.civicrm.org/jira/browse/CRM-18594) Creating event | |
287 | templates throws an 'Invalid Entity Filter' exception | |
288 | ([8424](https://github.com/civicrm/civicrm-core/pull/8424))** | |
289 | ||
290 | Test that events can have text as the event type. | |
291 | ||
292 | #### CiviGrant | |
293 | ||
294 | - **[CRM-19543](https://issues.civicrm.org/jira/browse/CRM-19543) contact_id | |
295 | should be marked as required on grant api | |
296 | ([9296](https://github.com/civicrm/civicrm-core/pull/9296))** | |
297 | ||
298 | The Grant API spec should indicate that `contact_id`, `status_id`, and | |
299 | `amount_total` are required. |