CiviCRM Core issueshttps://lab.civicrm.org/dev/core/-/issues2018-11-15T08:11:29Zhttps://lab.civicrm.org/dev/core/-/issues/193Order API Throw an error when adding tax amount on line items2018-11-15T08:11:29Zomar_compucorpOrder API Throw an error when adding tax amount on line itemsOrder API not factoring in tax amounts when comparing against contribution total.
*Overview:*
When creating an Order using Order API a check is done to compare Contribution's total_amount against the sum of line item's line_total's. If ...Order API not factoring in tax amounts when comparing against contribution total.
*Overview:*
When creating an Order using Order API a check is done to compare Contribution's total_amount against the sum of line item's line_total's. If Contribution total amount and Line Items' total are not equal, Order creation will fail.
As we know:
1. The line item line_total *do not* include any tax. Tax will be recorded separately in line item tax_amount field.
2. The contribution total_amount *do* include tax. A separate contribution tax_amount field also records the amount of tax.
Since the validation only compares the sum of line_totals with contribution total_amount, whenever there is tax, the validation will fail.
For illustration consider following data set that should create 1 contribution with 2 line items for memberships.
```
order_data =
{
'is_pay_later': True,
'contact_id': 240L,
'payment_instrument_id': 6,
'line_items': [{
'line_item': {
'42': {
'price_field_value_id': 60L,
'price_field_id': 36L,
'entity_id': 1249L,
'tax_amount': 2.0,
'line_total': 10.0,
'financial_type_id': 2,
'label': 'General',
'entity_table': 'civicrm_membership',
'unit_price': 10,
'qty': '1'}}}, {
'line_item': {
'43': {
'price_field_value_id': 61L,
'price_field_id': 37L,
'entity_id': 1248L,
'tax_amount': 1.67,
'line_total': 8.33,
'financial_type_id': 2,
'label': 'Concession',
'entity_table': 'civicrm_membership',
'unit_price': '8.33',
'qty': '1'}}}],
'tax_amount': 3.67,
'total_amount': 22.0,
'contribution_recur_id': 605L,
'financial_type_id': 2,
'fee_amount': 0,
'payment_processor_id': 5L,
'receive_date': u'2019-08-01',
'contribution_status_id': 2}
```
*Current situation:*
Calling the Order API to create Order with given data results with "Line item total doesn't match with total amount". This is because total_amount (22.0) <> sum of line_totals (18.33)
*How should it be:*
The Line Items check should consider tax_amounts of line_items and order creation should succeed.https://lab.civicrm.org/dev/core/-/issues/194Search Builder greater than and lesser than operators for contribution total ...2018-12-09T21:15:34ZMatthias BärnthalerSearch Builder greater than and lesser than operators for contribution total amount omittedTo reproduce:
* Go to Search -> Search generator
* Choose Contribution -> Total Amount
* No greater than, lesser than, greater than equal, lesser than equal operators are present.
My guess is that the field gets treated as a String, th...To reproduce:
* Go to Search -> Search generator
* Choose Contribution -> Total Amount
* No greater than, lesser than, greater than equal, lesser than equal operators are present.
My guess is that the field gets treated as a String, therefore the operator is omitted in Builder.js
`// based on data type remove invalid operators e.g. IS EMPTY doesn't work with Boolean type column
if ((field in CRM.searchBuilder.fieldTypes) === true) {
if (CRM.searchBuilder.fieldTypes[field] == 'Boolean') {
CRM.searchBuilder.generalOperators = _.omit(CRM.searchBuilder.generalOperators, ['IS NOT EMPTY', 'IS EMPTY']);
}
else if (CRM.searchBuilder.fieldTypes[field] == 'String') {
CRM.searchBuilder.generalOperators = _.omit(CRM.searchBuilder.generalOperators, ['>', '<', '>=', '<=']);
}
}
buildOperator(operator, CRM.searchBuilder.generalOperators);`5.4.0https://lab.civicrm.org/dev/core/-/issues/195Add Contribution Counts to Sub-tabs2022-08-17T05:03:37ZCamilo RodríguezAdd Contribution Counts to Sub-tabs## Overview
It would be helpful to be able to see on each sub-tab a count of Contributions / Recurring Contributions, keeping the UX consistent with how the rest of tabs work on Contact's Detail View.
## How it Works Currently
1. Go to ...## Overview
It would be helpful to be able to see on each sub-tab a count of Contributions / Recurring Contributions, keeping the UX consistent with how the rest of tabs work on Contact's Detail View.
## How it Works Currently
1. Go to a Contact's detail view.
2. The **Contributions** tab shows also the count of contributions associated to the contact.
3. Clicking on the tab displays two sub-tabs, one for Contributions, the second one for Recurring Contributions.
4. Sub-tabs don't show number of contributions on each.
## How it Should Work
1. Go to a Contact's detail view.
2. The **Contributions** tab shows also the count of contributions associated to the contact.
3. Clicking on the tab displays two sub-tabs, one for Contributions, the second one for Recurring Contributions.
4. Sub-tabs show number of contributions on each. Count done for **Recurring Contributions** is done on active recurring contributions.https://lab.civicrm.org/dev/core/-/issues/196email signature not included in activity email2018-11-05T12:22:00Zlcdwebemail signature not included in activity emailto reproduce:
* go into your contact record and click the edit button
* below the email address click to expand the signature panel. enter a value and save the form.
* on the summary view you will now see "(signature)" in parens and can...to reproduce:
* go into your contact record and click the edit button
* below the email address click to expand the signature panel. enter a value and save the form.
* on the summary view you will now see "(signature)" in parens and can click to view the value
* click the actions button and select "send an email"
the signature should prepopulate in the email body field but does not.
this is a regression. the behavior works as expected in 4.6 but was lost somewhere in the 4.7/5.x cycle.lcdweblcdwebhttps://lab.civicrm.org/dev/core/-/issues/199Fix ACL on Group.get API2021-03-29T13:53:28ZMichael McAndrewFix ACL on Group.get APIBefore
------
ACL filtering was done after results were retrieved from the database, which in the majority of cases would lead to incorrect results being returned.
Consider the following scenario. 100 groups exist in the DB. A user has...Before
------
ACL filtering was done after results were retrieved from the database, which in the majority of cases would lead to incorrect results being returned.
Consider the following scenario. 100 groups exist in the DB. A user has access to the 100th group.
Group.get will return 'the first' 25 groups, filter them all, and return that no groups are available.
Aside from this being a problem in itself, it also causes paged API calls (e.g. the API call that populates the CiviMail recipients list of groups) to fail as they assume that there are no more records to return.
After
-----
If check permissions is checked and we do not have view all contacts, we add an extra where clause to `_civicrm_api3_basic_get`, ensuring that only visible groups are returned.https://lab.civicrm.org/dev/core/-/issues/204Add testcases to civicrm-core PR #112912021-09-13T00:08:27ZvarshithAdd testcases to civicrm-core PR #11291Ref. https://github.com/civicrm/civicrm-core/pull/11291
The above PR adds case tokens support to email activities.
We need test cases for the above PR to complete it.Ref. https://github.com/civicrm/civicrm-core/pull/11291
The above PR adds case tokens support to email activities.
We need test cases for the above PR to complete it.https://lab.civicrm.org/dev/core/-/issues/206Filter webform dropdown through relationship type2018-10-15T12:00:57ZshitijgFilter webform dropdown through relationship type**Overview:**
This ticket is targeted at improving the data filtering capabilities of the ‘Existing Contact’ field of the Webform CiviCRM.
With this new filtering - we will be able to filter the existing contact field with values deri...**Overview:**
This ticket is targeted at improving the data filtering capabilities of the ‘Existing Contact’ field of the Webform CiviCRM.
With this new filtering - we will be able to filter the existing contact field with values derived from a particular relation type that a contact has with another contact.
**How it works currently:**
Currently we have the ability to filter through Groups and Tags
We also currently have the ability for the existing contact field on the webform to autoload static value through a predefined relationship to another ‘existing contact’ field on the webform.
i.e.
If Contact 1 is the Case Client and has a relationship: ‘Employee of’ with Ashville School, we can add another contact field on the webform and enable the relationship fields on it to:
‘Employee of’.
![Screen_Shot_2018-06-25_at_18.39.01](/uploads/c00aa3024f6e72160d7f781b1778f302/Screen_Shot_2018-06-25_at_18.39.01.png)
We will also have to edit the ‘Existing Contact’ field and select it’s default value to load from a relationship.
![Screen_Shot_2018-06-25_at_18.40.02](/uploads/0b316d87ec5e6fb5055765411b4dea1e/Screen_Shot_2018-06-25_at_18.40.02.png)
This would mean that Contact 2 on the webform will be the value coming from the ‘Employee of’ relationship with Contact 1 (in this case - for our selected case client - it would be ‘Ashville School’)
In this way we are able to load the value from a relationship that 2 contacts have, however, we can not do this dynamically.
I.e.
Contact 3 (another contact on the webform) cannot be set to filter and give back a list of all the students at Ashville School (have a relationship ‘Student at’ with ‘Ashville School’, so that the user filling the form can select one of the students.
**How we would like to improve the functionality:**
With this new implementation, we will be able to filter values for an ‘Existing Contact’ field on the webform through specifying a relationship and relationship with.
Continuing from our previous example where:
Contact 1 - Joe Bloggs (Case Client)
Contact 2 - Ashville School (Has the relationship ‘Employer of’ with Joe Bloggs)
Contact 3 - We need a list of all students at Ashville School and be able to select this on the form
To achieve this - we will need the following configurations in the filters section of the ‘Existing Contact’ field:
![Screen_Shot_2018-06-25_at_18.36.55](/uploads/b5ab2bbe9d46659399bae4739b6010e3/Screen_Shot_2018-06-25_at_18.36.55.png)
In the above example, the user will be able to select:
Relationship Type - ‘Student at’
Contact - ‘Contact 2’
This would mean when the webform loads, it will populate all the students at Contact 2 (Ashville School) as option values for Contact 3.https://lab.civicrm.org/dev/core/-/issues/208Load case to webform with contactID, checksum and caseID in the URL2020-10-19T23:40:28ZshitijgLoad case to webform with contactID, checksum and caseID in the URL**Overview:**
This ticket is targeted at improving the case loading functionality for webforms.
We need to modify the webform to autoload the case onto a webform if contact id and checksum of the case manager (or anyone who has permiss...**Overview:**
This ticket is targeted at improving the case loading functionality for webforms.
We need to modify the webform to autoload the case onto a webform if contact id and checksum of the case manager (or anyone who has permission to see the case) and case id are present in the url.
**How it works currently:**
Case fields (except case roles) are currently loading on webforms. However, this is not the case when we use checksum of a user who has access to the case and send this case url to as that user in email.
This url has the contactID and checksum of the user who we are sending an email, and the caseID.
**How we would like to improve the functionality:**
By passing the contactID + checksum (of a user who has access to the case) and the case ID in the URL, the case will be accessible (preload in the webform) to the case manager (or anyone who has permission to see the case)https://lab.civicrm.org/dev/core/-/issues/209Case Scheduled Reminders2023-10-03T05:03:22ZshitijgCase Scheduled Reminders**User story:**
- As a CiviCRM administrator
- I would like to configure a scheduled reminder to be sent
- that will include the following tokens:
- All fields from table civicrm_case and associated case custom fields
- All contac...**User story:**
- As a CiviCRM administrator
- I would like to configure a scheduled reminder to be sent
- that will include the following tokens:
- All fields from table civicrm_case and associated case custom fields
- All contact tokens for the contact the scheduled reminder is being sent to as per normal scheduled reminders
- when a specific case type (or types) changes to a specific case status (or status’s)
- either immediately or after a desired period of time has passed from the change in status*
- to one or more case roles, groups of contacts or individual contacts
- so that I can have an email or sms sent to specific contacts when the case status changes to inform them about changes in the case.
**Wireframe:**
The wireframe in the original ticket is somewhat incomplete and doesn’t discuss
- The time period point and how it should work
- The case role’s filtering
As such I would suggest the following solution:
![8d2fca53-d8a0-4cfa-b208-4cc889ee09e0](/uploads/a292bb55efdea95398d0ca47e4b363d4/8d2fca53-d8a0-4cfa-b208-4cc889ee09e0.png)
**Notes:**
- If case type or case status is not selected then all case types and status should send the reminder.
- The “when” feature should operate such that if it is left blank then the reminder should be sent and only sent once but for cases meeting the criteria and the following when criteria:
- “After status change”
- Immediately after the status change takes place if that is the selected option and no other fields are filled in.
- Or the specified time after the status change takes place if a “number of hours or days after” is filled in
- Or on or after the “when” date if this is filled in
- If both the when and the “number of hours or days after” is filled in then the scheduled reminder should send only once on the earlier of those two dates. CiviCRM’s UX here is a bit nutty - 😳
- “Case start date”
- Immediately after the case start date for cases that meet that criteria if that is the selected option and no other fields are filled in.
- Or the specified time after the case start date if a “number of hours or days after” is filled in
- Or on or after the “when” date if this is filled in
- If both the when and the “number of hours or days after” is filled in then the scheduled reminder should send only once on the earlier of those two dates.
- “Case end date”
- Immediately after the case end date for cases that meet that criteria if that is the selected option and no other fields are filled in.
- Or the specified time after the case end date if a “number of hours or days after” is filled in
- Or on or after the “when” date if this is filled in
- If both the when and the “number of hours or days after” is filled in then the scheduled reminder should send only once on the earlier of those two dates.
- NICE TO HAVE: Can we also support any date type custom fields that are added to the case with the same logic and list those custom fields in the dropdown? i.e. create a case custom field “Court date” and then have that date in the scheduled reminder filters? Lower priority.
- Limit or add to case roles:
- Should allow user to select the case roles that the email will be sent to.https://lab.civicrm.org/dev/core/-/issues/212Contribution Details report fails when "Is not one of" condition is used for ...2018-07-05T23:11:11ZscardiniusContribution Details report fails when "Is not one of" condition is used for Groups field# how to reproduce
* run CiviCRM 5.1.2
* open Report > Contribution Reports > Contribution Details
* click on Filters tab
* scroll down to Groups field
* change condition to "Is not one of"
* choose at least one group
* click Refresh re...# how to reproduce
* run CiviCRM 5.1.2
* open Report > Contribution Reports > Contribution Details
* click on Filters tab
* scroll down to Groups field
* change condition to "Is not one of"
* choose at least one group
* click Refresh results
* result: DB Error: no such field
# sql
sql error `Unknown column 'group_temp_table.id' in 'where clause'`
```
[db_error: message="DB Error: no such field" code=-19 mode=callback callback=CRM_Core_Error::handle prefix="" info="
CREATE TEMPORARY TABLE civireport_contribution_detail_temp2 DEFAULT
CHARACTER SET utf8 COLLATE utf8_unicode_ci AS SELECT SQL_CALC_FOUND_ROWS contact_civireport.sort_name as civicrm_contact_sort_name, contact_civireport.id as civicrm_contact_id, email_civireport.email as c
ivicrm_email_email, phone_civireport.phone as civicrm_phone_phone, contribution_civireport.id as civicrm_contribution_contribution_id, contribution_civireport.financial_type_id as civicrm_contribution_fin
ancial_type_id, contribution_civireport.currency as civicrm_contribution_currency, contribution_civireport.receive_date as civicrm_contribution_receive_date, contribution_soft_civireport.amount as civicrm
_contribution_total_amount, 'Soft Credit' as civicrm_contribution_contribution_or_soft, address_civireport.country_id as civicrm_address_country_id
FROM civireport_contribution_detail_temp1 temp1_civireport
INNER JOIN civicrm_contribution contribution_civireport
ON temp1_civireport.civicrm_contribution_contribution_id = contribution_civireport.id
INNER JOIN civicrm_contribution_soft contribution_soft_civireport
ON contribution_soft_civireport.contribution_id = contribution_civireport.id
INNER JOIN civicrm_contact contact_civireport
ON contact_civireport.id = contribution_soft_civireport.contact_id
LEFT JOIN civicrm_phone phone_civireport
ON (contact_civireport.id =
phone_civireport.contact_id) AND
phone_civireport.is_primary = 1
LEFT JOIN civicrm_address address_civireport
ON (contact_civireport.id =
address_civireport.contact_id) AND
address_civireport.is_primary = 1
LEFT JOIN civicrm_email email_civireport
ON contact_civireport.id = email_civireport.contact_id AND
email_civireport.is_primary = 1
WHERE (1) AND ( contribution_civireport.contribution_status_id IN (1) )
AND group_temp_table.id IS NULL
GROUP BY contact_civireport.id, contribution_civireport.id
[nativecode=1054 ** Unknown column 'group_temp_table.id' in 'where clause']"
]
```5.5.0https://lab.civicrm.org/dev/core/-/issues/214Suppress inappropriate error when trying to schedule mailing for today2022-08-17T05:03:36ZJoeMurraySuppress inappropriate error when trying to schedule mailing for todayWhen trying to schedule a mailing, there are two fields: one for date and one for time. If you select today for date a popup error immediately says that 'Error
The scheduled date and time is in the past'. It would be better if this was d...When trying to schedule a mailing, there are two fields: one for date and one for time. If you select today for date a popup error immediately says that 'Error
The scheduled date and time is in the past'. It would be better if this was delayed somewhat, though there are many possibilities. User ends up thinking Civi doesn't know correct date.
How about if validation changed so that if date==today and time is null, then set time=now()+1 minute?Monish DebMonish Debhttps://lab.civicrm.org/dev/core/-/issues/215Contact Dashboard Personal Campaign Pages section repeats Campaign rows for e...2022-08-18T05:03:48ZAllenShawContact Dashboard Personal Campaign Pages section repeats Campaign rows for each user-created PCPLooks to me like a regression of [CRM-11340](https://issues.civicrm.org/jira/browse/CRM-11340).
**PR Raised https://github.com/civicrm/civicrm-core/pull/12369**
To reproduce on dmaster.demo.civicrm.org:
1. Ensure exixstence of at leas...Looks to me like a regression of [CRM-11340](https://issues.civicrm.org/jira/browse/CRM-11340).
**PR Raised https://github.com/civicrm/civicrm-core/pull/12369**
To reproduce on dmaster.demo.civicrm.org:
1. Ensure exixstence of at least 2 1 contriubution page with Personal Campaign Pages enabled; this recipe is easier if you remove the admin approval requirement, but that's not relevant to the issue.
2. As anonymous user, visit the URL to create your own PCP page for this campaign and complete the process.
3. Repeat step 2 to create a second PCP page for this campaign.
4. As admin, visit http://dmaster.demo.civicrm.org/civicrm/admin/pcp?reset=1&action=browse and observe there are at least two PCP pages for this campaign. Also ensure neither of these two pages is owned by the account you're currently logged in with.
5. Visit the user dashboard at http://dmaster.demo.civicrm.org/civicrm/user?reset=1, and observe this campaign is listed twice under "create a Personal Campaign Page", ass in attached screenshot:
![dmaster](/uploads/45adace7953442815335acdff567dbf6/dmaster.png)
Preliminary testing shows the following patch fixes the issue, but unsure of possible side effects:
```
diff --git a/CRM/PCP/BAO/PCP.php b/CRM/PCP/BAO/PCP.php
index b21a3a2..65ef434 100644
--- a/CRM/PCP/BAO/PCP.php
+++ b/CRM/PCP/BAO/PCP.php
@@ -184,7 +184,7 @@ FROM civicrm_pcp_block block
LEFT JOIN civicrm_pcp pcp ON pcp.pcp_block_id = block.id
WHERE block.is_active = 1
{$clause}
-GROUP BY block.id, pcp.id
+GROUP BY block.id
ORDER BY target_entity_type, target_entity_id
";
$pcpBlockDao = CRM_Core_DAO::executeQuery($query);
```Monish DebMonish Debhttps://lab.civicrm.org/dev/core/-/issues/221Inappropriate warning on preview page of empty custom data set2018-07-30T09:49:04ZmadhaviInappropriate warning on preview page of empty custom data setI'am using Civicrm version 5.2.2.
When a new empty custom data set is created and clicked on preview it gives following warning on the preview page:
![customDataPreview](/uploads/5c4116b36bdd37e3a090e70b3a31eb41/customDataPreview.png)
PR...I'am using Civicrm version 5.2.2.
When a new empty custom data set is created and clicked on preview it gives following warning on the preview page:
![customDataPreview](/uploads/5c4116b36bdd37e3a090e70b3a31eb41/customDataPreview.png)
PR here : https://github.com/civicrm/civicrm-core/pull/12392https://lab.civicrm.org/dev/core/-/issues/223Expose prefix and suffix in reports2018-07-24T00:24:18ZyashodhaExpose prefix and suffix in reportsAdd prefix and suffix to *getContactColumns* method.Add prefix and suffix to *getContactColumns* method.5.5.0yashodhayashodhahttps://lab.civicrm.org/dev/core/-/issues/3231Correct Mailing Report unique Count2022-04-22T15:51:27ZsunilCorrect Mailing Report unique CountMailing -> Scheduled and Sent Mailings -> Report
Unique Opens -> Report
Total Opens -> Report
Both Report show same count.Mailing -> Scheduled and Sent Mailings -> Report
Unique Opens -> Report
Total Opens -> Report
Both Report show same count.5.10https://lab.civicrm.org/dev/core/-/issues/2275.3 beta - cannot update custom group of fields without backtrace2018-07-03T14:10:12Zjamie5.3 beta - cannot update custom group of fields without backtraceTo reproduce:
* Create a custom group that is used for Activities and don't pick any activity types.
* Don't add any fields
* Edit the settings for the custom group and select an activity type for it to apply to
Result is a back trace ...To reproduce:
* Create a custom group that is used for Activities and don't pick any activity types.
* Don't add any fields
* Edit the settings for the custom group and select an activity type for it to apply to
Result is a back trace (but the changes are saved).
This seems to be a regression from c746070e750af03108bc267ed3a583a5943c0f97.
In particular - `CRM_Core_BAO_SchemaHandler::changeUniqueToIndex` is called from line 207. is_multiple is false (I'm not entirely sure what that means) which causes CRM_Core_BAO_SchemaHandler::changeUniqueToIndex to pass $dropUnique as FALSE, which then tries to drop a foreign key that doesn't exist.
If $dropUnique is TRUE there is no backtrace.
Thanks to everyone for the amazing 5.3 work - our first bug after a week of roll outs!
jamie
```
#0 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/Error.php(190): CRM_Core_Error::backtrace()
#1 /var/www/powerbase/sites/all/modules/civicrm/packages/PEAR.php(921): CRM_Core_Error::handle(Object(DB_Error))
#2 /var/www/powerbase/sites/all/modules/civicrm/packages/DB.php(985): PEAR_Error->__construct("DB Error: not found", -4, 16, (Array:2), " ALTER TABLE civicrm_value_proposal_info_8\nDROP INDEX `FK_civicrm_value_prop...")
#3 /var/www/powerbase/sites/all/modules/civicrm/packages/PEAR.php(575): DB_Error->__construct(-4, 16, (Array:2), " ALTER TABLE civicrm_value_proposal_info_8\nDROP INDEX `FK_civicrm_value_prop...")
#4 /var/www/powerbase/sites/all/modules/civicrm/packages/PEAR.php(223): PEAR->_raiseError(Object(DB_mysqli), NULL, -4, 16, (Array:2), " ALTER TABLE civicrm_value_proposal_info_8\nDROP INDEX `FK_civicrm_value_prop...", "DB_Error", TRUE)
#5 /var/www/powerbase/sites/all/modules/civicrm/packages/DB/common.php(1905): PEAR->__call("raiseError", (Array:7))
#6 /var/www/powerbase/sites/all/modules/civicrm/packages/DB/mysqli.php(933): DB_common->raiseError(-4, NULL, NULL, " ALTER TABLE civicrm_value_proposal_info_8\nDROP INDEX `FK_civicrm_value_prop...", "1091 ** Can't DROP 'FK_civicrm_value_proposal_info_8_entity_id'; check that c...")
#7 /var/www/powerbase/sites/all/modules/civicrm/packages/DB/mysqli.php(403): DB_mysqli->mysqliRaiseError()
#8 /var/www/powerbase/sites/all/modules/civicrm/packages/DB/common.php(1216): DB_mysqli->simpleQuery(" ALTER TABLE civicrm_value_proposal_info_8\nDROP INDEX `FK_civicrm_value_prop...")
#9 /var/www/powerbase/sites/all/modules/civicrm/packages/DB/DataObject.php(2443): DB_common->query(" ALTER TABLE civicrm_value_proposal_info_8\nDROP INDEX `FK_civicrm_value_prop...")
#10 /var/www/powerbase/sites/all/modules/civicrm/packages/DB/DataObject.php(1635): DB_DataObject->_query(" ALTER TABLE civicrm_value_proposal_info_8\nDROP INDEX `FK_civicrm_value_prop...")
#11 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/DAO.php(415): DB_DataObject->query(" ALTER TABLE civicrm_value_proposal_info_8\nDROP INDEX `FK_civicrm_value_prop...")
#12 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/DAO.php(1371): CRM_Core_DAO->query(" ALTER TABLE civicrm_value_proposal_info_8\nDROP INDEX `FK_civicrm_value_prop...", TRUE)
#13 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/BAO/SchemaHandler.php(411): CRM_Core_DAO::executeQuery(" ALTER TABLE civicrm_value_proposal_info_8\nDROP INDEX `FK_civicrm_value_prop...")
#14 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/BAO/CustomGroup.php(207): CRM_Core_BAO_SchemaHandler::changeUniqueToIndex("civicrm_value_proposal_info_8", "")
#15 /var/www/powerbase/sites/all/modules/civicrm/CRM/Custom/Form/Group.php(458): CRM_Core_BAO_CustomGroup::create((Array:16))
#16 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/Form.php(466): CRM_Custom_Form_Group->postProcess()
#17 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/StateMachine.php(160): CRM_Core_Form->mainProcess()
#18 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/QuickForm/Action/Next.php(61): CRM_Core_StateMachine->perform(Object(CRM_Custom_Form_Group), "next", "Next")
#19 /var/www/powerbase/sites/all/modules/civicrm/packages/HTML/QuickForm/Controller.php(203): CRM_Core_QuickForm_Action_Next->perform(Object(CRM_Custom_Form_Group), "next")
#20 /var/www/powerbase/sites/all/modules/civicrm/packages/HTML/QuickForm/Page.php(103): HTML_QuickForm_Controller->handle(Object(CRM_Custom_Form_Group), "next")
#21 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/Controller.php(351): HTML_QuickForm_Page->handle("next")
#22 /var/www/powerbase/sites/all/modules/civicrm/CRM/Custom/Page/Group.php(172): CRM_Core_Controller->run()
#23 /var/www/powerbase/sites/all/modules/civicrm/CRM/Custom/Page/Group.php(139): CRM_Custom_Page_Group->edit("8", 2)
#24 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/Invoke.php(309): CRM_Custom_Page_Group->run((Array:4), NULL)
#25 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/Invoke.php(84): CRM_Core_Invoke::runItem((Array:16))
#26 /var/www/powerbase/sites/all/modules/civicrm/CRM/Core/Invoke.php(52): CRM_Core_Invoke::_invoke((Array:4))
#27 /var/www/powerbase/sites/all/modules/civicrm/drupal/civicrm.module(445): CRM_Core_Invoke::invoke((Array:4))
#28 /var/www/powerbase/includes/menu.inc(527): civicrm_invoke("admin", "custom", "group")
#29 /var/www/powerbase/index.php(21): menu_execute_active_handler()
#30 {main}
```5.3.0https://lab.civicrm.org/dev/core/-/issues/228Option group disabled on update2018-07-11T00:47:58ZajesamsonOption group disabled on updateWhen updating option group attributes (excluding `is_active`), the updated option group gets disabled. This is because option group was [defaulted](https://github.com/civicrm/civicrm-core/blob/master/CRM/Core/BAO/OptionGroup.php#L95) to ...When updating option group attributes (excluding `is_active`), the updated option group gets disabled. This is because option group was [defaulted](https://github.com/civicrm/civicrm-core/blob/master/CRM/Core/BAO/OptionGroup.php#L95) to `FALSE` when adding or updating record without specifying desired `is_active` status.
![option_group](/uploads/d8291f18e46149d5852335749ca473e3/option_group.gif)
The desired result would have been leaving the `is_active` status untouched, if not required to be updated during attributes update.5.5.0https://lab.civicrm.org/dev/core/-/issues/230Saved Search : Set Mapping id to null on mapping delete2018-11-18T20:56:51ZsunilSaved Search : Set Mapping id to null on mapping deletecivicrm_saved_search -> mapping_id is FOREIGN key REFERENCES of civicrm_mapping (id).
When mapping have reference with saved search table. while deleting the mapping get SQL Error.civicrm_saved_search -> mapping_id is FOREIGN key REFERENCES of civicrm_mapping (id).
When mapping have reference with saved search table. while deleting the mapping get SQL Error.5.5.0https://lab.civicrm.org/dev/core/-/issues/232Contact types with double hyphens in 'name' field : searches not returning an...2018-07-26T14:57:01ZPradeep Nayakpradpnayak@gmail.comContact types with double hyphens in 'name' field : searches not returning any contactshhttps://lab.civicrm.org/dev/core/-/issues/234Upgrade Steps in 5.3.alpha1 may not have been run2018-10-14T01:01:14ZseamusleeUpgrade Steps in 5.3.alpha1 may not have been runDue to a bug in the upgrade process the upgrade steps in 5.3.alhpa1 may not have been run. We need to copy them to 5.3.0 and re-runDue to a bug in the upgrade process the upgrade steps in 5.3.alhpa1 may not have been run. We need to copy them to 5.3.0 and re-run5.4.0seamusleeseamuslee