CiviCRM Core issueshttps://lab.civicrm.org/dev/core/-/issues2024-01-25T08:58:17Zhttps://lab.civicrm.org/dev/core/-/issues/4831Standalone: select2 seems to have too much margin, making it look a bit uggly2024-01-25T08:58:17ZjaapjansmaStandalone: select2 seems to have too much margin, making it look a bit ugglyThe select2 seems in standalone CiviCRM seems to have too much margin.
See screenshot:
![2023-12-04_13-30](/uploads/64d896e96a4f64311029bf1df1dc01e6/2023-12-04_13-30.png)The select2 seems in standalone CiviCRM seems to have too much margin.
See screenshot:
![2023-12-04_13-30](/uploads/64d896e96a4f64311029bf1df1dc01e6/2023-12-04_13-30.png)RichRichhttps://lab.civicrm.org/dev/core/-/issues/4830PHP 7.4 Don't Drop2023-12-03T07:01:29ZtreseroPHP 7.4 Don't DropPlease don't. I have tried multiple times to upgrade to PHP 8.1+ and there are still major issues.
Many issues with the intl php libraries and extensions. And other things. I've reverted multiple times back to php 7.4 to keep my site fu...Please don't. I have tried multiple times to upgrade to PHP 8.1+ and there are still major issues.
Many issues with the intl php libraries and extensions. And other things. I've reverted multiple times back to php 7.4 to keep my site functioning.https://lab.civicrm.org/dev/core/-/issues/4828Can't view/edit grants2023-12-03T18:47:17ZJonGoldCan't view/edit grantsOverview
----------------------------------------
Can't view/edit grants.
This is a 5.67 regression, from https://github.com/civicrm/civicrm-core/pull/27411.
Reproduction steps
----------------------------------------
1. Enable CiviGra...Overview
----------------------------------------
Can't view/edit grants.
This is a 5.67 regression, from https://github.com/civicrm/civicrm-core/pull/27411.
Reproduction steps
----------------------------------------
1. Enable CiviGrant.
1. Create a grant.
1. Go to **Grants » Find Grant**. Search for your grant.
1. Click **View**.
This is also true if you click **View** from a contact's *Grants* tab.
Additionally, while **Edit** works, the **Edit** and **Delete** buttons you see when viewing a grant do not.
Current behaviour
----------------------------------------
Empty grant view template.
Expected behaviour
----------------------------------------
Data should display.
Comments
----------------------------------------
There are two issues here. I have a partial fix but I can't work on this further.
* The View template contains tokens that aren't being passed to it. It's getting loaded from an `include` in `templates/CRM/Grant/Form/Grant.tpl` now, which it previously wasn't. We can use most of the values passed in `{$form}` for an Edit page, but we don't have a good way to display selects in View mode.
* When viewing the page, the grant ID and contact ID aren't being calculated correctly for the "Edit" and "Delete" button URLs.
To be honest, I'm not sure how this passed review. I can't find a single way to get a grant to display.colemanwcolemanwhttps://lab.civicrm.org/dev/core/-/issues/4826Add is_new as a field on membership api or possibly via membership_status2024-01-05T03:42:40ZeileenAdd is_new as a field on membership api or possibly via membership_statusI've been thinking about https://github.com/civicrm/civicrm-core/pull/28185 & have concluded that the way to determine if it is a new membership or renewal is to check for the new membership status.
However, that is not actually straig...I've been thinking about https://github.com/civicrm/civicrm-core/pull/28185 & have concluded that the way to determine if it is a new membership or renewal is to check for the new membership status.
However, that is not actually straight forward since we can't use {membership.membership_status_id.name} in case they have modified the statuses.
I'm thinking maybe an api calculated field (exposed as a token)
Then in the template it would be something like
```
{if {membership.membership_status_id.is_new|boolean}}
Signup
{else}
Renewal
{/if}
```
One concern with the above is that if you re-sent it after the status had changed from new (3 months by default) if would show 'renewal'. Obviously people can customise the templates, as they do the membership types, so we don't have to catch every possibility. We might consider doing instead
```
{if {membership.membership_status_id.is_new|boolean}}
Signup
{elseif !{contribution.receive_date|boolean}}
-- hasn't been sent already so we can be somewhat confident
Renewal
{else}
-- some mealy mouthed generic alternative
{/if}
```5.69.0https://lab.civicrm.org/dev/core/-/issues/4822Case activity filter causes performance headache for non-superusers2024-01-04T20:46:10ZJonGoldCase activity filter causes performance headache for non-superusersI received a report that contacts were taking over 60 seconds to load. This db has ~175,000 contacts and ~272,000 activities. It does not use CiviCase.
I traced the problem to the calculation of the activity count to display on the ac...I received a report that contacts were taking over 60 seconds to load. This db has ~175,000 contacts and ~272,000 activities. It does not use CiviCase.
I traced the problem to the calculation of the activity count to display on the activity tab. This is the query that's taking ~71 seconds:
```sql
SELECT count(*) as c
FROM civicrm_activity a
LEFT JOIN civicrm_case_activity actjoin_case_id ON (actjoin_case_id.activity_id = a.id)
WHERE (((`a`.`activity_type_id` IN (1, 2, 3, 4, 5, 6, 9, 10, 11, 12, 19, 22, 34, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 67, 68, 69, 70, 71, 72, 73, 74))))
AND (((`a`.`id` IN (SELECT activity_id FROM civicrm_activity_contact WHERE contact_id IN (SELECT contact_id FROM civicrm_acl_contact_cache WHERE user_id = 148762)))))
AND (a.id IN (SELECT activity_id FROM civicrm_activity_contact WHERE contact_id = "136672"))
AND (actjoin_case_id.case_id IS NULL)
AND (a.is_current_revision = "1")
AND (a.activity_type_id IN ("1", "58", "59", "60", "61", "62", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20", "21", "22", "23", "24", "25", "26", "27", "28", "29", "30", "31",
"32", "33", "34", "35", "36", "37", "38", "39", "40", "41", "42", "43", "44", "45", "46", "47", "48", "49", "50", "51", "52", "53", "54", "55", "56", "57", "63", "64", "67", "68", "69", "70", "71", "72", "73", "74", "75"))
AND (a.is_test = "0")
AND (a.is_deleted = "0")
```
I removed the references to CiviCase and it went down to .25 seconds:
```sql
SELECT count(*) as c
FROM civicrm_activity a
WHERE (((`a`.`activity_type_id` IN (1, 2, 3, 4, 5, 6, 9, 10, 11, 12, 19, 22, 34, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 67, 68, 69, 70, 71, 72, 73, 74))))
AND (((`a`.`id` IN (SELECT activity_id FROM civicrm_activity_contact WHERE contact_id IN (SELECT contact_id FROM civicrm_acl_contact_cache WHERE user_id = 148762)))))
AND (a.id IN (SELECT activity_id FROM civicrm_activity_contact WHERE contact_id = "136672"))
AND (a.is_current_revision = "1")
AND (a.activity_type_id IN ("1", "58", "59", "60", "61", "62", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20", "21", "22", "23", "24", "25", "26", "27", "28", "29", "30", "31",
"32", "33", "34", "35", "36", "37", "38", "39", "40", "41", "42", "43", "44", "45", "46", "47", "48", "49", "50", "51", "52", "53", "54", "55", "56", "57", "63", "64", "67", "68", "69", "70", "71", "72", "73", "74", "75"))
AND (a.is_test = "0")
AND (a.is_deleted = "0")
```
This site went from 5.65 to 5.67 a day ago, and was updated to PHP 8.1.26 from some pre-8.1.25 version.
I don't know if anyone has insight into this, but I don't think I can move the CiviCase-specific code to an extension because a) this is API3 and b) there's no hook. I can at least make this not try to filter by CiviCase when CiviCase is disabled.5.69.0JonGoldJonGoldhttps://lab.civicrm.org/dev/core/-/issues/4821SearchKit - Unknown column 'Contact_ActivityContact_Activity_01.id' in 'on cl...2024-02-08T21:42:14ZsamuelsovSearchKit - Unknown column 'Contact_ActivityContact_Activity_01.id' in 'on clause'With the awesome new feature to allow a [join between two fields](https://github.com/civicrm/civicrm-core/pull/28112), we managed to get this error :
```sql
SELECT `a`.`id` AS `id`, `a`.`sort_name` AS `sort_name`, `a`.`contact_type` AS ...With the awesome new feature to allow a [join between two fields](https://github.com/civicrm/civicrm-core/pull/28112), we managed to get this error :
```sql
SELECT `a`.`id` AS `id`, `a`.`sort_name` AS `sort_name`, `a`.`contact_type` AS `contact_type:label`, `a`.`contact_sub_type` AS `contact_sub_type:label`, `Contact_ActivityContact_Activity_01`.`subject` AS `Contact_ActivityContact_Activity_01.subject`, `Contact_ActivityContact_Activity_01`.`id` AS `Contact_ActivityContact_Activity_01.id`
FROM civicrm_contact a
LEFT JOIN (`civicrm_activity_contact` `Contact_ActivityContact_Activity_01_via_activitycontact` INNER JOIN `civicrm_value_activity_fiel_4` `Activity_field_1` ON (`Contact_ActivityContact_Activity_01`.`id` = `Activity_field_1`.`entity_id`) INNER JOIN `civicrm_activity` `Contact_ActivityContact_Activity_01` ON (`Contact_ActivityContact_Activity_01_via_activitycontact`.`activity_id` = `Contact_ActivityContact_Activity_01`.`id`)) ON `Contact_ActivityContact_Activity_01_via_activitycontact`.`record_type_id` = "3" AND `Activity_field_1`.`whatever_7` = TIMESTAMPDIFF(YEAR, `a`.`birth_date`, CURDATE()) AND `Contact_ActivityContact_Activity_01_via_activitycontact`.`contact_id` = `a`.`id`
WHERE (`a`.`contact_type` = "Individual")
AND (`a`.`is_deleted` = "0")
ORDER BY `a`.`sort_name` ASC
LIMIT 50
OFFSET 0
[nativecode=1054 ** Unknown column 'Contact_ActivityContact_Activity_01.id' in 'on clause']
```
The simplest query to reproduce the issue is to :
- create a custom field on activity
- create a SK with main entity Contact and left join on ActivityContact with a condition on the custom field = another field
Here is the SK UI:
![Screenshot_2023-11-30_at_12-27-50_Contacts_test_CiviCRM_Sandbox_on_Drupal](/uploads/73c3c9a4599173f655330451c8e9b4cb/Screenshot_2023-11-30_at_12-27-50_Contacts_test_CiviCRM_Sandbox_on_Drupal.png)
And the API info:
```
{
"version": 4,
"select": [
"id",
"sort_name",
"contact_type:label",
"contact_sub_type:label",
"Contact_ActivityContact_Activity_01.subject"
],
"orderBy": {},
"where": [
[
"contact_type:name",
"=",
"Individual"
]
],
"groupBy": [],
"join": [
[
"Activity AS Contact_ActivityContact_Activity_01",
"LEFT",
"ActivityContact",
[
"id",
"=",
"Contact_ActivityContact_Activity_01.contact_id"
],
[
"Contact_ActivityContact_Activity_01.record_type_id:name",
"=",
"\"Activity Targets\""
],
[
"Contact_ActivityContact_Activity_01.Activity_field.whatever",
"=",
"age_years"
]
]
],
"having": []
}
```
Apparently, it's a problem in the order the query is done.
Instead of :
```sql
LEFT JOIN (
`civicrm_activity_contact` `Contact_ActivityContact_Activity_01_via_activitycontact`
INNER JOIN `civicrm_value_activity_fiel_4` `Activity_field_1`
ON (`Contact_ActivityContact_Activity_01`.`id` = `Activity_field_1`.`entity_id`)
INNER JOIN `civicrm_activity` `Contact_ActivityContact_Activity_01`
ON (`Contact_ActivityContact_Activity_01_via_activitycontact`.`activity_id` = `Contact_ActivityContact_Activity_01`.`id`)
)
```
In sql, moving the `civicrm_activity` join before the custom field table join solves it :
```sql
LEFT JOIN (
`civicrm_activity_contact` `Contact_ActivityContact_Activity_01_via_activitycontact`
INNER JOIN `civicrm_activity` `Contact_ActivityContact_Activity_01`
ON (`Contact_ActivityContact_Activity_01_via_activitycontact`.`activity_id` =
INNER JOIN `civicrm_value_activity_fiel_4` `Activity_field_1`
ON (`Contact_ActivityContact_Activity_01`.`id` = `Activity_field_1`.`entity_id`)
`Contact_ActivityContact_Activity_01`.`id`)
)
```colemanwcolemanwhttps://lab.civicrm.org/dev/core/-/issues/4820Contact ID is no longer available in Advanced Search2023-12-04T10:00:53ZJonGoldContact ID is no longer available in Advanced SearchThis regressed in Civi 5.67. See screenshot of 5.66 below.
I did a `git bisect` and traced this to https://github.com/civicrm/civicrm-core/pull/27854. I thought it would be a trivial fix and maybe it is but not at my current brain capa...This regressed in Civi 5.67. See screenshot of 5.66 below.
I did a `git bisect` and traced this to https://github.com/civicrm/civicrm-core/pull/27854. I thought it would be a trivial fix and maybe it is but not at my current brain capacity.
![Selection_2071](/uploads/3d8aaf0674b6ccd2d6aba2e9a8351ce4/Selection_2071.png)https://lab.civicrm.org/dev/core/-/issues/4816CiviMail: Bounce processing is broken with 5.672023-12-04T09:57:49ZDetlev SieberCiviMail: Bounce processing is broken with 5.67## Overview
CiviMail has implemented elaborated bounce processing features: When an email sent by CiviMail is not accepted by the recipient mail server, a bounce mail is sent to the bounce mail account configured in .../civicrm/admin/ma...## Overview
CiviMail has implemented elaborated bounce processing features: When an email sent by CiviMail is not accepted by the recipient mail server, a bounce mail is sent to the bounce mail account configured in .../civicrm/admin/mailSettings&reset=1
The scheduled job fetch_bounces is parsing these bounce mails, using the verp address.
Normally, the bounce mail will be moved to a mail folder called /CiviMail/processed, if it can be traced to an email sent by CiviMail.
If however the bounce mail cannot be connected to a mail sent via CiviMail, the bounce mail is moved to /CiviMail/ignored
The connection is done via the verp address of the bounce mail, e.g.:
[mail+b+\<civicrm_mailing_job.id\>+\<civicrm_mailing_event_queue.id\>+\<hash\>@](mailto:mail+b+10193+10096107+c7dd2e9e8eb2f242@digitalcourage.de)\<domain.org\>
Since 5.67 it seems that this functionality is broken:
Any bounce mails are moved to the ignored folder. No bounce processing is performed anymore.
This issue might be a duplicate of #4775
I have reproduced this on two different CiviCRM installs on WordPress.5.68.0https://lab.civicrm.org/dev/core/-/issues/4815Create Formbuilder page to view Queue status2023-11-30T11:40:03ZdamilareCreate Formbuilder page to view Queue statusWe need a page for CiviCRM administrators with Queue administration privilege to view the status of Civi Queues.
The page can be assigned this link: `https://{CIVI_DOMAIN}/civicrm/admin/queue`We need a page for CiviCRM administrators with Queue administration privilege to view the status of Civi Queues.
The page can be assigned this link: `https://{CIVI_DOMAIN}/civicrm/admin/queue`5.69.0https://lab.civicrm.org/dev/core/-/issues/48145.69 change? regression? improvement - contribution & membership amounts are ...2024-03-15T01:11:33Zeileen5.69 change? regression? improvement - contribution & membership amounts are separate line itemsI've realised that when purchasing a quick config membership with an additional contribution as per
![image](/uploads/be6d34b67ddfdac42681f1895ab40bc4/image.png)
In 5.60 only one line item was created - in this case the total is $100 me...I've realised that when purchasing a quick config membership with an additional contribution as per
![image](/uploads/be6d34b67ddfdac42681f1895ab40bc4/image.png)
In 5.60 only one line item was created - in this case the total is $100 membership + $15 tax + $10 contribution + $1.50 tax and only the tax_amount on the contribution record is wrong
![image](/uploads/c8a6a51b876b8f767b24db7810a217f1/image.png)
In 5.69 rc the current behaviour is to create 2 line items
![image](/uploads/f4319273e0c10e09cff4ed6b7a7c921f/image.png)
- this feels more correct to me and I am loath to change it back unless people want to push for that.
I should note the financial type of the current line item is currently the same as that configured for the contribution page - on the same page as the configuration of the contribution amount in question. Once again this feels more logical to me but it could pick up the financial type of the membership being purchased if that was the case people wanted to argue.
Lastly I should note that there is code in the form (which could do with testing) to ensure that if both are purchased then only the membership amount is put in the recurring contribution.5.69.0https://lab.civicrm.org/dev/core/-/issues/4812Drop php 7.3 in 5.70 after the 5.69 ESR release2023-12-13T17:32:03ZeileenDrop php 7.3 in 5.70 after the 5.69 ESR releaseIt has been a year since we dropped php 7.2 so we are staying a similar amount behind the php support schedule
https://lab.civicrm.org/dev/core/-/issues/3991It has been a year since we dropped php 7.2 so we are staying a similar amount behind the php support schedule
https://lab.civicrm.org/dev/core/-/issues/3991https://lab.civicrm.org/dev/core/-/issues/4811Angularjs.bootstrap behaves differently when opening in a popup on older CMSes2023-12-04T04:39:25ZseamusleeAngularjs.bootstrap behaves differently when opening in a popup on older CMSesOverview
----------------------------------------
When trying to have a form builder form integrated on a Smarty Page. On CMSes that ship by default older jQuery versions e.g. Drupal 7. The form builder form does not render correctly in ...Overview
----------------------------------------
When trying to have a form builder form integrated on a Smarty Page. On CMSes that ship by default older jQuery versions e.g. Drupal 7. The form builder form does not render correctly in the popup.
Reproduction steps
----------------------------------------
1. Create a basic Drupal 7 + CiviCRM site with buildkit
1. Clone the searchkit branch of the [Line Item editor Extension](https://lab.civicrm.org/extensions/lineitemedit/-/tree/searchkit?ref_type=heads)
1. Enable Line Item extension
4. Do a find contribution search and try and edit any contribution and see that the angular js table does not load correctly to list the line items. But if you open it in a new tab find it renders correctly
Environment information
----------------------------------------
* __CiviCRM:__ Master
* __CMS:__ Drupal 75.69.0colemanwcolemanwhttps://lab.civicrm.org/dev/core/-/issues/4807[php8] CRM_Core_Form_Tag::_entityTagValues seems to be in the wrong place2023-12-13T17:32:03ZDaveD[php8] CRM_Core_Form_Tag::_entityTagValues seems to be in the wrong placeThis class doesn't ever seem to get instantiated as its own form, and the property is always accessed from "outside" as `$form->_entityTagValues`. There are two actual forms that declare the property - those declarations were added a yea...This class doesn't ever seem to get instantiated as its own form, and the property is always accessed from "outside" as `$form->_entityTagValues`. There are two actual forms that declare the property - those declarations were added a year ago. The property has existed forever.
I'm thinking maybe it should live on CRM_Core_Form instead, or at least remove it from CRM_Core_Form_Tag and add it to the classes that call CRM_Core_Form_Tag functions. A larger refactor might instead make those classes contain an instance of CRM_Core_Form_Tag and then it could be protected inside there.
Also `_tagsetInfo`5.70.0https://lab.civicrm.org/dev/core/-/issues/4805[PHP 8.3] static fields syntax error2024-01-31T22:30:17Zjofranzfranz@systopia.de[PHP 8.3] static fields syntax error
```bash
civicrm-core (f8a214edfd8c888dec0922e2622d3e8a9ff66eb2) parallel-lint --no-progress -p php8.3 .
PHP 8.3.0 | 10 parallel jobs
Checked 4242 files in 11.2 seconds
Syntax error found in...
```bash
civicrm-core (f8a214edfd8c888dec0922e2622d3e8a9ff66eb2) parallel-lint --no-progress -p php8.3 .
PHP 8.3.0 | 10 parallel jobs
Checked 4242 files in 11.2 seconds
Syntax error found in 2 files
------------------------------------------------------------
Parse error: ./CRM/Mailing/Event/BAO/MailingEventForward.php:236
> 236 | static $fields = NULL;
Duplicate declaration of static variable $fields in ./CRM/Mailing/Event/BAO/MailingEventForward.php
------------------------------------------------------------
Parse error: ./CRM/Import/Parser.php:1131
> 1131 | static $fields = NULL;
Duplicate declaration of static variable $fields in ./CRM/Import/Parser.php
```
Slightly related: #3958https://lab.civicrm.org/dev/core/-/issues/4804SearchKit: New toolbar in SearchKit doesn't show for contacts entity2024-02-05T21:57:51ZTobias Voigttobias.voigt@civiservice.deSearchKit: New toolbar in SearchKit doesn't show for contacts entityThe new option in CiviCRM 5.67.0 to add a toolbar with custom buttons to SearchKits is awesome!
Anyway - while it seems to work for other entities (e.g. participants), it doesn't show up for SearchKits that are based on the contacts ent...The new option in CiviCRM 5.67.0 to add a toolbar with custom buttons to SearchKits is awesome!
Anyway - while it seems to work for other entities (e.g. participants), it doesn't show up for SearchKits that are based on the contacts entity.colemanwcolemanwhttps://lab.civicrm.org/dev/core/-/issues/4803Custom Fields on Campaign are hidden on validation2024-03-26T07:53:12Za.valllloveraCustom Fields on Campaign are hidden on validation## Overview
When trying to submit a new Campaign with a Type that have custom fields, if the valdator return some error/fields missing, the custom fields are hidden.
## Reproduction steps
1. Create some Custom Fields for a Campaign Ty...## Overview
When trying to submit a new Campaign with a Type that have custom fields, if the valdator return some error/fields missing, the custom fields are hidden.
## Reproduction steps
1. Create some Custom Fields for a Campaign Type. **Administer -\> Customize Data and Screens -\> Custom Fields**
2. Create new Campaign. **Campaigns-\> New Campaign**
3. Select the Campaign Type that have the custom fields but **don't input the title** (for easier validation). The custom fields appers at bottom.
4. Click **Save**
5. The custom fields are hidden because validator tells you to fill the Title field.
## Current behaviour
![Error Campaign.gif](/uploads/41a8748520c6037df7d5a7d502762670/Error_Campaign.gif)
## Expected behaviour
Custom fields should still remain after validation fails.
## Environment information
* **CiviCRM:** _Master/5.69.alpha1_https://lab.civicrm.org/dev/core/-/issues/4802Main contribution page - amounts entered with money formatting that is non-En...2023-11-27T20:32:14ZeileenMain contribution page - amounts entered with money formatting that is non-English are truncatedIf a contribution page is configured with an other_amount field then the value from that field is not passed through `cleanMoney()` & is potentially truncated
- eg. 7,90 becomes 7
I verified this in 5.60 so not a new regressionIf a contribution page is configured with an other_amount field then the value from that field is not passed through `cleanMoney()` & is potentially truncated
- eg. 7,90 becomes 7
I verified this in 5.60 so not a new regression5.69.0https://lab.civicrm.org/dev/core/-/issues/4799Autocomplete-Select options not saving/displaying properly2023-11-24T14:51:53ZbrienneAutocomplete-Select options not saving/displaying properlyOverview
----------------------------------------
Autocomplete-Select custom fields are not properly displaying when that field is viewed, but does show the selected option in edit mode.
Reproduction steps
------------------------------...Overview
----------------------------------------
Autocomplete-Select custom fields are not properly displaying when that field is viewed, but does show the selected option in edit mode.
Reproduction steps
----------------------------------------
1. Create a custom field of type ‘Autocomplete-Select’
1. Select an option for that field on a contact/contribution/ext. and **Save**
1. Note that the response does not display when viewing the field on that record
1. Click **Edit** and note that the selected option does display
![Selection_026](/uploads/a081103560d07c0726c43779471a35b9/Selection_026.png)
![Selection_027](/uploads/11ed0759d7e3c8d5103bdbeb049a2106/Selection_027.png)
Current behaviour
----------------------------------------
Custom fields of type ‘Autocomplete-Select’ are not displaying when in View mode, but do display when editing that field on a record.
The id of the OptionValue is what is getting saved for the field, instead of its value:
Getting the custom field from the example contact’s record:
```json
[
{
"Auotcomplete_save_test.Favorite_genre_of_rock_music": "1001",
"Auotcomplete_save_test.Favorite_genre_of_rock_music:name": null,
"Auotcomplete_save_test.Favorite_genre_of_rock_music:label": null
}
]
```
Getting the OptionValues for the custom field:
```json
[
{
"id": 1001,
"value": "1",
"label": "Heavy metal",
"name": "Heavy_metal"
},
{
"id": 1002,
"value": "2",
"label": "Hard rock",
"name": "Hard_rock"
},
{
"id": 1003,
"value": "3",
"label": "Punk rock",
"name": "Punk_rock"
},
]
```
Expected behaviour
----------------------------------------
The option selected for the Autocomplete-Select custom field should be displayed both in View and Edit modes.
Environment information
----------------------------------------
* __CiviCRM: 5.67.1, 5.68.beta1https://lab.civicrm.org/dev/core/-/issues/4797A regression? Can't assign case role in CiviCase2023-11-23T13:15:28ZtomrosenbloomA regression? Can't assign case role in CiviCaseI'm not able to assign (or re-assign) a case role to a case in CiviCase in the latest version - I can do this in our live Civi (5.64.4) but not in latest version 5.69.alpha1 either running locally or on the dmaster demo site.
Expected b...I'm not able to assign (or re-assign) a case role to a case in CiviCase in the latest version - I can do this in our live Civi (5.64.4) but not in latest version 5.69.alpha1 either running locally or on the dmaster demo site.
Expected behaviour:
1. create case, or find existing case in dashboard
2. click Manage, then expand Roles pane
3. click pencil icon next to a role
4. in dialogue box 'Assign <role>', select a contact using autocomplete
Current behaviour:
as above until step 4, where the dialogue box is broken - seems to be a plain text input instead of autocomplete, and dialogue cannot be dismissed with Save or Cancel.https://lab.civicrm.org/dev/core/-/issues/4796Cancel button on the "unsubscribe mailing" form doesn't work as expected.2024-01-05T03:42:40ZCésarCancel button on the "unsubscribe mailing" form doesn't work as expected.Overview
----------------------------------------
Hello,
The footer of a mailing (civicrm/admin/component?action=update&id=2) includes the token {action.optOutUrl}, but, if you create a new footer with the token {action.unsubscribeUrl...Overview
----------------------------------------
Hello,
The footer of a mailing (civicrm/admin/component?action=update&id=2) includes the token {action.optOutUrl}, but, if you create a new footer with the token {action.unsubscribeUrl} and send a mailing, when you click to unsubscribe from the group, a mailing is resent allowing you to resubscribe. In this last form "civicrm/mailing/resubscribe" if you click on the cancel button, you resubscribe.
Both the "next" and "cancel" buttons work the same way.
![Screenshot_from_2023-11-22_16-10-01](/uploads/3b2c5eb787317542ea5b9e4542c97579/Screenshot_from_2023-11-22_16-10-01.png)
* https://github.com/civicrm/civicrm-core/blob/5.63.3/templates/CRM/Mailing/Page/Resubscribe.tpl#L23
Reproduction steps
----------------------------------------
1. Add contact to group
2. Create/edit footer on: "civicrm/admin/component", add {action.unsubscribeUrl}
3. Send mailing test with new footer
4. Unsubscribe with token email
5. Access to new mail Resubscribe and click cancel button (Now you are rejoined to group)
Current behaviour
----------------------------------------
* When I click on the “here” link in the re-subscribe confirmation and then on button “Cancel”, we still get re-subscribed.
* The "next" and "cancel" buttons work the same way.
Expected behaviour
----------------------------------------
* Do nothing with cancel button (Cancel action)
Environment information
----------------------------------------
* __CiviCRM: 5.63
* __PHP: 7.4 / 8.1
* __CMS: Drupal5.69.0