Development issueshttps://lab.civicrm.org/groups/dev/-/issues2020-11-23T01:43:30Zhttps://lab.civicrm.org/dev/core/-/issues/2205Deprecation warning when doing search result tasks after Find Cases2020-11-23T01:43:30ZDaveDDeprecation warning when doing search result tasks after Find Cases`User deprecated function: Deprecated function CRM_Core_Form_Task::getTableName, use function should be overridden. Array ( [civi.tag] => deprecated ) in CRM_Core_Error_Log->log() (line 58 of .../CRM/Core/Error/Log.php).`
`User deprecat...`User deprecated function: Deprecated function CRM_Core_Form_Task::getTableName, use function should be overridden. Array ( [civi.tag] => deprecated ) in CRM_Core_Error_Log->log() (line 58 of .../CRM/Core/Error/Log.php).`
`User deprecated function: Deprecated function CRM_Core_Form_Task::getEntityAliasField, use function should be overridden. Array ( [civi.tag] => deprecated ) in CRM_Core_Error_Log->log() (line 58 of .../CRM/Core/Error/Log.php).`
Seems to be from here: https://github.com/civicrm/civicrm-core/pull/18783/files#diff-d3f50e6b56f73404b1de848be304c52ce8fbd3c126f120268778ea44ffb2dff8R3055.32.0https://lab.civicrm.org/dev/civicrm-asset-plugin/-/issues/13Can we make the "Registration Info" profile be adequate for membership contri...2020-11-24T15:15:11ZHeneryHCan we make the "Registration Info" profile be adequate for membership contribution pages?I added a "Your Registration Info" profile to my new member signup contribution page but it still complains that I need to also include the Supporter Profile too.
Seems redundant but maybe it just has to be.
![supporter_profile](/uploa...I added a "Your Registration Info" profile to my new member signup contribution page but it still complains that I need to also include the Supporter Profile too.
Seems redundant but maybe it just has to be.
![supporter_profile](/uploads/baa07dc3c381876414e8a6e8f9a634ac/supporter_profile.png)https://lab.civicrm.org/dev/core/-/issues/808support reCaptcha v32020-11-24T22:45:22ZJoeMurraysupport reCaptcha v3There's a new reCaptcha that does not show I am not a robot, but does require evaluation of a score returned. Would be good to support it before current v2 goes away (this is Google, days before Google+ is disappearing ;) ).
See https:/...There's a new reCaptcha that does not show I am not a robot, but does require evaluation of a score returned. Would be good to support it before current v2 goes away (this is Google, days before Google+ is disappearing ;) ).
See https://developers.google.com/recaptcha/docs/versionshttps://lab.civicrm.org/dev/drupal/-/issues/45Drupal 7: "Access CiviCRM backend and API Master control" permission Required2020-11-25T13:15:21ZjoeglDrupal 7: "Access CiviCRM backend and API Master control" permission RequiredThis wasn't me, but we had the same issue and fixed it the same way: https://civicrm.stackexchange.com/questions/28085/access-denied-for-specific-role
We have Drupal 7.61 CiviCRM 5.9.0. Whenever a user tries to access the civicrm backen...This wasn't me, but we had the same issue and fixed it the same way: https://civicrm.stackexchange.com/questions/28085/access-denied-for-specific-role
We have Drupal 7.61 CiviCRM 5.9.0. Whenever a user tries to access the civicrm backend (mysite.com/civicrm) they get an "Access Denied" result. The only permission which fixes this is the "Access CiviCRM backend and API Master control" but it says to give to trusted roles only. This doesn't seem right, but I also don't remember this permission existing before.
I also can't find any documentation related to this permission or what it entails. Interestingly enough, two of the CiviCRM roles already had the permission, but one didn't. And all of these roles were able to access the CiviCRM backend before we upgraded from 4.7.17 to 5.9.1.https://lab.civicrm.org/dev/core/-/issues/2186Support For multiple cases while creating email activity2020-11-26T15:35:37Zshahrukh_compucorpSupport For multiple cases while creating email activityOverview
----------------------------------------
CiviCRM has functionality to allow you to create email activities and to optionally attach it to one case as well.
Currently the email activity creation form only accepts one case id un...Overview
----------------------------------------
CiviCRM has functionality to allow you to create email activities and to optionally attach it to one case as well.
Currently the email activity creation form only accepts one case id unlike contact id parameter which can accept multiple comma separated ids.
This makes it impossible to attach the same email activity to multiple cases.
Note: I am not sure if there is any particular reason that this form does not support multiple cases as the print merge document does support multiple case ids.
Problem statement
----------------------------------------
Currently it is impossible to attach one email activity to multiple cases.
Example use-case
----------------------------------------
1. Go to email activity creation form with valid contact ids in parameter and multiple valid case ids separated by comma.
2. Fill the form and Proceed to submit.
Current behaviour
----------------------------------------
The submitted form results in an error.
Proposed behaviour
----------------------------------------
The caseid parameter can be renamed to caseids so that it can accept multiple case ids separated by comma similar to cid parameter and the created activity can be attached with all the providid cases.https://lab.civicrm.org/dev/drupal/-/issues/149D8/D9 Fix Session Start Handling2020-11-30T23:13:25ZseamusleeD8/D9 Fix Session Start HandlingAt present because there is no override in the Drupal8 system class, the DrupalBase SessionStart function is used instead which uses functions and session related code that is not suitable for Drupal8 and can cause Session Already Starte...At present because there is no override in the Drupal8 system class, the DrupalBase SessionStart function is used instead which uses functions and session related code that is not suitable for Drupal8 and can cause Session Already Started notices in watchdog if you use cron.php to execute your cron job.5.33.0seamusleeseamusleehttps://lab.civicrm.org/dev/core/-/issues/2224Advanced search - AND/OR operator always does OR for tags and groups2020-12-01T15:57:28ZDaveDAdvanced search - AND/OR operator always does OR for tags and groupsExample:
1. Select two tags and leave the search operator at AND. It does an OR search instead. If you change the operator to OR it also does an OR search.
2. Ditto for groups.
Happens on https://dmaster.demo.civicrm.org
Doesn't seem t...Example:
1. Select two tags and leave the search operator at AND. It does an OR search instead. If you change the operator to OR it also does an OR search.
2. Ditto for groups.
Happens on https://dmaster.demo.civicrm.org
Doesn't seem to be recent. Happens in 5.24 too.https://lab.civicrm.org/dev/drupal/-/issues/148When creating Premium - requiring subscription even for "physical" premiums2020-12-02T20:14:25ZplanetwebbWhen creating Premium - requiring subscription even for "physical" premiumsWhen trying to add a new Premium (first one), I get the error "Please enter a Period Type" - even though the premium is a regular "product" and not a subscription.
Civi 5.31 / Drupal 7.73 / PHP 7.3
It has been reproduced by another us...When trying to add a new Premium (first one), I get the error "Please enter a Period Type" - even though the premium is a regular "product" and not a subscription.
Civi 5.31 / Drupal 7.73 / PHP 7.3
It has been reproduced by another user with 5.31, his workaround is to submit dummy subscription info just to submit.
![Screen_Shot_2020-11-20_at_10.08.59_AM](/uploads/8ae8ed5da027f8fd5e550f3ea5185971/Screen_Shot_2020-11-20_at_10.08.59_AM.png)5.32.0https://lab.civicrm.org/dev/core/-/issues/2162Reports cannot filter for Contacts with multiple selections in a multi-select...2020-12-02T21:04:03ZjhungerfordReports cannot filter for Contacts with multiple selections in a multi-select Custom FieldOverview
----------------------------------------
If a Contact has multiple selections in a multi-select Custom Field, a Report which filters for "one of" those selections will never find that Contact. There is no "includes" or similar o...Overview
----------------------------------------
If a Contact has multiple selections in a multi-select Custom Field, a Report which filters for "one of" those selections will never find that Contact. There is no "includes" or similar option which finds Contacts who have the specified selection and other selections as well. The generated SQL syntax is not compatible with the storage format of multi-select custom fields when more than one option is selected.
For example: Consider the demo database at https://demo.circle-interactive.co.uk/
It has a Custom Field called "Most Important Issue" with the options "Environment", "Education", and "Social Justice".
Suppose we create another Custom Field which uses the same options, and it is a multi-select. We'll call this field "Important Issues" and check "searchable" and "multi-select".
Now we edit two contacts at random - give one of them "Environment" in their "Important Issues" field, and give the other one "Environment" and "Social Justice" in the same field.
Last, we create a Contact Summary report showing the Important Issues. In the filters, we select "Is one of" - "Environment", and run the report. It will find the Contact who only has "Environment" selected, but the one who has that and "Social Justice" will not be shown.
If you see this issue shortly after it is reported, the described setup may be visible in this report:
https://demo.circle-interactive.co.uk/civicrm/report/instance/39?reset=1&force=1
Reproduction steps
----------------------------------------
- Log into a civi demo site (e.g. demo.circle-interactive.co.uk)
- Create new custom fieldset "Test Report Filter Issue"
- Add a custom field:
- Field Label: Important Issues
- Alphanumeric Select
- Multi-Select is enabled
- Reuse an existing set of multiple choice options if suitable (e.g. from "Most Important Issue") or create a new set
- Searchable: Yes
- Edit two random Contacts
- For one, set the new "Important Issues" field to "Environment"
- For the other, set the new field to "Environment" and "Social Justice"
- Create a new "Constituent Report (Summary)" (/civicrm/report/contact/summary?reset=1)
- in "Columns", tick "First name", "Last name", and "Important Issues" (the new custom field)
- in "Filters", choose "Important Issues" - "Is one of" - "Environment"
- Run the report
Current behaviour
----------------------------------------
The report only finds the Contact who has the single selection.
There is no other way to filter for people who do have the Environment selection (e.g. "includes one of" as distinct from "is exactly one of").
Expected behaviour
----------------------------------------
If some sites do want the "is exactly one of" filter, others (like ours) will need a separate "includes one of" option. I may be able to do this with custom report templates for our site as needed, but a system-wide solution would be much better.
The behaviour appears to have changed when we upgraded to 5.27 from the previous ESR, though we've only noticed it a few months later.
From our perspective, the old behaviour was correct and expected, and the "is one of" text could have been improved by changing it to "includes one of". However, the new behaviour may be desired by some sites. I think that may be implied by this old issue, but I may be misunderstanding since they're also discussing the regex as it relates to the storage format:
https://issues.civicrm.org/jira/browse/CRM-18803
Environment information
----------------------------------------
* __Browser:__ Chrome 86.0.4240.111 (Official Build) Arch Linux (64-bit)
* __CiviCRM:__ 5.27.5, also tested on 5.29.1 and 5.30.1
* __PHP:__ 7.3
* __CMS:__ Drupal 7.73
* __Database:__ MariaDB 10.3
* __Web Server:__ Apache 2.4
Comments
----------------------------------------
A couple of years ago, there was some discussion of a similar issue with contact subtypes, and Eileen wondered whether it might affect custom fields as well:
https://github.com/civicrm/civicrm-core/pull/13158#issuecomment-442334591
At the time, it was still using a regex, but the new SQL generated by the report takes the simpler form "IN ('3')", which will never match a column with a '3' nestled between control codes and other values.
Yesterday when trying to trace the path which generated the SQL, I thought this line might be relevant:
https://lab.civicrm.org/dev/core/-/blob/master/CRM/Core/BAO/CustomField.php#L2583-2584
Considering that the new behaviour might be deliberate, I thought I should report the issue rather than trying to find a solution since the correct path forward is not obvious to me.5.33.0https://lab.civicrm.org/dev/core/-/issues/2228CiviCRM 5.31.0, CiviCRM Mailing, changing the Location Type from "Automatic" ...2020-12-03T06:28:38Zjustinfreeman (Agileware)CiviCRM 5.31.0, CiviCRM Mailing, changing the Location Type from "Automatic" to any of the other Location Types results in Error 'number:4' is not a valid option for field location_type_idCiviCRM Mailing, changing the Location Type from "Automatic" to any of the other Location Types results in Error 'number:4' is not a valid option for field location_type_id.
Bug first identified in CiviCRM 5.31.0, repeatable in CiviCRM ...CiviCRM Mailing, changing the Location Type from "Automatic" to any of the other Location Types results in Error 'number:4' is not a valid option for field location_type_id.
Bug first identified in CiviCRM 5.31.0, repeatable in CiviCRM 5.31.1 and CiviCRM DMASTER, CiviCRM 5.33.alpha1
Steps to reproduce:
1. Create a Mailing
2. Select a Recipient Group
3. Click the "Edit Recipient Options" button
4. Select a different Location Type from the Location Types drop-down
5. Close the dialog
6. Wait for the Mailing to save, error message will then be shown
![screencapture-dmaster-demo-civicrm-org-civicrm-a-2020-12-02-16_05_36](/uploads/b5ff3aa5cd08ebb4beaa40f43ecf05a0/screencapture-dmaster-demo-civicrm-org-civicrm-a-2020-12-02-16_05_36.png)
Agileware Ref: CIVICRM-16195.32.0https://lab.civicrm.org/dev/core/-/issues/1790Send email to contacts when clicking on their email address on the contact's ...2020-12-03T14:14:42ZreneolivoSend email to contacts when clicking on their email address on the contact's cardOverview
----------------------------------------
We would like to be able to send emails to contacts when we click on their email address on the contact's card
![gif](/uploads/0526250aed0f562f0f56f3dc2b966e36/gif.gif)
Example use-case...Overview
----------------------------------------
We would like to be able to send emails to contacts when we click on their email address on the contact's card
![gif](/uploads/0526250aed0f562f0f56f3dc2b966e36/gif.gif)
Example use-case
----------------------------------------
1. Hover the contact's icon. The contact's card with their information is going to be displayed.
2. Click on any email address.
3. The email modal should open up populated with the contact's details.
Current behaviour
----------------------------------------
* The contact's card hides as soon as we try to move the mouse on top of the email address.
* When we click on the email nothing happens.
Proposed behaviour
----------------------------------------
* The contact's card should stay open when hovering over it.
* When an email is clicked, it should open with the email modal with the contact's information.
This is useful when checking multiple contacts. We can send an email to one of them without having to open up the contact's details.https://lab.civicrm.org/dev/core/-/issues/2227ACLed user that can access deleted contacts, get deleted contacts within thei...2020-12-03T18:56:33ZseamusleeACLed user that can access deleted contacts, get deleted contacts within their search result when generatePermissionClause is called with onlyDeleted is FALSEOverview
----------------------------------------
An ACLed user doing an advanced search but does have permission to view deleted (trashed) contacts will see those trash contacts appear in an advanced search without explicitly searching ...Overview
----------------------------------------
An ACLed user doing an advanced search but does have permission to view deleted (trashed) contacts will see those trash contacts appear in an advanced search without explicitly searching in the trash
Reproduction steps
----------------------------------------
1. Create a role without view all contacts / edit all contacts but with view deleted contacts permission and ensure that there is at least 1 deleted contact a user with that role could see
1. Perform an advanced search as a user with that role but don't search in the trash
1. Find that the trashed contact can still be found in the advanced search
Current behaviour
----------------------------------------
Contacts in the trash appear on advanced searches when not searching in the trash
Expected behaviour
----------------------------------------
Contacts in the trash should only be found if searching in the trash
Environment information
----------------------------------------
* __CiviCRM:__ _5.31.1_ <!-- If this problem relates to an upgrade, then specify both old and new versions -->
* __PHP:__ _7.2_
* __CMS:__ _Drupal 7_5.32.0https://lab.civicrm.org/dev/core/-/issues/2213Upgrade CiviCRM 5.28.3 to 5.30.0 with Clean URLs and WordPress Base Page "Civ...2020-12-03T22:20:10Zjustinfreeman (Agileware)Upgrade CiviCRM 5.28.3 to 5.30.0 with Clean URLs and WordPress Base Page "CiviCRM" breaks Mosaico IMG URLs and Email Tracked URLsThis has been observed on a CiviCRM and WordPress site. After upgrading from CiviCRM 5.28.3 to 5.30.0 with Clean URLs and WordPress Base Page "CiviCRM" we received reports that Mosaico IMG URLs and Email Tracked URLs were both broken. Th...This has been observed on a CiviCRM and WordPress site. After upgrading from CiviCRM 5.28.3 to 5.30.0 with Clean URLs and WordPress Base Page "CiviCRM" we received reports that Mosaico IMG URLs and Email Tracked URLs were both broken. This was confirmed as those URLs were returning 404s.
This was an old site and noted that the CiviCRM WordPress Base Page option was set to "CiviCRM". After changing the WordPress Base Page option to "civicrm" the Mosaico IMG URLs and Email Tracked URLs resolved correctly, no more 404s.
Was unable to reproduce this same problem on existing CiviCRM 5.31.0 and WordPress site, toggling the CiviCRM WordPress Base Page option from "civicrm" to "CiviCRM" did not result in 404 errors.
**Solution**
1. Find the WordPress page for CiviCRM, note the **Slug** part of the **Permalink** for this page eg. Permalink is https://test.com/civicrm then the Slug is **civicrm**
2. Go to CiviCRM, Administration, **CMS Database Integration**.
3. Change **CMS Database Integration** option to match the **Slug** part of the **Permalink**. eg. **civicrm**
4. Click **Save**.
5. Crack open a beer and **test**.
Agileware Ref: CIVICRM-16135.32.0https://lab.civicrm.org/dev/core/-/issues/233Discussion on how to track merged contacts2020-12-03T23:36:37ZeileenDiscussion on how to track merged contacts**Why?**
I'm raising this ticket because we don't have an agreed standard on how to track the history of merged contacts. Knowing which contacts were merged into a given contact can be important for reasons such us
1. When a donor requ...**Why?**
I'm raising this ticket because we don't have an agreed standard on how to track the history of merged contacts. Knowing which contacts were merged into a given contact can be important for reasons such us
1. When a donor requests that their data be deleted from the database there may be personal information retained in the database for that contact under merged contact records, which should also be tracked and deleted
1. When displaying log data for a contact such as their address history some of that data may be against a different contact. (For example the Extended reports extension allows you to create an address history report and optionally add it as a tab on the contact summary. This report currently includes data from merged contacts IF it can determine them - which currently requires you to have hacked core).
1. When looking up a contact by id and they have been merged to another contact then it should be easy to move to that contact in the UI
Because these various functions take place in different extensions a standard way of tracking merge history makes sense.
**Current Behaviour?**
Currently when a merge takes place 2 activities are created
* (1) 'Contact Merged'
- source is the logged in user,
- target is the retained contact.
- Deleted contact id is mentioned in subject text
- [CRM-14792](https://issues.civicrm.org/jira/browse/CRM-14792)
* (2) 'Contact deleted in merge'
- source is the logged in user
- target is the deleted contact
- Both contact ids are mentioned in the subject text
- activity has the other contact as 'parent_id'
- [CRM-18106](https://issues.civicrm.org/jira/browse/CRM-18106)
**Options**
1) The current behaviour DOES provide a path to piece together the contact history - ie. you need to track through 2 activities to get the contact pair. This seems a little unperformant / obscure but is do-able. We could enhance this by
a) adding an api eg. Contact.getmerges that would return details of previous merges and that could be a standard method for extensions like privacy extensions (including GDPR) and reports/dashlets that display contact history to find past mergees.
b) based on the above add a prominent link from merged contacts to the contact they were merge to.
2) Link the contacts via a single activity. ie. each of the activities created stores the logging in user and a target but leaves 'assignee' unused. This feels very logical and in fact would support a 'many-to-one' merge if we ever implemented it. WMF has implemented this through a core-hack and the extended reports extensions will present address history encompassing merges if sites implement this method. This was discussed on [CRM-21415](https://issues.civicrm.org/jira/browse/CRM-21415) and on [CRM-18106](https://issues.civicrm.org/jira/browse/CRM-18106) and there were 2 arguments made against
a) There is some complexity around viewing an activity assigned to a deleted contact (resolvable IMHO)
b) The semantics are odd - ie. the use of the 'assigned' field in one of the activites doesn't 'feel' like the right language.
The advantages are that the logic of reconstructing history seems simpler. However, it seems like either way the api & link described above make sense to expose the data
3) Using an external extension. This would basically mean a hook could catch the creation of the second activity & crawl back up the parent id to compose the detail of the first activity and either update the second activity with the extra detail OR store the data in another format - e.g a table. Storing in a table potentially gets around weirdness if the deleted contact is fully deleted but we don't want to have to totally rebuild from the log table. It does feel like there is some data duplication in this though and not 'wanting' to totally rebuild from the log table may or may not be a good argument for that duplication. There is some discomfort with having an extension provide the described api but I guess extensions like Extended reports don't have to have it as a real dependency - they can just change their behaviour depending on whether it is present.https://lab.civicrm.org/dev/core/-/issues/274required fields in multi-record custom field set not working in inline mode2020-12-03T23:48:27Zcziwjmkrequired fields in multi-record custom field set not working in inline modeIf you set a Custom Field to be required in a multi-record Custom Field Set, then you cannot add records when the Display Style is set to inline. I have followed the instruction to use the Edit button. When I try and save a record with a...If you set a Custom Field to be required in a multi-record Custom Field Set, then you cannot add records when the Display Style is set to inline. I have followed the instruction to use the Edit button. When I try and save a record with a value set in the required field, I get the error message:
Please correct the following errors in the form fields below:
• instrument name is a required field.
(instrument name is the field name)
It seems to work fine with display style Tab or Tab with table, but that doesn't suit how I would like to use it as this is important information that should be on the main screen.
Raised in stack exchange a couple of years ago (https://civicrm.stackexchange.com/questions/13001/repeatable-custom-groups-w-required-field/25840#25840) I have checked it on the WordPress and Drupal demo sites (currently at 5.5alpha1).https://lab.civicrm.org/dev/core/-/issues/301Dedupe ignores phone number from Drupal-Webforms and Contact Import depending...2020-12-03T23:49:48ZBobSDedupe ignores phone number from Drupal-Webforms and Contact Import depending on Civi version at rule creationOld rules found in table civicrm_dedupe_rule specify the rule_field 'phone', while rules created in more recent versions of Civi specify 'phone_numeric'.
In addition, there is some inconsistency in how the phone value is received in the...Old rules found in table civicrm_dedupe_rule specify the rule_field 'phone', while rules created in more recent versions of Civi specify 'phone_numeric'.
In addition, there is some inconsistency in how the phone value is received in the $params arguement of CRM/Dedupe/Finder.php:dupesByParams:
* webform_civicrm passes:<br>
`$params['civicrm_phone']['phone'] = "123-456-7890" (raw text string)`
* Contact import passes:<br>
`$params['civicrm_phone']['phone_numeric'] = "123-456-7890" (raw text string)`
In the dupesByParams function, there is a block which replaces the ['phone_numeric'] value with its numeric version, but there is no creation of ['phone_numeric'] if there exists only ['phone'].
This results in two conditions in which dedup ignores the phone number:
1. Webform submissions with new rules, because the rule specifies['phone_numeric'].
2. Contact import with old rules, because the rule specifies ['phone'].
I propose two changes to solve both these problems:
1. Upon upgrade, replace all occurences of 'phone' in civicrm_dedupe_rule.rule_field with 'phone_numeric'.
2. If passed only ['phone'] and not ['phone_numeric'], create the latter as shown in the following patch (based on the current Jun 11 917acf6 commit):
```
--- 917acf6/CRM/Dedupe/Finder.php
+++ new/CRM/Dedupe/Finder.php
@@ -146,6 +146,9 @@
}
$params['check_permission'] = CRM_Utils_Array::value('check_permission', $params, TRUE);
+ if (isset($params['civicrm_phone']['phone']) && !isset($params['civicrm_phone']['phone_numeric'])) {
+ $params['civicrm_phone']['phone_numeric'] = $params['civicrm_phone']['phone'];
+ }
if (isset($params['civicrm_phone']['phone_numeric'])) {
$orig = $params['civicrm_phone']['phone_numeric'];
$params['civicrm_phone']['phone_numeric'] = preg_replace('/[^\d]/', '', $orig);
```
Problems identified and solution tested in Civi 5.4.0.https://lab.civicrm.org/dev/core/-/issues/417Address.create API call: Untranslated province names are invalid options for ...2020-12-04T00:10:43ZjensschuppeAddress.create API call: Untranslated province names are invalid options for field state_province_idWhen calling the `Address.create` API call with a `state_province_id` set to the untranslated name of a province (as in its `name` attribute in the DB), and this province being translated in the current default language, an API error `'X...When calling the `Address.create` API call with a `state_province_id` set to the untranslated name of a province (as in its `name` attribute in the DB), and this province being translated in the current default language, an API error `'XYZ' is not a valid option for field state_province_id` is returned and the address is not being created/updated.
Being aware of this field ideally receiving the actual state_province ID instead of its name, this might be a minor issue, but it makes manual imports a mess, if we'd have to issue another API call first to retrieve the ID from the untranslated name, which is the actual value in the DB. So this error causes quite some confusion.
Steps to reproduce:
1. Set CiviCRM's default language to e.g. German
2. Find a state province which is translated (e.g. Switzerland's Geneva, which is "Genf" in German)
3. Issue an `Address.create` API call with the following parameters:
```JSON
{
"contact_id": 123, // A valid contact ID
"location_type_id": "Home",
"country_id": "CH",
"state_province_id": "Geneva",
}
```
4. Notice the API error.https://lab.civicrm.org/dev/core/-/issues/315Cancelling or going back on step 3 of importing memberships stills shows a wa...2020-12-04T01:40:53ZlolcodeCancelling or going back on step 3 of importing memberships stills shows a warning to backup the DBHitting either the cancel button or the previous page button stills shows a warning to backup the DB which looks like it is going to import the memberships. If I hit cancel on this dialog then it just disappears. If I hit OK it appears t...Hitting either the cancel button or the previous page button stills shows a warning to backup the DB which looks like it is going to import the memberships. If I hit cancel on this dialog then it just disappears. If I hit OK it appears to attempt to import and shows a progress bar but in my testing nothing was imported. There is no safe way to exit this screen except to close the browser.
I also notice that on this demo site (5.3.1) that was set to use French that the dialog message is in English.
![import_page_cancel](/uploads/3780d947ab561fdbd459be0a0148a1ff/import_page_cancel.jpg)https://lab.civicrm.org/dev/core/-/issues/885Attendee Report: Incorrect filtering by deceased participants2020-12-04T01:44:28ZshaneonabikeAttendee Report: Incorrect filtering by deceased participantsSo today I discovered a pretty strange bug, but I'm open to determine whether this is related to something in the configuration.
**Issue**
When viewing the Attendee List for a new event I noticed that the participant count was lower th...So today I discovered a pretty strange bug, but I'm open to determine whether this is related to something in the configuration.
**Issue**
When viewing the Attendee List for a new event I noticed that the participant count was lower than the Event Participants List. What is narrows down to is that the Attendee List has a *filter for excluding deceased participants*. When I set this to **Any** value it works perfectly.
I traced on so called *deceased* participant and they are not set to deceased. All of these users were imported about 1.5 years ago from an old CiviCRM system and imported here. I don't know if perhaps there an incorrect value is set for the deceased value and therefore is causing certain participants to be considered this way. In total I believe there is about **48** in total :/
**CiviCRM Details**
* Drupal 7
* CiviCRM 5.12.0
* PHP 7.3.4https://lab.civicrm.org/dev/civicrm-asset-plugin/-/issues/17Error in composer prevents install of some packages2020-12-04T02:31:22Zluke.stewartError in composer prevents install of some packagesThere seems to be an error occurring when installing some drupal modules via composer when civicrm is already installed.
Back trace shown:
```
Exception trace:
() at /vendor/civicrm/composer-compile-plugin/src/Util/ComposerPassthru.php...There seems to be an error occurring when installing some drupal modules via composer when civicrm is already installed.
Back trace shown:
```
Exception trace:
() at /vendor/civicrm/composer-compile-plugin/src/Util/ComposerPassthru.php:72
Civi\CompilePlugin\Util\ComposerPassthru->run() at phar:///usr/local/bin/composer/src/Composer/Plugin/PluginManager.php(196) : eval()'d code:117
Civi\CompilePlugin\CompilePlugin_composer_tmp5->runTasks() at n/a:n/a
call_user_func() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:164
Composer\EventDispatcher\EventDispatcher->doDispatch() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:96
Composer\EventDispatcher\EventDispatcher->dispatchScript() at phar:///usr/local/bin/composer/src/Composer/Installer.php:338
Composer\Installer->run() at phar:///usr/local/bin/composer/src/Composer/Command/RequireCommand.php:248
Composer\Command\RequireCommand->doUpdate() at phar:///usr/local/bin/composer/src/Composer/Command/RequireCommand.php:205
Composer\Command\RequireCommand->execute() at phar:///usr/local/bin/composer/vendor/symfony/console/Command/Command.php:245
Symfony\Component\Console\Command\Command->run() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:835
Symfony\Component\Console\Application->doRunCommand() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:185
Symfony\Component\Console\Application->doRun() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:281
Composer\Console\Application->doRun() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:117
Symfony\Component\Console\Application->run() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:113
Composer\Console\Application->run() at phar:///usr/local/bin/composer/bin/composer:61
require() at /usr/local/bin/composer:24
```
I can reproduce this on a clean install by doing the following:
composer create-project drupal/recommended-project civicrm
cd civicrm/
composer config extra.enable-patching true
composer config minimum-stability dev
composer require civicrm/civicrm-{core,packages,drupal-8}:'~5.32'
composer require drupal/drupalauth4ssp
Failure happens at the last step. Have also tried --with-all-dependencies and wiping vendor and composer.install in case this helps.
I suspect this might be related to: https://lab.civicrm.org/dev/drupal/-/issues/150