CiviCRM Core issueshttps://lab.civicrm.org/dev/core/-/issues2023-12-06T23:18:04Zhttps://lab.civicrm.org/dev/core/-/issues/4818Line Items: different behaviour between order API and backend when registerin...2023-12-06T23:18:04ZmasettoLine Items: different behaviour between order API and backend when registering price options not related to a membership typeWhen I create a membership with price sets, for the price options that not are related to a membership type, the entity table in line items is `civicrm_contribution`.
But if I create a membership with Order API the entity table for all ...When I create a membership with price sets, for the price options that not are related to a membership type, the entity table in line items is `civicrm_contribution`.
But if I create a membership with Order API the entity table for all line items have to be `civicrm_membership` otherwise the membership is not created.
For example, if I use `civicrm_contribution` for "price_field_id = 16" in the following example, the membership is not created. If I replace to `civicrm_membership` the membership is created correctly.
But I add the same membership in the backend, the entity_table for "price_field_id = 16" is `civicrm_contribution`.
```
[return] => membership_id
[contact_id] => 178918
[financial_type_id] => 2
[contribution_status] => Pending
[total_amount] => 36
[receive_date] => 20231129084211
[payment_instrument_id] => 7
[invoice_id] => CH-a1dafa484b7dbbf1ea4aae1b
[trxn_id] =>
[payment_processor_id] => 2
[is_email_receipt] =>
[line_items] => Array
(
[0] => Array
(
[line_item] => Array
(
[0] => Array
(
[entity_table] => civicrm_membership
[price_field_id] => 15
[price_field_value_id] => 22
[qty] => 1
[unit_price] => 30
[line_total] => 30
)
[1] => Array
(
[entity_table] => civicrm_contribution
[price_field_id] => 16
[price_field_value_id] => 25
[qty] => 1
[unit_price] => 6
[line_total] => 6
)
)
[params] => Array
(
[id] =>
[membership_type_id] => 1
[contact_id] => 178918
[end_date] => 2024-12-31
[is_override] => 0
[status_id] => Pending
[max_related] => 0
[join_date] => 20231129084211
[start_date] => 2024-01-01
)
)
)
[debug] => 1
[is_test] => 0
```
It is important that the data is recorded in the same way. Also because if I have to make queries becomes very complicated (I have not yet found a way to do this with SearchKit).https://lab.civicrm.org/dev/core/-/issues/4817$imageURL is not available on membership contribution confirmation and thank ...2023-12-06T22:25:06Zfreeform.steph$imageURL is not available on membership contribution confirmation and thank you pagesThis was originally posted here: https://issues.civicrm.org/jira/browse/CRM-19983 in 2017 but I am not finding any indication that it was ever resolved, or this is a regression, not sure.
If you include the contact photo field (image_ur...This was originally posted here: https://issues.civicrm.org/jira/browse/CRM-19983 in 2017 but I am not finding any indication that it was ever resolved, or this is a regression, not sure.
If you include the contact photo field (image_url) in a profile on a membership contribution form and a user uses the field, the image is uploaded, however the image preview (thumbnail with option to delete) fails to display on the confirmation and thank you pages. This causes the users confusion because the field to upload an image appears in its place which leads the individuals to re-try uploading their image (which will cause their image to not be saved). It also fails to appear on the thank you page if you do not enable the confirmation page option.
If you include the smarty debug tag in templates/CRM/UF/Form/Fields.tpl where you'd expect the image to be output, you'll see that $imageURL is not defined.
If you use the same field on a standalone profile form, the preview does display on the last page (there is no confirmation page in this case), so it does appear to be limited to when the profile is included on a contribution form.
What we should see: (1) no upload field on confirmation or thank you pages, (2) include a preview of an image if one was uploaded.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/4813CRM_Report_Form_Activity: Add Employer field, and "contact"-based custom fields2023-12-18T23:06:40ZAllenShawCRM_Report_Form_Activity: Add Employer field, and "contact"-based custom fieldsThis improvement is requested and sponsored by Stuart at Korlon.
We aim to implement the following changes to the CiviCRM core "Activity Detail" report (CRM_Report_Form_Activity):
- add "Current Employer" as an available column (not fi...This improvement is requested and sponsored by Stuart at Korlon.
We aim to implement the following changes to the CiviCRM core "Activity Detail" report (CRM_Report_Form_Activity):
- add "Current Employer" as an available column (not filter), to display with its Display Name, as a link to the employer contact
- auto-include "contact"-based custom fields (currently only "individual"-based custom fields get this treatment)
A PR is forthcoming. If it seems this is not a desirable improvement, please let me know in comments!
(Joinery reference: F#1317)https://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/4810Class name must be a valid object or a string2023-12-06T23:12:00ZPaulButlerClass name must be a valid object or a stringI am seeing a strange issue that "seemed" to create itself. When trying to access a member record I get this error:
Class name must be a valid object or a string
in httpdocs/administrator/components/com_civicrm/civicrm/CRM/Utils/SQL.ph...I am seeing a strange issue that "seemed" to create itself. When trying to access a member record I get this error:
Class name must be a valid object or a string
in httpdocs/administrator/components/com_civicrm/civicrm/CRM/Utils/SQL.php (line 61)
* @param string $joinColumn * @return array */ public static function mergeSubquery($entityName, $joinColumn = 'id') {
* $baoName = CRM_Core_DAO_AllCoreTables::getBAOClassName(CRM_Core_DAO_AllCoreTables::getFullName($entityName));
* $bao = new $baoName();
* $fields = $bao::getSupportedFields();
* $mergeClauses = $subClauses = [];
* foreach ((array) $bao->addSelectWhereClause($entityName) as $fieldName => $fieldClauses) { if ($fieldClauses) { foreach ((array) $fieldClauses as $fieldClause) {
The command that is failing is $bao = new $baoName
This error seemed to manifest itself (I know it won't have!). I restored a dump of the database from a previous day and can access the member record just fine , when I restore the database it then throws this error.
What more can I do to try and trace the source of it. My gut feel is that it's a DB corruption of sorts but I am unable to identify what. I set SQL trace on in CiviCRM but that doesn't display any errors that I can see.
Suggestions please?
My site is running Joomla 4.4 , PHP 8.0.30 and CiviCRM 5.67.1https://lab.civicrm.org/dev/core/-/issues/4809Backend register for event via credit card has problematic pre-help text and ...2023-12-06T23:06:43ZDaveDBackend register for event via credit card has problematic pre-help text and should be completely removed and replaced with only a translation-friendly indicator of live vs testCopied from https://github.com/civicrm/civicrm-core/pull/28309
I think the [tpl line](https://github.com/civicrm/civicrm-core/blob/6c6fdea6429f39d552d0cc6bae0254d27daa4919/templates/CRM/Event/Form/Participant.tpl#L31) needs to be comple...Copied from https://github.com/civicrm/civicrm-core/pull/28309
I think the [tpl line](https://github.com/civicrm/civicrm-core/blob/6c6fdea6429f39d552d0cc6bae0254d27daa4919/templates/CRM/Event/Form/Participant.tpl#L31) needs to be completely replaced. I would remove the first sentence since it adds no value since right above it already says the name when it's present, and when it's not present is the cause of this notice, and then the second sentence is not correct in other languages (the "live"/"test" is always in english). Elsewhere the approach for that when there's a known list of values is to just hardcode the full sentences in an `{if}` block.
I do think it's important to identify if it's live or test, but since none of the above has been raised as an issue the help text itself seems very unimportant. Maybe it should just have some kind of icon indicating live or test and that's it.https://lab.civicrm.org/dev/core/-/issues/4808Proposal: Phase out public profile fields and profile listings2023-12-06T22:08:58ZbgmProposal: Phase out public profile fields and profile listingsNow that SearchKit provides this functionality, we should consider deprecating "public profile fields" and profile listings. They are a recurrent source of confusion and a bad configuration can lead to a data leak (I stumble on them regu...Now that SearchKit provides this functionality, we should consider deprecating "public profile fields" and profile listings. They are a recurrent source of confusion and a bad configuration can lead to a data leak (I stumble on them regularly, with the help of the [symbiotic extension](https://civicrm.org/extensions/symbiotic).
I think we should:
- [ ] Add a feature flag (a hidden setting?) that hides
- ~~On Profiles, the option "Standalone Form or Directory"~~ (edit: I guess this might be needed for profile/edit of users with a checksum?)
- On Profile Fields: hide the visibility options, set them by default to "User and Admin only"
- [ ] Remove the feature from the Admin documentation
- [ ] Begin changing the interface to warn that we will be removing this feature, and that they can opt-in to that change right now
- [ ] Set a date for complete removal (or if someone really insists on keeping this feature, help them create an extension for it)https://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/4806Tax amount on 'other amount field' - not being added2023-12-06T23:04:26ZeileenTax amount on 'other amount field' - not being addedWhen you Configure a Contribution Page with tax that applies to the 'Other Amount' field it is not applied.
Note that the way the page appears I feel like the amount entered should be treated as inclusive rather than exclusive - the alt...When you Configure a Contribution Page with tax that applies to the 'Other Amount' field it is not applied.
Note that the way the page appears I feel like the amount entered should be treated as inclusive rather than exclusive - the alternative would be to improve the messaging to make it clearer on the page but it feels weird to ask people to enter a tax-exclusive amount
Screenshots from 5.60 with odd currency formatting configured
![image](/uploads/3ca803cb8846284f720063a253df407b/image.png)
Note tax is still $15
![image](/uploads/a54e7208521af056f0f958e152a4ff1b/image.png)
In the final screen the tax is ... interesting
![image](/uploads/074207531cc4cdb00fb56db499ca6421/image.png)
**Note**
1) there is code to say that if the membership recurs then the other amount should not be includedhttps://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/4801[PHP 8.2] Access to an undefined property in CRM_Event_Badge_*2023-12-11T23:28:11Zjofranzfranz@systopia.de[PHP 8.2] Access to an undefined property in CRM_Event_Badge_*If I spot them correctly these are yet not covered by a unit test:
```
------ --------------------------------------------------------------------------------------
Line Logo.php ...If I spot them correctly these are yet not covered by a unit test:
```
------ --------------------------------------------------------------------------------------
Line Logo.php
------ --------------------------------------------------------------------------------------
17 Access to an undefined property CRM_Event_Badge_Logo::$format.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
31 Access to an undefined property CRM_Event_Badge_Logo::$lMarginLogo.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
32 Access to an undefined property CRM_Event_Badge_Logo::$tMarginName.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
40 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
41 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
43 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
51 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
52 Access to an undefined property CRM_Event_Badge_Logo::$border.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
52 Access to an undefined property CRM_Event_Badge_Logo::$lMarginLogo.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
52 Access to an undefined property CRM_Event_Badge_Logo::$lMarginLogo.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
52 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
52 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
54 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
54 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
56 Access to an undefined property CRM_Event_Badge_Logo::$border.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
56 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
56 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
58 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
59 Access to an undefined property CRM_Event_Badge_Logo::$border.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
59 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
59 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
59 Access to an undefined property CRM_Event_Badge_Logo::$tMarginName.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
60 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
61 Access to an undefined property CRM_Event_Badge_Logo::$border.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
61 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
61 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
61 Access to an undefined property CRM_Event_Badge_Logo::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
------ --------------------------------------------------------------------------------------
------ --------------------------------------------------------------------------------------
Line Logo5395.php
------ --------------------------------------------------------------------------------------
17 Access to an undefined property CRM_Event_Badge_Logo5395::$format.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
31 Access to an undefined property CRM_Event_Badge_Logo5395::$lMarginLogo.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
32 Access to an undefined property CRM_Event_Badge_Logo5395::$tMarginName.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
40 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
41 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
43 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
51 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
52 Access to an undefined property CRM_Event_Badge_Logo5395::$border.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
52 Access to an undefined property CRM_Event_Badge_Logo5395::$lMarginLogo.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
52 Access to an undefined property CRM_Event_Badge_Logo5395::$lMarginLogo.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
52 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
52 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
54 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
54 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
56 Access to an undefined property CRM_Event_Badge_Logo5395::$border.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
56 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
56 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
58 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
59 Access to an undefined property CRM_Event_Badge_Logo5395::$border.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
59 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
59 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
59 Access to an undefined property CRM_Event_Badge_Logo5395::$tMarginName.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
60 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
61 Access to an undefined property CRM_Event_Badge_Logo5395::$border.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
61 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
61 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
61 Access to an undefined property CRM_Event_Badge_Logo5395::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
------ --------------------------------------------------------------------------------------
------ --------------------------------------------------------------------------------------
Line NameTent.php
------ --------------------------------------------------------------------------------------
33 Access to an undefined property CRM_Event_Badge_NameTent::$lMargin.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
34 Access to an undefined property CRM_Event_Badge_NameTent::$tMargin.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
37 Access to an undefined property CRM_Event_Badge_NameTent::$format.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
55 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
62 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
62 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
65 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
65 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
66 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
67 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
68 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
68 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
69 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
70 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
78 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
79 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
79 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
79 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
79 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
81 Access to an undefined property CRM_Event_Badge_NameTent::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
------ --------------------------------------------------------------------------------------
------ --------------------------------------------------------------------------------------
Line Simple.php
------ --------------------------------------------------------------------------------------
31 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
32 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
33 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
34 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
34 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
34 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
35 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
36 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
36 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
36 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
37 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
38 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
38 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
39 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
39 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
39 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
40 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
41 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
41 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
42 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
42 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
42 Access to an undefined property CRM_Event_Badge_Simple::$pdf.
π‘ Learn more: https://phpstan.org/blog/solving-phpstan-access-to-undefined-property
------ --------------------------------------------------------------------------------------
```
Related: #4072https://lab.civicrm.org/dev/core/-/issues/4800Add Card Type and Last 4 to Contribution Import2023-12-06T22:31:00Zlevi.kAdd Card Type and Last 4 to Contribution ImportOverview
----------------------------------------
When importing a contribution there are certain fields like Date, transaction ID from the contribution that get added to the Financial_Trx it would be nice to have the Card Type ID and PA...Overview
----------------------------------------
When importing a contribution there are certain fields like Date, transaction ID from the contribution that get added to the Financial_Trx it would be nice to have the Card Type ID and PAN Truncation fields to be available in the contribution importer
Current behavior
----------------------------------------
currently Card Type ID (Card type like Visa Amex) and PAN Truncation (Last 4 of cc number) fields aren't available during contribution import
Proposed behavior
----------------------------------------
add those fields to contribution importhttps://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.beta1