CiviCRM Core issueshttps://lab.civicrm.org/dev/core/-/issues2019-10-12T16:11:35Zhttps://lab.civicrm.org/dev/core/-/issues/1309Contribution Dashboard still uses broken Open Flash Charts2019-10-12T16:11:35ZeileenContribution Dashboard still uses broken Open Flash ChartsReplacement chart not rendering on Contribution Dashboard @artfulrobot promised to make it beautiful againReplacement chart not rendering on Contribution Dashboard @artfulrobot promised to make it beautiful again5.20.0RichRichhttps://lab.civicrm.org/dev/core/-/issues/1295Per agreement in NYC sprint, add status check is_active to table2019-10-17T18:16:43ZeileenPer agreement in NYC sprint, add status check is_active to tablehttps://docs.google.com/document/d/1z1Lm-DUrri6xPzGXU37nLk5SfRjo4i9Elvx-lfbmK24/edit#heading=h.164d9ulc2oa3https://docs.google.com/document/d/1z1Lm-DUrri6xPzGXU37nLk5SfRjo4i9Elvx-lfbmK24/edit#heading=h.164d9ulc2oa35.20.0https://lab.civicrm.org/dev/core/-/issues/1286Do not escape html in report header and footers on API create2020-01-20T10:52:39ZMichael McAndrewDo not escape html in report header and footers on API createReportInstance.create escapes the HTML when inserting into the DB (and when retreiving, it seems) but other parts of the UI do not.
`civicrm_report_instance.header` and `civicrm_report_instance.footer` both contain HTML that (if I am fo...ReportInstance.create escapes the HTML when inserting into the DB (and when retreiving, it seems) but other parts of the UI do not.
`civicrm_report_instance.header` and `civicrm_report_instance.footer` both contain HTML that (if I am following https://lab.civicrm.org/dev/core/blob/master/CRM/Utils/API/HTMLInputCoder.php correctly - @colemanw - you touched that file recently) should not be escaped.
Adding 'header' and 'footer' to the list of fields that should not be escaped fixes the issue.
Aside: `CRM_Utils_API_HTMLInputCoder::getSkipFields()` seems flawed in that it does not specify the entity of the field that is to be ignored. Thankfully in this instance, the CiviCRM DB schema 'header' and 'footer' are only used the civicrm_report_instance but it feels like this class could end up inadvertently not escaping html that should be escaped (and maybe that is a potential security issue?)5.23.0colemanwcolemanwhttps://lab.civicrm.org/dev/core/-/issues/1166Update Country list: change Macedonia, Republic of into North Macedonia2019-12-03T08:07:43ZBetty DolfingUpdate Country list: change Macedonia, Republic of into North MacedoniaI understand ([see stackexchange question](https://civicrm.stackexchange.com/questions/31577/countries-up-to-date)) that the country list in CiviCRM is [maintained manually](https://github.com/civicrm/civicrm-core/blob/5.15.2/xml/templat...I understand ([see stackexchange question](https://civicrm.stackexchange.com/questions/31577/countries-up-to-date)) that the country list in CiviCRM is [maintained manually](https://github.com/civicrm/civicrm-core/blob/5.15.2/xml/templates/civicrm_country.tpl#L172).
In the iso 3166-1 list, Macedonia, Republic of is now called: **North Macedonia**
Can this be changed in the country list in CiviCRM?5.21.0seamusleeseamusleehttps://lab.civicrm.org/dev/core/-/issues/1143Field Names now Reserved Words in MySQL82020-01-09T00:12:27ZJoeMurrayField Names now Reserved Words in MySQL8The new reserved words includes two which we use as field names:
- description
- grouping
While our code to create the fields will work because it uses ` to quote them as identifiers, we'll likely want to either change these names or go...The new reserved words includes two which we use as field names:
- description
- grouping
While our code to create the fields will work because it uses ` to quote them as identifiers, we'll likely want to either change these names or go through the code base and add the backtick quotes everywhere. Either approach will still mean that extensions will have to make changes to become MySQL 8.0 compatible. Using backticks will mean that extensions can continue to run on earlier versions of MySQL, and is likely the better approach. We don't want to force all extension maintainers to change references to these fields all at once when only a small number of installations will be using MySQL 8.0.
Decision: use backticks.5.23.0Monish DebMonish Debhttps://lab.civicrm.org/dev/core/-/issues/1142Upgrade test infrastructure to support 'edge' versions of dependencies like M...2020-01-08T01:52:11ZJoeMurrayUpgrade test infrastructure to support 'edge' versions of dependencies like MySQL8@totten wrote:
> we currently check releases using a matrix with `min` and `max` columns
>
> if we expect civicrm to be compatible already (and/or that updates will be quick and straight-forward), then we can use KISS approach and just...@totten wrote:
> we currently check releases using a matrix with `min` and `max` columns
>
> if we expect civicrm to be compatible already (and/or that updates will be quick and straight-forward), then we can use KISS approach and just bump up max (`mysql57` => `mysql80`)
>
> otoh, if the process is going to take longer, then we should add a new column (`min`, `max`, `edge`)
>
> (note: adding an `edge` column could also be useful wrt to phasing-in support for `php73`)
>
> ... it would mean that reports of errors for infrastructure that is on the edge of getting support are not treated as blockers, and are identifiable as edge errors
Once an edge technology dependency like MySQL 8 or PHP 7.3 are deemed ready to be declared supported, the max column will change, and the edge column will change to NULL or perhaps the next higher version if people are prepared to start work on that.
This issue is focused on adding edge support to the matrix through a new column, and everything that entails in the build infrastructure and error reporting.
In order to do that, MySQL8 happens to be the first edge version to be incorporated. Issues specific to getting MySQL8.0 testing working on infrastructure will be managed at https://lab.civicrm.org/dev/core/issues/1144. Issues regarding MySQL8 compatibility are being managed via the meta issue https://lab.civicrm.org/dev/core/issues/392.
PHP73 is expected to be the next edge dependency.5.23.0tottentottenhttps://lab.civicrm.org/dev/core/-/issues/1123Changing the label for the Inbound Email activity type lets you edit/delete t...2019-09-07T21:07:07ZDaveDChanging the label for the Inbound Email activity type lets you edit/delete them even if the permission disallowsThis is related to dev/core#1116 but I'd like to start with this one first since it's more contained and allows removing a confusing variable that is only ever used once and used incorrectly.
1. To reproduce, set the permission so that ...This is related to dev/core#1116 but I'd like to start with this one first since it's more contained and allows removing a confusing variable that is only ever used once and used incorrectly.
1. To reproduce, set the permission so that editing inbound emails is disallowed. Will probably already be like this by default.
2. Change the activity type label for Inbound Email.
3. Go to a contact's activities tab and click the view link for an inbound email. On the popup there's now edit and delete buttons whereas before there weren't.
4. Click the edit button, make your edit, and save.
The problem is this line in https://github.com/civicrm/civicrm-core/blob/5.15.1/templates/CRM/Activity/Form/Activity.tpl#L252
`{if $action eq 4 && ($activityTName neq 'Inbound Email' || $allow_edit_inbound_emails == 1)}`
$activityTName (which is different than $activityTypeName, although it has the same value) is actually the label, and so if you've changed the label the comparison doesn't work.
This is the only place this variable is used.5.18.0https://lab.civicrm.org/dev/core/-/issues/1058Display bug for Checkboxes Custom field on Event Confirm / Thank you pages2019-11-29T15:07:45ZsamuelsovDisplay bug for Checkboxes Custom field on Event Confirm / Thank you pagesOn event registration form, check some checkboxes on a checkboxes custom field :
![Screenshot_2019-06-19_-_Event_with_custom_checkboxes](/uploads/ff1f5cc9fb3575f6ace441d4c8355af7/Screenshot_2019-06-19_-_Event_with_custom_checkboxes.png)...On event registration form, check some checkboxes on a checkboxes custom field :
![Screenshot_2019-06-19_-_Event_with_custom_checkboxes](/uploads/ff1f5cc9fb3575f6ace441d4c8355af7/Screenshot_2019-06-19_-_Event_with_custom_checkboxes.png)
On confirm / thank you, the wrong label is chown :
![Screenshot_2019-06-19_Event_with_custom_checkboxes_-_confirm](/uploads/cad6321211977c0a3ef5af0fb1aa16d1/Screenshot_2019-06-19_Event_with_custom_checkboxes_-_confirm.png)5.16.0https://lab.civicrm.org/dev/core/-/issues/959Expose contribution page in Contribution Summary report2019-05-24T01:27:11ZyashodhaExpose contribution page in Contribution Summary reportExpose contribution page in Contribution Summary reportExpose contribution page in Contribution Summary report5.15.0yashodhayashodhahttps://lab.civicrm.org/dev/core/-/issues/787Auto-complete search results not consistent with other searches2020-03-16T20:27:10ZyashodhaAuto-complete search results not consistent with other searchesAuto-complete (custom data on contacts) search results not consistent with other searches if the searched string has a space.
(check screenshot)![search](/uploads/8047fab578e9e63da65526701a88682d/search.png)
The quick search result is ri...Auto-complete (custom data on contacts) search results not consistent with other searches if the searched string has a space.
(check screenshot)![search](/uploads/8047fab578e9e63da65526701a88682d/search.png)
The quick search result is right and the auto-complete should also show 1 result only.5.25.0yashodhayashodhahttps://lab.civicrm.org/dev/core/-/issues/785Differentiate smart group from regular group using icon in select2 field2020-07-27T19:47:10ZMonish DebDifferentiate smart group from regular group using icon in select2 fieldCurrently there is no way to tell which group is smart or regular group from UI. It would be ideal to use icon against such smart group options to differentiate them from regular ones.Currently there is no way to tell which group is smart or regular group from UI. It would be ideal to use icon against such smart group options to differentiate them from regular ones.5.29.0Monish DebMonish Debhttps://lab.civicrm.org/dev/core/-/issues/781Contact Display Name vs Email Greeting in Workflow templates2019-10-23T20:22:53ZMichael LabriolaContact Display Name vs Email Greeting in Workflow templatesI noticed that some of the workflow templates use contact.display_name in the greeting and some of them use contact.email_greeting. It would make sense to me that they all use contact.email_greeting. From what I can tell these template...I noticed that some of the workflow templates use contact.display_name in the greeting and some of them use contact.email_greeting. It would make sense to me that they all use contact.email_greeting. From what I can tell these templates are part of civicrm_generated.mysql file, which is quite large. I created a fork and updated the several places where display_name is still being used. Is submitting a merge request something a general user can do here?
Thanks!5.20.0https://lab.civicrm.org/dev/core/-/issues/779Support token for participant id in scheduled reminder2021-10-12T02:22:06ZyashodhaSupport token for participant id in scheduled reminderCurrently, the participant id token is not available for scheduled reminder.
This is especially useful if the user need to be sent Self-service Registration Update forms
https://yoursite/civicrm/event/selfsvcupdate?reset=1&pid=xCurrently, the participant id token is not available for scheduled reminder.
This is especially useful if the user need to be sent Self-service Registration Update forms
https://yoursite/civicrm/event/selfsvcupdate?reset=1&pid=x5.43.0yashodhayashodhahttps://lab.civicrm.org/dev/core/-/issues/778Sales tax and Vat issue within memberships - membership fee increases incorre...2021-02-23T00:47:09ZgibsonoliverSales tax and Vat issue within memberships - membership fee increases incorrectly when the membership has an errorWhen sales tax is enabled (as per https://docs.civicrm.org/user/en/latest/contributions/sales-tax-and-vat/) there is an issue.
- Tax and invoicing is enabled
- A sales tax financial account type has been created
- This new financial acco...When sales tax is enabled (as per https://docs.civicrm.org/user/en/latest/contributions/sales-tax-and-vat/) there is an issue.
- Tax and invoicing is enabled
- A sales tax financial account type has been created
- This new financial account type has been assigned to the Member Dues financial type (so all memberships have the sales tax applied).
If you then add a new membership via the CRM member menu.
Then assign it to a contact, choose a membership type (which has a fee) and create an error deliberately (e.g. choose a membership end date before the start date).
The membership fee will then change upwards automatically to an incorrect amount.
And if you try to save the membership again with a deliberate error the membership price increases again. An again etc.
This has been recreated on the CiviCRM sandbox demo and I've attached a screenshot of a $100 membership price increasing.![Capture](/uploads/33f62e932c022d0efa680524e492332b/Capture.PNG)5.36.0https://lab.civicrm.org/dev/core/-/issues/774Changing the LABEL for a relationship type causes an error when creating a ne...2019-11-07T03:35:25ZDaveDChanging the LABEL for a relationship type causes an error when creating a new case that has that relationship/role set as CreatorTo reproduce, and I can reproduce this on dmaster.demo.civicrm.org:
1. Look in a case type definition to see which role is checked as "assign to creator".
2. Under admin - customize data - relationship types, change the label(s) for the ...To reproduce, and I can reproduce this on dmaster.demo.civicrm.org:
1. Look in a case type definition to see which role is checked as "assign to creator".
2. Under admin - customize data - relationship types, change the label(s) for the relationship type to something else.
3. Create a new case with the given case type.
4. Fatal error.
**It seems to ultimately come from here, where it looks up LABEL instead of NAME:
https://github.com/civicrm/civicrm-core/blob/master/CRM/Case/XMLProcessor.php#L114**
The allRelationshipTypes() function seems to only be used in two places, and both seem to be trying to match on label when it should be name, so the fix is probably just change 'label' to 'name'.
But then I'm wondering if any existing configs that depend on label will suddenly break, and taking a step back, this label vs name mismatch has come up a few times over the years in a few places so I'm wondering if fighting it is just postponing the problem. But maybe that should be a separate issue: i.e. if "name" was an integer or goofy string, or the field were named something like "key", a recurrence of the problem would be more obvious.5.20.0https://lab.civicrm.org/dev/core/-/issues/766New Event using a template - clicking "Continue" doesn't save custom data2022-04-22T16:22:26ZkenNew Event using a template - clicking "Continue" doesn't save custom dataWhen creating a New Event from an Event Template, and entering custom data for the event, hitting "Continue" doesn't save the custom data. This happens for me on 5.10.4, on the CiviHosting demo which is running 5.10.0, and the CiviCRM Sa...When creating a New Event from an Event Template, and entering custom data for the event, hitting "Continue" doesn't save the custom data. This happens for me on 5.10.4, on the CiviHosting demo which is running 5.10.0, and the CiviCRM Sandbox running 5.12.alpha1.
**How to reproduce**
1. Add a custom field to Event entities
2. Click _Events > New event_
3. Choose an Event Template
4. Enter the mandatory fields _and_ the custom data
5. Click _Continue_
6. Reload the page to force CiviCRM to fetch the event from the database
7. Visit the _Info and Settings_ tab
8. The custom data is unset
**Hint**
In my debugger I had a breakpoint in my implementation of _hook_civicrm_pre()_ and this didn't trigger when _Continue_ was pressed, but did when _Save_ or _Save and Done_ were pressed. If _Continue_ bypasses _pre()_ then perhaps it skips the Custom Data too?5.39.0https://lab.civicrm.org/dev/core/-/issues/754Fatal db error in search (with ONLY_FULL_GROUP_BY)2019-09-16T17:49:43ZbjoernFatal db error in search (with ONLY_FULL_GROUP_BY)CiviCRM-Version 5.10.3
MySQL-Version: 5.7.25
PHP-Version: 7.2
Steps to reproduce:
1. Select Search / Find Contacts
2. Leave Field "Name or Email" empty to get at least 2 Pages with results.
3. Click on the page-up button on the top rig...CiviCRM-Version 5.10.3
MySQL-Version: 5.7.25
PHP-Version: 7.2
Steps to reproduce:
1. Select Search / Find Contacts
2. Leave Field "Name or Email" empty to get at least 2 Pages with results.
3. Click on the page-up button on the top right corner.
Popup appears with message:
`Network Error
Unable to reach the server. Please refresh this page in your browser and try again.`
Error message of the response:
`DB Error: unknown error
Return to home page.`
CiviCRM Error-log:
```SQL
SELECT
contact_a.id as contact_id,
contact_a.contact_type as `contact_type`,
contact_a.contact_sub_type as `contact_sub_type`,
contact_a.sort_name as `sort_name`,
contact_a.display_name as `display_name`,
contact_a.do_not_email as `do_not_email`,
contact_a.do_not_phone as `do_not_phone`,
contact_a.do_not_mail as `do_not_mail`,
contact_a.do_not_sms as `do_not_sms`,
contact_a.do_not_trade as `do_not_trade`,
contact_a.is_opt_out as `is_opt_out`,
contact_a.legal_identifier as `legal_identifier`,
contact_a.external_identifier as `external_identifier`,
contact_a.nick_name as `nick_name`,
contact_a.legal_name as `legal_name`,
contact_a.image_URL as `image_URL`,
contact_a.preferred_communication_method as `preferred_communication_method`,
contact_a.preferred_language as `preferred_language`,
contact_a.preferred_mail_format as `preferred_mail_format`,
contact_a.first_name as `first_name`,
contact_a.middle_name as `middle_name`,
contact_a.last_name as `last_name`,
contact_a.prefix_id as `prefix_id`,
contact_a.suffix_id as `suffix_id`,
contact_a.formal_title as `formal_title`,
contact_a.communication_style_id as `communication_style_id`,
contact_a.job_title as `job_title`,
contact_a.gender_id as `gender_id`,
contact_a.birth_date as `birth_date`,
contact_a.is_deceased as `is_deceased`,
contact_a.deceased_date as `deceased_date`,
contact_a.household_name as `household_name`,
IF ( contact_a.contact_type = 'Individual', NULL, contact_a.organization_name ) as organization_name,
contact_a.sic_code as `sic_code`,
contact_a.is_deleted as `contact_is_deleted`,
IF ( contact_a.contact_type = 'Individual', contact_a.organization_name, NULL ) as current_employer,
civicrm_address.id as address_id,
civicrm_address.street_address as `street_address`,
civicrm_address.supplemental_address_1 as `supplemental_address_1`,
civicrm_address.supplemental_address_2 as `supplemental_address_2`,
civicrm_address.supplemental_address_3 as `supplemental_address_3`,
civicrm_address.city as `city`,
civicrm_address.postal_code_suffix as `postal_code_suffix`,
civicrm_address.postal_code as `postal_code`,
civicrm_address.geo_code_1 as `geo_code_1`,
civicrm_address.geo_code_2 as `geo_code_2`,
civicrm_address.state_province_id as state_province_id,
civicrm_address.country_id as country_id,
civicrm_phone.id as phone_id,
civicrm_phone.phone_type_id as phone_type_id,
civicrm_phone.phone as `phone`,
civicrm_email.id as email_id,
civicrm_email.email as `email`,
civicrm_email.on_hold as `on_hold`,
civicrm_im.id as im_id,
civicrm_im.provider_id as provider_id,
civicrm_im.name as `im`,
civicrm_worldregion.id as worldregion_id,
civicrm_worldregion.name as `world_region`,
(CASE
WHEN contact_a.id = 14799 THEN 0
WHEN contact_a.id = 17549 THEN 1
.
.
.
.
WHEN contact_a.id = 23911 THEN 47
WHEN contact_a.id = 23915 THEN 48
WHEN contact_a.id = 23048 THEN 49
END
) AS _wgt
FROM civicrm_contact contact_a
LEFT JOIN civicrm_address ON ( contact_a.id = civicrm_address.contact_id AND civicrm_address.is_primary = 1 )
LEFT JOIN civicrm_email ON (contact_a.id = civicrm_email.contact_id AND civicrm_email.is_primary = 1)
LEFT JOIN civicrm_phone ON (contact_a.id = civicrm_phone.contact_id AND civicrm_phone.is_primary = 1)
LEFT JOIN civicrm_im ON (contact_a.id = civicrm_im.contact_id AND civicrm_im.is_primary = 1)
LEFT JOIN civicrm_country ON civicrm_address.country_id = civicrm_country.id
LEFT JOIN civicrm_worldregion ON civicrm_country.region_id = civicrm_worldregion.id
WHERE (contact_a.is_deleted = 0)
AND contact_a.id IN (14799,17549, .... ,23915,23048)
GROUP BY contact_a.id ORDER BY _wgt
[nativecode=1055 ** Expression #37 of SELECT list is not in GROUP BY clause and contains nonaggregated column '*****.civicrm_address.id' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by]
```5.15.0https://lab.civicrm.org/dev/core/-/issues/723File custom fields cause a fatal error when trying to merge2019-05-30T21:47:13ZtommyboboFile custom fields cause a fatal error when trying to mergeIf you are trying to merge a contact with a custom field that is a file, if the contact that will be deleted is passing a file to the remain contact, the merge will fail, generate a fatal error, and lose all the custom data in the set in...If you are trying to merge a contact with a custom field that is a file, if the contact that will be deleted is passing a file to the remain contact, the merge will fail, generate a fatal error, and lose all the custom data in the set including the file.
To recreate:
1. Create a contact custom field that accepts a file.
2. Add files to one or two contact records.
3. Merge a contact with a file into another contact
4. Fatal Error occurs. All files are no longer attached to the custom fields. The contact to be deleted loses all the custom fields. While the remaining contact looses only the file.
If the contact that is to remain has no image the error message is
> **No record found for given file ID - 0 and entity ID - 203**
The Entity ID is the Contact ID of the remaining contact
> Feb 13 16:13:23 [info] $backTrace = #0 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Error.php(381): CRM_Core_Error::backtrace("backTrace", TRUE)
> #1 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/BAO/File.php(234): CRM_Core_Error::fatal("No record found for given file ID - 0 and entity ID - 203")
> #2 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Dedupe/Merger.php(1723): CRM_Core_BAO_File::deleteFileReferences(NULL, "203", 9)
> #3 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Contact/Form/Merge.php(289): CRM_Dedupe_Merger::moveAllBelongings("203", "204", (Array:11))
> #4 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Form.php(489): CRM_Contact_Form_Merge->postProcess()
> #5 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/StateMachine.php(160): CRM_Core_Form->mainProcess()
> #6 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/QuickForm/Action/Next.php(61): CRM_Core_StateMachine->perform(Object(CRM_Contact_Form_Merge), "next", "Next")
> #7 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/HTML/QuickForm/Controller.php(203): CRM_Core_QuickForm_Action_Next->perform(Object(CRM_Contact_Form_Merge), "next")
> #8 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/HTML/QuickForm/Page.php(103): HTML_QuickForm_Controller->handle(Object(CRM_Contact_Form_Merge), "next")
> #9 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Controller.php(351): HTML_QuickForm_Page->handle("next")
> #10 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Utils/Wrapper.php(113): CRM_Core_Controller->run()
> #11 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(282): CRM_Utils_Wrapper->run("CRM_Contact_Form_Merge", "Merge Contact", (Array:0))
> #12 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(84): CRM_Core_Invoke::runItem((Array:13))
> #13 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(52): CRM_Core_Invoke::_invoke((Array:3))
> #14 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm.php(1240): CRM_Core_Invoke::invoke((Array:3))
> #15 /srv/www/demo19/public_html/wp-includes/class-wp-hook.php(298): CiviCRM_For_WordPress->invoke("")
> #16 /srv/www/demo19/public_html/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters("", (Array:1))
> #17 /srv/www/demo19/public_html/wp-includes/plugin.php(453): WP_Hook->do_action((Array:1))
> #18 /srv/www/demo19/public_html/wp-admin/admin.php(222): do_action("toplevel_page_CiviCRM")
> #19 {main}
If the remaining contact has a file that will be overwritten.
>** DB Error: syntax error**
> [code] => -2
> [message] => DB Error: syntax error
> [mode] => 16
> [debug_info] => UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203 [nativecode=1064 ** You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'WHERE entity_id = 203' at line 1]
> [type] => DB_Error
> [user_info] => UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203 [nativecode=1064 ** You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'WHERE entity_id = 203' at line 1]
> [to_string] => [db_error: message="DB Error: syntax error" code=-2 mode=callback callback=CRM_Core_Error::handle prefix="" info="UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203 [nativecode=1064 ** You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'WHERE entity_id = 203' at line 1]"]
> )
> #1 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/PEAR.php(921): CRM_Core_Error::handle(Object(DB_Error))
> #2 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/DB.php(985): PEAR_Error->__construct("DB Error: syntax error", -2, 16, (Array:2), "UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203 [native...")
> #3 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/PEAR.php(575): DB_Error->__construct(-2, 16, (Array:2), "UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203 [native...")
> #4 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/PEAR.php(223): PEAR->_raiseError(Object(DB_mysqli), NULL, -2, 16, (Array:2), "UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203 [native...", "DB_Error", TRUE)
> #5 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/DB/common.php(1907): PEAR->__call("raiseError", (Array:7))
> #6 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/DB/mysqli.php(933): DB_common->raiseError(-2, NULL, NULL, "UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203 [native...", "1064 ** You have an error in your SQL syntax; check the manual that correspon...")
> #7 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/DB/mysqli.php(403): DB_mysqli->mysqliRaiseError()
> #8 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/DB/common.php(1216): DB_mysqli->simpleQuery("UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203")
> #9 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/DB/DataObject.php(2415): DB_common->query("UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203")
> #10 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/DB/DataObject.php(1607): DB_DataObject->_query("UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203")
> #11 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/DAO.php(438): DB_DataObject->query("UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203")
> #12 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/DAO.php(1413): CRM_Core_DAO->query("UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203", TRUE)
> #13 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Dedupe/Merger.php(1736): CRM_Core_DAO::executeQuery("UPDATE civicrm_value_test_info_4 SET image_9 = WHERE entity_id = 203")
> #14 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Contact/Form/Merge.php(289): CRM_Dedupe_Merger::moveAllBelongings("203", "204", (Array:10))
> #15 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Form.php(489): CRM_Contact_Form_Merge->postProcess()
> #16 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/StateMachine.php(160): CRM_Core_Form->mainProcess()
> #17 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/QuickForm/Action/Next.php(61): CRM_Core_StateMachine->perform(Object(CRM_Contact_Form_Merge), "next", "Next")
> #18 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/HTML/QuickForm/Controller.php(203): CRM_Core_QuickForm_Action_Next->perform(Object(CRM_Contact_Form_Merge), "next")
> #19 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/packages/HTML/QuickForm/Page.php(103): HTML_QuickForm_Controller->handle(Object(CRM_Contact_Form_Merge), "next")
> #20 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Controller.php(351): HTML_QuickForm_Page->handle("next")
> #21 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Utils/Wrapper.php(113): CRM_Core_Controller->run()
> #22 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(282): CRM_Utils_Wrapper->run("CRM_Contact_Form_Merge", "Merge Contact", (Array:0))
> #23 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(84): CRM_Core_Invoke::runItem((Array:13))
> #24 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(52): CRM_Core_Invoke::_invoke((Array:3))
> #25 /srv/www/demo19/public_html/wp-content/plugins/civicrm/civicrm.php(1240): CRM_Core_Invoke::invoke((Array:3))
> #26 /srv/www/demo19/public_html/wp-includes/class-wp-hook.php(298): CiviCRM_For_WordPress->invoke("")
> #27 /srv/www/demo19/public_html/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters("", (Array:1))
> #28 /srv/www/demo19/public_html/wp-includes/plugin.php(453): WP_Hook->do_action((Array:1))
> #29 /srv/www/demo19/public_html/wp-admin/admin.php(222): do_action("toplevel_page_CiviCRM")5.15.0https://lab.civicrm.org/dev/core/-/issues/715Cannot delete relationship type through UI2019-02-14T22:27:10ZRichCannot delete relationship type through UIClicking more » Delete on the `/civicrm/admin/reltype` page pops up box but fails to load the confirmation message. A network error is shown, and if you look in the console the actual response is:
> Sorry, due to an error, we are unable...Clicking more » Delete on the `/civicrm/admin/reltype` page pops up box but fails to load the confirmation message. A network error is shown, and if you look in the console the actual response is:
> Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred.
Cannot determine api action for CRM_Admin_Form_RelationshipType.CRM_Core_Action "delete" not recognized.
The path is `civicrm/admin/reltype?action=delete&id=11&snippet=json`
Confirmed in two sites on v5.8.1 and v5.10.0 (inc. the civihosting demo site) on Drupal 7. This worked in 5.3.1
(It is possible to delete relationship types using the API)5.10.2https://lab.civicrm.org/dev/core/-/issues/711Google+ references should be removed as it phases out2023-01-10T18:40:34ZphilmorbruGoogle+ references should be removed as it phases outNot a big deal, but as Google phases out Google+, visible references to it should be removed, especially from non-configurable features such as the "Tell a Friend" block for events.Not a big deal, but as Google phases out Google+, visible references to it should be removed, especially from non-configurable features such as the "Tell a Friend" block for events.5.23.0