| 1 | # CiviCRM 4.7.23 |
| 2 | |
| 3 | Released August 2, 2017 |
| 4 | |
| 5 | - **[Synopsis](#synopsis)** |
| 6 | - **[Features](#features)** |
| 7 | - **[Bugs resolved](#bugs)** |
| 8 | - **[Miscellany](#misc)** |
| 9 | - **[Credits](#credits)** |
| 10 | - **[Feedback](#feedback)** |
| 11 | |
| 12 | ## <a name="synopsis"></a>Synopsis |
| 13 | |
| 14 | | *Does this version...?* | | |
| 15 | |:--------------------------------------------------------------- |:-------:| |
| 16 | | Fix security vulnerabilities? | no | |
| 17 | | **Change the database schema?** | **yes** | |
| 18 | | **Alter the API?** | **yes** | |
| 19 | | **Require attention to configuration options?** | **yes** | |
| 20 | | **Fix problems installing or upgrading to a previous version?** | **yes** | |
| 21 | | **Introduce features?** | **yes** | |
| 22 | | **Fix bugs?** | **yes** | |
| 23 | |
| 24 | ## <a name="features"></a>Features |
| 25 | |
| 26 | ### Core CiviCRM |
| 27 | |
| 28 | - **[CRM-20830](https://issues.civicrm.org/jira/browse/CRM-20830) Improve |
| 29 | handling of overdue activities |
| 30 | ([10618](https://github.com/civicrm/civicrm-core/pull/10618))** |
| 31 | |
| 32 | Activity statuses can now be edited to denote whether activities with a given |
| 33 | status should be considered "complete" or not. This attribute is now the |
| 34 | basis for determining whether an activity is overdue. In addition to UI |
| 35 | indications of being overdue, the API can return this value for each activity. |
| 36 | |
| 37 | - **[CRM-20803](https://issues.civicrm.org/jira/browse/CRM-20803) Enable Farsi |
| 38 | (fa_IR), Serbian (sr_RS), Ukrainian (uk_UA) in the languages option group so |
| 39 | that we can install in those languages |
| 40 | ([10667](https://github.com/civicrm/civicrm-core/pull/10667))** |
| 41 | |
| 42 | These languages can now be used for installation of CiviCRM. |
| 43 | |
| 44 | - **[CRM-20759](https://issues.civicrm.org/jira/browse/CRM-20759) Import, add |
| 45 | 'Primary' as an address location |
| 46 | ([10738](https://github.com/civicrm/civicrm-core/pull/10738), |
| 47 | [10565](https://github.com/civicrm/civicrm-core/pull/10565), |
| 48 | [10594](https://github.com/civicrm/civicrm-core/pull/10594), |
| 49 | [10554](https://github.com/civicrm/civicrm-core/pull/10554), and |
| 50 | [10547](https://github.com/civicrm/civicrm-core/pull/10547))** |
| 51 | |
| 52 | Columns in imports can now import to fields in the matching contact's primary |
| 53 | address, regardless of location type. |
| 54 | |
| 55 | - **[CRM-20793](https://issues.civicrm.org/jira/browse/CRM-20793) Add filter - |
| 56 | activity date and status on search criteria of activity listing |
| 57 | ([10588](https://github.com/civicrm/civicrm-core/pull/10588))** |
| 58 | |
| 59 | The activity tab on a contact record now allows filtering by date and status |
| 60 | besides just activity type. In addition, a site-wide option toggles whether a |
| 61 | user's filters on one contact's activities persist as they visit other |
| 62 | contacts. |
| 63 | |
| 64 | - **[CRM-20847](https://issues.civicrm.org/jira/browse/CRM-20847) Support custom |
| 65 | api with composite primary keys |
| 66 | ([10599](https://github.com/civicrm/civicrm-core/pull/10599))** |
| 67 | |
| 68 | This change adds testing for custom APIs using the basic get function and |
| 69 | avoids automatically selecting the `id` field if there is no such field in the |
| 70 | spec. |
| 71 | |
| 72 | - **[CRM-20842](https://issues.civicrm.org/jira/browse/CRM-20842) Change api |
| 73 | explorer page title |
| 74 | ([10633](https://github.com/civicrm/civicrm-core/pull/10633))** |
| 75 | |
| 76 | The API Explorer now explicitly states it is demonstrating API v3. |
| 77 | |
| 78 | - **[CRM-20780](https://issues.civicrm.org/jira/browse/CRM-20780) Add settings |
| 79 | file option to define CMS_ROOT |
| 80 | ([10574](https://github.com/civicrm/civicrm-core/pull/10574))** |
| 81 | |
| 82 | The CiviCRM settings file can now explicitly set the path to the CMS root. |
| 83 | |
| 84 | - **[CRM-20169](https://issues.civicrm.org/jira/browse/CRM-20169) Add support |
| 85 | for alterReportVar hook in Activity Report |
| 86 | ([9886](https://github.com/civicrm/civicrm-core/pull/9886))** |
| 87 | |
| 88 | Extensions can now modify the SQL of the Activity Report. |
| 89 | |
| 90 | - **[CRM-20721](https://issues.civicrm.org/jira/browse/CRM-20721) Add parameter |
| 91 | to dateQueryBuilder fn to change date value to desired format |
| 92 | ([10497](https://github.com/civicrm/civicrm-core/pull/10497))** |
| 93 | |
| 94 | Queries on fields formatted in ways other than the typical MySQL date format |
| 95 | can now use the standard date query builder method in the contact BAO. |
| 96 | |
| 97 | - **[CRM-20600](https://issues.civicrm.org/jira/browse/CRM-20600) Expose |
| 98 | AngularJS screens to hooks |
| 99 | ([10644](https://github.com/civicrm/civicrm-core/pull/10644)) (follow-up |
| 100 | work)** |
| 101 | |
| 102 | A message now displays both before and after upgrade if a site's configuration |
| 103 | is likely to prevent successful asset-caching. |
| 104 | |
| 105 | - **[CRM-20673](https://issues.civicrm.org/jira/browse/CRM-20673) Tag and group |
| 106 | edit form: implement Select2 for tags |
| 107 | ([10634](https://github.com/civicrm/civicrm-core/pull/10634)) (completes |
| 108 | previous work)** |
| 109 | |
| 110 | Tags are now listed in the widget in the same order as they are displayed for |
| 111 | management. |
| 112 | |
| 113 | - **[CRM-20622](https://issues.civicrm.org/jira/browse/CRM-20622) contact edit: |
| 114 | tags and groups panel layout/styling |
| 115 | ([10429](https://github.com/civicrm/civicrm-core/pull/10429))** |
| 116 | |
| 117 | The tag and group editing interface now uses standard markup rather than |
| 118 | unique, outdated approaches. |
| 119 | |
| 120 | ### CiviCase |
| 121 | |
| 122 | - **[CRM-19778](https://issues.civicrm.org/jira/browse/CRM-19778) Allowed |
| 123 | statuses per case-type |
| 124 | ([10552](https://github.com/civicrm/civicrm-core/pull/10552))** |
| 125 | |
| 126 | The available options in the API for case status can now be filtered to those |
| 127 | appropriate for a given case type. |
| 128 | |
| 129 | - **[CRM-20794](https://issues.civicrm.org/jira/browse/CRM-20794) Colors for |
| 130 | case status ([10586](https://github.com/civicrm/civicrm-core/pull/10586)) |
| 131 | (preliminary work)** |
| 132 | |
| 133 | When editing case statuses, you may now select a color. However, case display |
| 134 | does not yet show the status colors. |
| 135 | |
| 136 | - **[CRM-20756](https://issues.civicrm.org/jira/browse/CRM-20756) Multi tab |
| 137 | structure ([10545](https://github.com/civicrm/civicrm-core/pull/10545)) |
| 138 | (preliminary work)** |
| 139 | |
| 140 | The AngularJS `ui.bootstrap` library is now included in CiviCRM. |
| 141 | |
| 142 | - **[CRM-20816](https://issues.civicrm.org/jira/browse/CRM-20816) Case |
| 143 | multi/single client settings |
| 144 | ([10609](https://github.com/civicrm/civicrm-core/pull/10609))** |
| 145 | |
| 146 | Settings for redacting activity emails, allowing multiple clients per case, |
| 147 | and the sort order of activity types can now be modified in an administrative |
| 148 | form rather than exclusively in XML files defining case types. |
| 149 | |
| 150 | ### CiviContribute |
| 151 | |
| 152 | - **[CRM-20778](https://issues.civicrm.org/jira/browse/CRM-20778) Use |
| 153 | civicontribute permission for contribution recur.cancel |
| 154 | ([10569](https://github.com/civicrm/civicrm-core/pull/10569))** |
| 155 | |
| 156 | The permissions to view, modify, cancel, and delete recurring contributions |
| 157 | now mirror the corresponding permissions needed for working with payments. |
| 158 | |
| 159 | - **[CRM-20682](https://issues.civicrm.org/jira/browse/CRM-20682) Include human |
| 160 | readable contribution's custom field label in token widget for Thankyou letter |
| 161 | ([10467](https://github.com/civicrm/civicrm-core/pull/10467))** |
| 162 | |
| 163 | Contribution custom field tokens are now listed among the available tokens in |
| 164 | the Thank-you Letter form. They had been processed, but there was no |
| 165 | indication that they were available. |
| 166 | |
| 167 | - **[CRM-20860](https://issues.civicrm.org/jira/browse/CRM-20860) Add in |
| 168 | password type field availability and apply to payment processor fields |
| 169 | ([10649](https://github.com/civicrm/civicrm-core/pull/10649))** |
| 170 | |
| 171 | Field metadata can now specify the HTML field type of `Password` which adds a |
| 172 | `HTML_QuickForm_password` field element. This is implemented on payment |
| 173 | processor settings fields. |
| 174 | |
| 175 | ### CiviMember |
| 176 | |
| 177 | - **[CRM-20901](https://issues.civicrm.org/jira/browse/CRM-20901) Add submit |
| 178 | credit card membership link on membership form |
| 179 | ([10689](https://github.com/civicrm/civicrm-core/pull/10689))** |
| 180 | |
| 181 | The backend add membership form now has a link to the backend credit card |
| 182 | membership form. |
| 183 | |
| 184 | ### Backdrop Integration |
| 185 | |
| 186 | - **Port of civicrm_engage to Backdrop |
| 187 | ([28](https://github.com/civicrm/civicrm-backdrop/pull/28))** |
| 188 | |
| 189 | ### Drupal Integration |
| 190 | |
| 191 | - **[CRM-20751](https://issues.civicrm.org/jira/browse/CRM-20751) Support Drupal |
| 192 | aliases for event links in Views |
| 193 | ([456](https://github.com/civicrm/civicrm-drupal/pull/456) and |
| 194 | [455](https://github.com/civicrm/civicrm-drupal/pull/455))** |
| 195 | |
| 196 | If a CiviCRM event has a Drupal alias set for it, views linking to the event |
| 197 | will now link to the alias rather than the CiviCRM URL. |
| 198 | |
| 199 | ## <a name="bugs"></a>Bugs resolved |
| 200 | |
| 201 | ### Core CiviCRM |
| 202 | |
| 203 | - **[CRM-20873](https://issues.civicrm.org/jira/browse/CRM-20873) CIVICRM-118 DB |
| 204 | Error: no such field / Unknown column 'civicrm_custom_group.is_public' breaks |
| 205 | CiviCRM database update process |
| 206 | ([10662](https://github.com/civicrm/civicrm-core/pull/10662))** |
| 207 | |
| 208 | This fixes a bug in upgrading from 4.7.18 or earlier to 4.7.19 or later. Code |
| 209 | used by the upgrade to load the available custom data for an entity relies |
| 210 | upon a field that is not made available until after the upgrade. |
| 211 | |
| 212 | - **[CRM-20849](https://issues.civicrm.org/jira/browse/CRM-20849) Multiple |
| 213 | extensions using the same autoloader prefix will overwrite previous |
| 214 | ([10637](https://github.com/civicrm/civicrm-core/pull/10637))** |
| 215 | |
| 216 | - **[CRM-20739](https://issues.civicrm.org/jira/browse/CRM-20739) contact import |
| 217 | doesn't add to group on fill if matching without ID |
| 218 | ([10507](https://github.com/civicrm/civicrm-core/pull/10507))** |
| 219 | |
| 220 | - **[CRM-20666](https://issues.civicrm.org/jira/browse/CRM-20666) enable |
| 221 | uploading of files to activities that are up to 255 characters in length |
| 222 | ([10449](https://github.com/civicrm/civicrm-core/pull/10449))** |
| 223 | |
| 224 | File names of activity uploads had previously been capped at 60 characters. |
| 225 | |
| 226 | - **[CRM-20776](https://issues.civicrm.org/jira/browse/CRM-20776) Menu structure |
| 227 | ([10573](https://github.com/civicrm/civicrm-core/pull/10573))** |
| 228 | |
| 229 | This fixes incorrect handling of URL paths, queries and fragments in the |
| 230 | navigation menu. This was a particular problem for AngularJS pages. |
| 231 | |
| 232 | - **[CRM-20640](https://issues.civicrm.org/jira/browse/CRM-20640) contribution |
| 233 | summary report: duplicates values with group filter |
| 234 | ([10603](https://github.com/civicrm/civicrm-core/pull/10603) and |
| 235 | [10596](https://github.com/civicrm/civicrm-core/pull/10596))** |
| 236 | |
| 237 | Reports with group filters would display rows twice if multiple groups were |
| 238 | selected in the filter and contacts were in more than one of those groups. |
| 239 | |
| 240 | - **[CRM-20953](https://issues.civicrm.org/jira/browse/CRM-20953) Importing |
| 241 | contacts with deceased_date not setting is_deceased |
| 242 | ([10742](https://github.com/civicrm/civicrm-core/pull/10742))** |
| 243 | |
| 244 | - **[CRM-20871](https://issues.civicrm.org/jira/browse/CRM-20871) crmUiSelect |
| 245 | fails to update when model changes |
| 246 | ([10659](https://github.com/civicrm/civicrm-core/pull/10659))** |
| 247 | |
| 248 | - **[CRM-20809](https://issues.civicrm.org/jira/browse/CRM-20809) Move |
| 249 | extensions cache from $extensionsDir to $uploadDir |
| 250 | ([10604](https://github.com/civicrm/civicrm-core/pull/10604))** |
| 251 | |
| 252 | Cached data about extensions was stored in the extensions directory, which may |
| 253 | not be an appropriate place and may not be writable. It is now stored in the |
| 254 | upload directory. |
| 255 | |
| 256 | - **[CRM-20828](https://issues.civicrm.org/jira/browse/CRM-20828) Saved field |
| 257 | mappings drop down is limited to 1 |
| 258 | ([10615](https://github.com/civicrm/civicrm-core/pull/10615))** |
| 259 | |
| 260 | - **[CRM-20509](https://issues.civicrm.org/jira/browse/CRM-20509) Checking |
| 261 | Contribution Note field in reports results in no rows |
| 262 | ([10631](https://github.com/civicrm/civicrm-core/pull/10631))** |
| 263 | |
| 264 | When displaying note fields in reports, the query would limit the results to |
| 265 | rows that had notes. |
| 266 | |
| 267 | - **[CRM-20351](https://issues.civicrm.org/jira/browse/CRM-20351) |
| 268 | hook_civicrm_buildForm invoked twice on a bunch of forms |
| 269 | ([10068](https://github.com/civicrm/civicrm-core/pull/10068))** |
| 270 | |
| 271 | - **[CRM-20774](https://issues.civicrm.org/jira/browse/CRM-20774) Add check for |
| 272 | existing index keys(different values) while creating missing indices. |
| 273 | ([10572](https://github.com/civicrm/civicrm-core/pull/10572) and |
| 274 | [10566](https://github.com/civicrm/civicrm-core/pull/10566))** |
| 275 | |
| 276 | The check and resolution for missing indexes would previously be unaware of |
| 277 | variations in the keys for equivalent indexes. |
| 278 | |
| 279 | - **[CRM-20722](https://issues.civicrm.org/jira/browse/CRM-20722) 'Lock wait |
| 280 | timeout exceeded' error triggered on smart group cache rebuild |
| 281 | ([10498](https://github.com/civicrm/civicrm-core/pull/10498))** |
| 282 | |
| 283 | This avoids an error when rebuilding the smart group cache on sites that have |
| 284 | a very large number of smart groups. |
| 285 | |
| 286 | - **[CRM-20443](https://issues.civicrm.org/jira/browse/CRM-20443) SQL syntax |
| 287 | error creating logging triggers if column name is reserved word |
| 288 | ([10530](https://github.com/civicrm/civicrm-core/pull/10530))** |
| 289 | |
| 290 | - **[CRM-20950](https://issues.civicrm.org/jira/browse/CRM-20950) Contact import |
| 291 | mapping to wrong location type (unreleased regression) |
| 292 | ([10736](https://github.com/civicrm/civicrm-core/pull/10736) and |
| 293 | [10735](https://github.com/civicrm/civicrm-core/pull/10735))** |
| 294 | |
| 295 | - **[CRM-20754](https://issues.civicrm.org/jira/browse/CRM-20754) memory leak in |
| 296 | CLI CSV import ([10537](https://github.com/civicrm/civicrm-core/pull/10537))** |
| 297 | |
| 298 | This resolves a problem of accumulating too much data in the |
| 299 | `PEAR_DB_DATAOBJECT` cache on large imports. |
| 300 | |
| 301 | - **[CRM-19702](https://issues.civicrm.org/jira/browse/CRM-19702) Fatal error |
| 302 | when merging contact records with custom file fields |
| 303 | ([9784](https://github.com/civicrm/civicrm-core/pull/9784))** |
| 304 | |
| 305 | - **[CRM-19653](https://issues.civicrm.org/jira/browse/CRM-19653) Custom field |
| 306 | checkboxes migrated incorrectly on merge (part deux) |
| 307 | ([10407](https://github.com/civicrm/civicrm-core/pull/10407))** |
| 308 | |
| 309 | - **[CRM-19821](https://issues.civicrm.org/jira/browse/CRM-19821) Remove |
| 310 | performance degrading joins from activity search (& api calls) |
| 311 | ([10274](https://github.com/civicrm/civicrm-core/pull/10274))** |
| 312 | |
| 313 | - **[CRM-20743](https://issues.civicrm.org/jira/browse/CRM-20743) users without |
| 314 | reserved tag permission may still modify the tag |
| 315 | ([10522](https://github.com/civicrm/civicrm-core/pull/10522))** |
| 316 | |
| 317 | While users lacking the "Administer reserved tags" permission were barred from |
| 318 | deleting or moving reserved tags, this prevents them from editing the tag name |
| 319 | and description. |
| 320 | |
| 321 | - **[CRM-20621](https://issues.civicrm.org/jira/browse/CRM-20621) manage tags: |
| 322 | the tag usage count is not accurate |
| 323 | ([10441](https://github.com/civicrm/civicrm-core/pull/10441))** |
| 324 | |
| 325 | ### CiviCase |
| 326 | |
| 327 | - **[CRM-20802](https://issues.civicrm.org/jira/browse/CRM-20802) |
| 328 | CaseType.create - Stale definition retained in memory |
| 329 | ([10591](https://github.com/civicrm/civicrm-core/pull/10591))** |
| 330 | |
| 331 | Cached case type information was retained even after modifying the case type. |
| 332 | |
| 333 | ### CiviContribute |
| 334 | |
| 335 | - **[CRM-20765](https://issues.civicrm.org/jira/browse/CRM-20765) Missing id for |
| 336 | 'onBehalfOfOrg' section |
| 337 | ([10550](https://github.com/civicrm/civicrm-core/pull/10550))** |
| 338 | |
| 339 | The `<div>` containing on-behalf section on contribution pages lacks the |
| 340 | `onBehalfOfOrg` ID attribute that it had in 4.6. |
| 341 | |
| 342 | - **[CRM-20753](https://issues.civicrm.org/jira/browse/CRM-20753) Net amount |
| 343 | doesn't respect localization |
| 344 | ([10536](https://github.com/civicrm/civicrm-core/pull/10536))** |
| 345 | |
| 346 | - **[CRM-20891](https://issues.civicrm.org/jira/browse/CRM-20891) Pay later |
| 347 | option incorrectly shows as completed when combining membership and donation |
| 348 | ([10683](https://github.com/civicrm/civicrm-core/pull/10683))** |
| 349 | |
| 350 | Using a contribution page with "separate membership payment" set, a pay-later |
| 351 | contribution would incorrectly mark the membership contribution completed. |
| 352 | |
| 353 | - **[CRM-20848](https://issues.civicrm.org/jira/browse/CRM-20848) Upgrade to |
| 354 | 4.7.19 sets price_field to inactive if default Financial Types are disabled |
| 355 | ([10675](https://github.com/civicrm/civicrm-core/pull/10675))** |
| 356 | |
| 357 | - **[CRM-20857](https://issues.civicrm.org/jira/browse/CRM-20857) Deferred |
| 358 | Revenue report - DB Error: unknown error |
| 359 | ([10646](https://github.com/civicrm/civicrm-core/pull/10646))** |
| 360 | |
| 361 | The Deferred Revenue report would have an error on if a database server's |
| 362 | `sql_mode` was set to `only_full_group_by`. |
| 363 | |
| 364 | - **[CRM-20867](https://issues.civicrm.org/jira/browse/CRM-20867) Class not |
| 365 | found ([10656](https://github.com/civicrm/civicrm-core/pull/10656))** |
| 366 | |
| 367 | This fixes a fatal error in the additional payment form due to a typo in the |
| 368 | name of the `CRM_Contribute_BAO_Contribution` class. |
| 369 | |
| 370 | - **[CRM-20649](https://issues.civicrm.org/jira/browse/CRM-20649) Notice error |
| 371 | when creating Price set |
| 372 | ([10431](https://github.com/civicrm/civicrm-core/pull/10431))** |
| 373 | |
| 374 | Validation of a price set name would generate a PHP notice if the name was |
| 375 | blank. |
| 376 | |
| 377 | - **[CRM-20823](https://issues.civicrm.org/jira/browse/CRM-20823) Price Set |
| 378 | field with an Expiry Date still being 'required' after being expired. |
| 379 | ([10613](https://github.com/civicrm/civicrm-core/pull/10613))** |
| 380 | |
| 381 | - **[CRM-20752](https://issues.civicrm.org/jira/browse/CRM-20752) Editing a |
| 382 | Cancelled Pledge updates the status of it to Pending/Inprogress |
| 383 | ([10535](https://github.com/civicrm/civicrm-core/pull/10535))** |
| 384 | |
| 385 | - **[CRM-20812](https://issues.civicrm.org/jira/browse/CRM-20812) Notice on live |
| 386 | contribution when only pay later is selected |
| 387 | ([10606](https://github.com/civicrm/civicrm-core/pull/10606))** |
| 388 | |
| 389 | - **[CRM-20761](https://issues.civicrm.org/jira/browse/CRM-20761) Formrule error |
| 390 | when priceset is selected on contribution page |
| 391 | ([10549](https://github.com/civicrm/civicrm-core/pull/10549))** |
| 392 | |
| 393 | When enabling a contribution amounts section and selecting a price set on a |
| 394 | contribution page's settings form, validation would fail, looking for a |
| 395 | contribution amount label. |
| 396 | |
| 397 | - **[CRM-20401](https://issues.civicrm.org/jira/browse/CRM-20401) Cancel/modify |
| 398 | URL receipt links not correct for Paypal Website Payments Pro |
| 399 | ([10424](https://github.com/civicrm/civicrm-core/pull/10424))** |
| 400 | |
| 401 | - **[CRM-20745](https://issues.civicrm.org/jira/browse/CRM-20745) Post date of |
| 402 | recur not respected in credit card pledge payment |
| 403 | ([10524](https://github.com/civicrm/civicrm-core/pull/10524))** |
| 404 | |
| 405 | - **[CRM-20773](https://issues.civicrm.org/jira/browse/CRM-20773) Contribution |
| 406 | tab shows Receive Date twice instead of Thank You date |
| 407 | ([10607](https://github.com/civicrm/civicrm-core/pull/10607))** |
| 408 | |
| 409 | - **[CRM-20387](https://issues.civicrm.org/jira/browse/CRM-20387) Sales Tax and |
| 410 | Invoicing code overwrites existing CiviCRM invoice ID |
| 411 | ([10298](https://github.com/civicrm/civicrm-core/pull/10298))** |
| 412 | |
| 413 | A new `invoice_number` field is added to the `civicrm_contribution` table to |
| 414 | record the ID of the manually-generated invoice. |
| 415 | |
| 416 | - **[CRM-20488](https://issues.civicrm.org/jira/browse/CRM-20488) Lift |
| 417 | restrictions for contact type soft credit |
| 418 | ([10532](https://github.com/civicrm/civicrm-core/pull/10532) and |
| 419 | [10419](https://github.com/civicrm/civicrm-core/pull/10419))** |
| 420 | |
| 421 | Users could not soft-credit an organization if the contribution originated |
| 422 | from a contribution page where honor/memory is enabled. |
| 423 | |
| 424 | - **[CRM-19478](https://issues.civicrm.org/jira/browse/CRM-19478) API not |
| 425 | handling Paypal recurring IPN where p=null for Contribution Page |
| 426 | ([10447](https://github.com/civicrm/civicrm-core/pull/10447))** |
| 427 | |
| 428 | - **[CRM-20495](https://issues.civicrm.org/jira/browse/CRM-20495) "Contribution |
| 429 | amounts section" checkbox setting on contribution pages always shows as |
| 430 | checked. ([10521](https://github.com/civicrm/civicrm-core/pull/10521))** |
| 431 | |
| 432 | - **[CRM-20747](https://issues.civicrm.org/jira/browse/CRM-20747) |
| 433 | {contribution.campaign} token not working on Contribution ThankYou letter |
| 434 | ([10533](https://github.com/civicrm/civicrm-core/pull/10533))** |
| 435 | |
| 436 | ### CiviMember |
| 437 | |
| 438 | - **[CRM-19017](https://issues.civicrm.org/jira/browse/CRM-19017) Scheduled |
| 439 | membership reminders have stopped working |
| 440 | ([10652](https://github.com/civicrm/civicrm-core/pull/10652))** |
| 441 | |
| 442 | - **[CRM-20716](https://issues.civicrm.org/jira/browse/CRM-20716) Array to |
| 443 | string issue on php7 when creating membership activity |
| 444 | ([10492](https://github.com/civicrm/civicrm-core/pull/10492))** |
| 445 | |
| 446 | - **[CRM-20650](https://issues.civicrm.org/jira/browse/CRM-20650) Translate |
| 447 | strings (ts) in CiviMember dashboard and Contribute manage |
| 448 | ([10432](https://github.com/civicrm/civicrm-core/pull/10432))** |
| 449 | |
| 450 | - **[CRM-18177](https://issues.civicrm.org/jira/browse/CRM-18177) When Renewing |
| 451 | an existing membership, if CC details are incorrect, Membership is set to |
| 452 | Cancelled preventing contact from trying again |
| 453 | ([10770](https://github.com/civicrm/civicrm-core/pull/10770)) (fix to problem |
| 454 | introduced in original bug fix)** |
| 455 | |
| 456 | - **[CRM-20850](https://issues.civicrm.org/jira/browse/CRM-20850) Replace fatal |
| 457 | with statusBounce in membership form |
| 458 | ([10638](https://github.com/civicrm/civicrm-core/pull/10638))** |
| 459 | |
| 460 | When a user links to edit a linked contribution from a membership and they |
| 461 | don't have permission to edit the contribution, they should be redirected with |
| 462 | an error notice rather than being shown a fatal error. |
| 463 | |
| 464 | - **[CRM-20667](https://issues.civicrm.org/jira/browse/CRM-20667) Additonal Line |
| 465 | item created from Membership backoffice form |
| 466 | ([10450](https://github.com/civicrm/civicrm-core/pull/10450))** |
| 467 | |
| 468 | - **[CRM-20805](https://issues.civicrm.org/jira/browse/CRM-20805) Fatal Error |
| 469 | when adding new membership type on a contribution page. |
| 470 | ([10597](https://github.com/civicrm/civicrm-core/pull/10597))** |
| 471 | |
| 472 | - **[CRM-20668](https://issues.civicrm.org/jira/browse/CRM-20668) Notice error |
| 473 | ([10452](https://github.com/civicrm/civicrm-core/pull/10452))** |
| 474 | |
| 475 | This fixes a PHP notice when creating a membership using a price set on the |
| 476 | backend. |
| 477 | |
| 478 | - **[CRM-20675](https://issues.civicrm.org/jira/browse/CRM-20675) Membership |
| 479 | status update creates renewal activity |
| 480 | ([10457](https://github.com/civicrm/civicrm-core/pull/10457))** |
| 481 | |
| 482 | - **[CRM-20567](https://issues.civicrm.org/jira/browse/CRM-20567) backoffice |
| 483 | membership via price set errors with non-aggregated column |
| 484 | ([10346](https://github.com/civicrm/civicrm-core/pull/10346))** |
| 485 | |
| 486 | This is one of several errors that appear when `sql_mode` was set to |
| 487 | `only_full_group_by`. |
| 488 | |
| 489 | - **[CRM-20720](https://issues.civicrm.org/jira/browse/CRM-20720) CIVICRM-128 |
| 490 | Unable to sort Price Options for Price Fieldset. Weight values are not being |
| 491 | set at all in database. |
| 492 | ([10542](https://github.com/civicrm/civicrm-core/pull/10542))** |
| 493 | |
| 494 | - **[CRM-20670](https://issues.civicrm.org/jira/browse/CRM-20670) Cannot edit |
| 495 | membership type if lots of members already exist |
| 496 | ([10534](https://github.com/civicrm/civicrm-core/pull/10534) and |
| 497 | [10455](https://github.com/civicrm/civicrm-core/pull/10455))** |
| 498 | |
| 499 | ### CiviEvent |
| 500 | |
| 501 | - **[CRM-20741](https://issues.civicrm.org/jira/browse/CRM-20741) Cancellation |
| 502 | message shown as error |
| 503 | ([10515](https://github.com/civicrm/civicrm-core/pull/10515))** |
| 504 | |
| 505 | - **[CRM-20633](https://issues.civicrm.org/jira/browse/CRM-20633) custom field |
| 506 | set displayed twice on register event Participant |
| 507 | ([10551](https://github.com/civicrm/civicrm-core/pull/10551))** |
| 508 | |
| 509 | When switching event types on the backend form to add an event participant, |
| 510 | custom fields common to all event types would be added repeatedly. |
| 511 | |
| 512 | - **[CRM-20775](https://issues.civicrm.org/jira/browse/CRM-20775) Wrong is full |
| 513 | results for API event get |
| 514 | ([10568](https://github.com/civicrm/civicrm-core/pull/10568))** |
| 515 | |
| 516 | When Max Number of Participants event field is left empty, the API would |
| 517 | return `1` for the `is_full`property instead of `0`. |
| 518 | |
| 519 | - **[CRM-19745](https://issues.civicrm.org/jira/browse/CRM-19745) Image URL |
| 520 | field doesn't show up on CiviEvent Additional Participants Profile |
| 521 | ([9777](https://github.com/civicrm/civicrm-core/pull/9777))** |
| 522 | |
| 523 | ### CiviMail |
| 524 | |
| 525 | - **[CRM-20781](https://issues.civicrm.org/jira/browse/CRM-20781) Truncate long |
| 526 | text in mail listing |
| 527 | ([10576](https://github.com/civicrm/civicrm-core/pull/10576))** |
| 528 | |
| 529 | Long values in columns would crowd other columns off the screen or into |
| 530 | illegibility. |
| 531 | |
| 532 | - **[CRM-20902](https://issues.civicrm.org/jira/browse/CRM-20902) DB Syntax |
| 533 | error on Mailing Opened Report |
| 534 | ([10690](https://github.com/civicrm/civicrm-core/pull/10690))** |
| 535 | |
| 536 | - **[CRM-20746](https://issues.civicrm.org/jira/browse/CRM-20746) CiviMail - |
| 537 | text part of resubscribe confirmation mail contains html |
| 538 | ([10528](https://github.com/civicrm/civicrm-core/pull/10528))** |
| 539 | |
| 540 | - **[CRM-20412](https://issues.civicrm.org/jira/browse/CRM-20412) mailing |
| 541 | report: unique opens detail view inaccurate |
| 542 | ([10558](https://github.com/civicrm/civicrm-core/pull/10558))** |
| 543 | |
| 544 | - **[CRM-20411](https://issues.civicrm.org/jira/browse/CRM-20411) mailing tab |
| 545 | listing: MySQL 5.7 group by error |
| 546 | ([10562](https://github.com/civicrm/civicrm-core/pull/10562) and |
| 547 | [10541](https://github.com/civicrm/civicrm-core/pull/10541))** |
| 548 | |
| 549 | - **[CRM-20713](https://issues.civicrm.org/jira/browse/CRM-20713) db error when |
| 550 | populating mailing recipients because sms_provider_id is 'null' |
| 551 | ([10487](https://github.com/civicrm/civicrm-core/pull/10487))** |
| 552 | |
| 553 | ### Backdrop Integration |
| 554 | |
| 555 | - **Fix spelling to canvass for civicrm_engage |
| 556 | ([40](https://github.com/civicrm/civicrm-backdrop/pull/40))** |
| 557 | |
| 558 | - **Bug fixes - issues #22, #31, #33 |
| 559 | ([39](https://github.com/civicrm/civicrm-backdrop/pull/39))** |
| 560 | |
| 561 | - **Improve Views checkbox value handling |
| 562 | ([37](https://github.com/civicrm/civicrm-backdrop/pull/37))** |
| 563 | |
| 564 | - **add new views handlers to hook_autoload_info |
| 565 | ([38](https://github.com/civicrm/civicrm-backdrop/pull/38))** |
| 566 | |
| 567 | - **Merge in civicrm/drupal from Dec 15, 2015 to June 21, 2017 |
| 568 | ([36](https://github.com/civicrm/civicrm-backdrop/pull/36))** |
| 569 | |
| 570 | ### Drupal Integration |
| 571 | |
| 572 | - **[CRM-20525](https://issues.civicrm.org/jira/browse/CRM-20525) Webform Pay |
| 573 | later sends Receipt email rather than Invoice email |
| 574 | ([10306](https://github.com/civicrm/civicrm-core/pull/10306))** |
| 575 | |
| 576 | - **[CRM-19976](https://issues.civicrm.org/jira/browse/CRM-19976) Drush: cannot |
| 577 | disable civicrm debug |
| 578 | ([457](https://github.com/civicrm/civicrm-drupal/pull/457))** |
| 579 | |
| 580 | While `drush civicrm-enable-debug` was defined, this adds the |
| 581 | `civicrm-disable-debug` command. |
| 582 | |
| 583 | ### Joomla Integration |
| 584 | |
| 585 | - **[CRM-19914](https://issues.civicrm.org/jira/browse/CRM-19914) |
| 586 | civicrmHooks.php issues on windows |
| 587 | ([10571](https://github.com/civicrm/civicrm-core/pull/10571))** |
| 588 | |
| 589 | This resolves problems locating the `civicrmHooks.php` file on Joomla sites in |
| 590 | Windows. |
| 591 | |
| 592 | ## <a name="misc"></a>Miscellany |
| 593 | |
| 594 | - **[CRM-20837](https://issues.civicrm.org/jira/browse/CRM-20837) Make setting |
| 595 | bug more explicit |
| 596 | ([10627](https://github.com/civicrm/civicrm-core/pull/10627))** |
| 597 | |
| 598 | - **[CRM-20677](https://issues.civicrm.org/jira/browse/CRM-20677) Use |
| 599 | generalised function to retrieve financial account |
| 600 | ([10463](https://github.com/civicrm/civicrm-core/pull/10463))** |
| 601 | |
| 602 | - **[CRM-20786](https://issues.civicrm.org/jira/browse/CRM-20786) Move |
| 603 | deprecated utils functions to the import classes |
| 604 | ([10578](https://github.com/civicrm/civicrm-core/pull/10578), |
| 605 | [10580](https://github.com/civicrm/civicrm-core/pull/10580), |
| 606 | [10579](https://github.com/civicrm/civicrm-core/pull/10579), and |
| 607 | [10581](https://github.com/civicrm/civicrm-core/pull/10581))** |
| 608 | |
| 609 | - **[CRM-20771](https://issues.civicrm.org/jira/browse/CRM-20771) Ensure that |
| 610 | AddColumn in CRM_Upgrade_Incremental_Base can support translatable columns |
| 611 | ([10561](https://github.com/civicrm/civicrm-core/pull/10561))** |
| 612 | |
| 613 | - **[CRM-20833](https://issues.civicrm.org/jira/browse/CRM-20833) Change |
| 614 | namespace for APIv4 entities |
| 615 | ([10632](https://github.com/civicrm/civicrm-core/pull/10632) and |
| 616 | [10625](https://github.com/civicrm/civicrm-core/pull/10625))** |
| 617 | |
| 618 | The namespace is now `Civi\Api4\Entity` rather than `Civi\Api4`. |
| 619 | |
| 620 | - **[CRM-19726](https://issues.civicrm.org/jira/browse/CRM-19726) |
| 621 | `CiviMailUtils::clearMessages()` should clear all messages by default |
| 622 | ([10669](https://github.com/civicrm/civicrm-core/pull/10669))** |
| 623 | |
| 624 | - **Misspelling ([10619](https://github.com/civicrm/civicrm-core/pull/10619))** |
| 625 | |
| 626 | - **[CRM-20797](https://issues.civicrm.org/jira/browse/CRM-20797) Use is_payment |
| 627 | to retrieve payments |
| 628 | ([10587](https://github.com/civicrm/civicrm-core/pull/10587))** |
| 629 | |
| 630 | - **Replace a couple of calls to deprecated function |
| 631 | ([10527](https://github.com/civicrm/civicrm-core/pull/10527))** |
| 632 | |
| 633 | - **[CRM-20758](https://issues.civicrm.org/jira/browse/CRM-20758) Fix deprecated |
| 634 | fn call on import screen |
| 635 | ([10544](https://github.com/civicrm/civicrm-core/pull/10544))** |
| 636 | |
| 637 | - **[CRM-20541](https://issues.civicrm.org/jira/browse/CRM-20541) Edge case |
| 638 | where DB connection is not available |
| 639 | ([447](https://github.com/civicrm/civicrm-drupal/pull/447))** |
| 640 | |
| 641 | Certain static variables now use Drupal's built-in system. |
| 642 | |
| 643 | ## <a name="credits"></a>Credits |
| 644 | |
| 645 | This release was developed by the following code authors: |
| 646 | |
| 647 | AGH Strategies - Andie Hunt; Arun Singh; Australian Greens - Seamus Lee; Brooks |
| 648 | Digital - Spencer Brooks; CEDC - Laryn Kragt Bakker; Circle Interactive - Dave |
| 649 | Jenkins; CiviCRM - Coleman Watts, Tim Otten; CiviDesk - Yashodha Chaku; |
| 650 | CompuCorp - Michael Devery; Coop SymbioTIC - Mathieu Lutfy; Dave Greenberg; |
| 651 | Electronic Frontier Foundation - Mark Burdett; Francesc Bassas i Bullich; |
| 652 | Freeform Solutions - Herb van den Dool; Fuzion - Chris Burgess, Eileen |
| 653 | McNaughton, Jitendra Purohit; Gizra - Aron Novak; JMA Consulting - Edsel Lopez, |
| 654 | Monish Deb, Pradeep Nayak; John Kingsnorth; Joinery - Allen Shaw; Joost Fock; |
| 655 | Klaas Eikelboom; Lighthouse Design and Consulting - Brian Shaughnessy; Mattias |
| 656 | Michaux; Megaphone Technology Consulting - Jon Goldberg; MJW Consulting - |
| 657 | Matthew Wire; Oxfam Germany - Thomas Schüttler; Progressive Technology Project - |
| 658 | Jamie McClelland; Squiffle Consulting - Aidan Saunders; Wikimedia Foundation - |
| 659 | Eileen McNaughton, Maggie Epps |
| 660 | |
| 661 | Most authors also reviewed code for this release; in addition, the following |
| 662 | reviewers contributed their comments: |
| 663 | |
| 664 | Agileware - Agileware Team; Arkadiusz Rzadkowolski; Blackfly Solutions - Alan |
| 665 | Dixon; CiviDesk - Nicolas Ganivet; CompuCorp - Davi Alexandre, Guanhuan Chen, |
| 666 | Jamie Novick, Mirela Stanila; DevMate - Adam Kwiatkowski; Donald Hirst; DotPro - |
| 667 | Diego Viegas; F. M. Andrimont; Fuzion - Peter Davis, Torrance Hodgson; JMA |
| 668 | Consulting - Joe Murray, Pradeep Nayak; Johan Vervloet; Jvillage Network - Dina |
| 669 | London; Korlon - Stuart Gaston; Lueck Data Systems - Michael Lueck; MC3 - Graham |
| 670 | Mitchell; Nathan Brettell; Oxfam Germany - Thomas Schüttler; Peter Bull; Phil |
| 671 | McKerracher; Semper IT - Karin Gerritsen; Skvare - Mark Hanna; Stephen |
| 672 | Palmstrom; Tadpole Collective - Kevin Cristiano; Upleaf - Osvaldo Gomez; |
| 673 | Wikimedia Foundation - Elliott Eggleston |
| 674 | |
| 675 | ## <a name="feedback"></a>Feedback |
| 676 | |
| 677 | These release notes have been made possible by the diligent curation of Andie Hunt. |
| 678 | If you'd like to provide feedback on them, please login to https://chat.civicrm.org/civicrm |
| 679 | and contact `@agh1`. |