CiviCRM Core issueshttps://lab.civicrm.org/dev/core/-/issues2022-04-22T16:17:47Zhttps://lab.civicrm.org/dev/core/-/issues/3340Additional Memberships added via Contribution Pages overwrite existing member...2022-04-22T16:17:47ZalanpuccinelliAdditional Memberships added via Contribution Pages overwrite existing membershipsVerified on current demo install of ver 5.0
To Reproduce:
1. Create an inherited membership for an individual by assigning the membership to a related organization.
2. Create a Pending membership via a contribution page and select "Pay ...Verified on current demo install of ver 5.0
To Reproduce:
1. Create an inherited membership for an individual by assigning the membership to a related organization.
2. Create a Pending membership via a contribution page and select "Pay Later/by check"
3. Notice that Pending membership is not created for contribution page membership
4. Receive payment for the pending membership contribution. (Membership should switch to active at this point)
5. Because there is no pending membership it appears that the system will overwrite the existing inherited membership and extend the end date by whatever the new membership period is.https://lab.civicrm.org/dev/core/-/issues/69'state_province_name' token not working for alternate billing addresses2018-05-16T09:21:00Zvarshith'state_province_name' token not working for alternate billing addresses## Overview ##
This issue is related to this existing issue
https://issues.civicrm.org/jira/browse/CRM-21830
The PR for the above issue is here
https://github.com/civicrm/civicrm-core/pull/11776
Though this fixes the basic issue, it ...## Overview ##
This issue is related to this existing issue
https://issues.civicrm.org/jira/browse/CRM-21830
The PR for the above issue is here
https://github.com/civicrm/civicrm-core/pull/11776
Though this fixes the basic issue, it still doesn't work for all fields.
## How it works currently ##
If state_province field name is not of the form "state_province-{$billingLocationTypeID}", then state_province_name is empty. Which means field names of form 'billing_state_province-{#}' and 'billing_state_province_id-{#}' results in empty state_province_name when "state_province_name" token is used.5.3.0https://lab.civicrm.org/dev/core/-/issues/70On any custom search 'Print selected rows' action doesn't retain columns/values2018-04-26T17:31:14ZMonish DebOn any custom search 'Print selected rows' action doesn't retain columns/valuesSteps to replicate:
* Go to any custom search
* Choose any or all record
* Then choose 'Print selected rows'
Actual Result: There are different headers and except name all values are empty
Expected Result: The print screen should th...Steps to replicate:
* Go to any custom search
* Choose any or all record
* Then choose 'Print selected rows'
Actual Result: There are different headers and except name all values are empty
Expected Result: The print screen should the headers chosen for that Custom search and its corresponding values under itMonish DebMonish Debhttps://lab.civicrm.org/dev/core/-/issues/71Add Print/Merge Letter functionality for activity searches2020-02-27T20:19:41Zaydunsaidan.saunders@squiffle.ukAdd Print/Merge Letter functionality for activity searchesMost of the standard searches provide an action to create a PDF or Word document - except Activities.Most of the standard searches provide an action to create a PDF or Word document - except Activities.5.23.0aydunsaidan.saunders@squiffle.ukaydunsaidan.saunders@squiffle.ukhttps://lab.civicrm.org/dev/core/-/issues/72PayflowPro throws error due to more than 4 decimal places2018-04-30T22:08:25ZyashodhaPayflowPro throws error due to more than 4 decimal placesPayflowPro throws error due to more than 4 decimal places
> Payment Processor Error message: 9013: Error - from payment processor: [4 Invalid amount]
> 9013: Error - from payment processor: [4 Invalid amount]
This was introduced in
ht...PayflowPro throws error due to more than 4 decimal places
> Payment Processor Error message: 9013: Error - from payment processor: [4 Invalid amount]
> 9013: Error - from payment processor: [4 Invalid amount]
This was introduced in
https://github.com/civicrm/civicrm-core/pull/11016
where database changes supported decimal upto 9 places.
**Before patch**
![payflow_before](/uploads/076f9b7a26906f24006898c670ad4345/payflow_before.png)
**After patch**
![payflow_after](/uploads/da4ecc053566b989aed53d42daa26068/payflow_after.png)5.2.0yashodhayashodhahttps://lab.civicrm.org/dev/core/-/issues/73Add invoice number to bookkeeping report2018-04-28T07:06:34ZyashodhaAdd invoice number to bookkeeping reportAdd invoice number to bookkeeping reportAdd invoice number to bookkeeping reportyashodhayashodhahttps://lab.civicrm.org/dev/core/-/issues/74'Price Set Details for Event Participants' gives DB error if the price fields...2018-11-18T21:07:07Zyashodha'Price Set Details for Event Participants' gives DB error if the price fields are disabled.Steps to replicate:
-------------------
1. Create a price set and associate with an event.
2. Register a participant with the event.
3. Disable the price fields.
4. Go to Custom Searches > Price Set Details for Event Participants, sear...Steps to replicate:
-------------------
1. Create a price set and associate with an event.
2. Register a participant with the event.
3. Disable the price fields.
4. Go to Custom Searches > Price Set Details for Event Participants, search with the said event.
It throws DB error
> DB Error: syntax error
> Error Details
> Database Error Code: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE participant_id = 52' at line 3, 1064
> Additional Details:
> Array
> (
> [callback] => Array
> (
> [0] => CRM_Core_Error
> [1] => handle
> )
>
> [code] => -2
> [message] => DB Error: syntax error
> [mode] => 16
> [debug_info] =>
> UPDATE civicrm_temp_custom_c87e02e10a4041be20a9ae7529218687
> SET
> WHERE participant_id = 52;
> [nativecode=1064 ** You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE participant_id = 52' at line 3]
> [type] => DB_Error
> [user_info] =>
> UPDATE civicrm_temp_custom_c87e02e10a4041be20a9ae7529218687
> SET
> WHERE participant_id = 52;
> [nativecode=1064 ** You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE participant_id = 52' at line 3]
> [to_string] => [db_error: message="DB Error: syntax error" code=-2 mode=callback callback=CRM_Core_Error::handle prefix="" info="
> UPDATE civicrm_temp_custom_c87e02e10a4041be20a9ae7529218687
> SET
> WHERE participant_id = 52;
> [nativecode=1064 ** You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE participant_id = 52' at line 3]"]
> )yashodhayashodhahttps://lab.civicrm.org/dev/core/-/issues/75warning message after an activity is created2018-04-28T23:34:18Zjitendrawarning message after an activity is createdA warning is displayed when an activity is created - http://dmaster.demo.civicrm.org/civicrm/activity?reset=1&action=add&context=standalone
> Warning: in_array() expects parameter 2 to be array, null given in CRM_Activity_Form_Activity-...A warning is displayed when an activity is created - http://dmaster.demo.civicrm.org/civicrm/activity?reset=1&action=add&context=standalone
> Warning: in_array() expects parameter 2 to be array, null given in CRM_Activity_Form_Activity->processActivity() (line 1102 of /srv/buildkit/build/dmaster/sites/all/modules/civicrm/CRM/Activity/Form/Activity.php).jitendrajitendrahttps://lab.civicrm.org/dev/core/-/issues/76Multiple roles per participant causes incorrect participant counts (was: Civi...2023-11-12T15:46:22ZUpperholmeMultiple roles per participant causes incorrect participant counts (was: CiviEvent no longer respects Max Participants)Since upgrading to 5.0 I find that events continue to allow front end registrations despite the number of counted participants exceeding the max number set on the event configuration. The on-screen alert is not displayed, and registratio...Since upgrading to 5.0 I find that events continue to allow front end registrations despite the number of counted participants exceeding the max number set on the event configuration. The on-screen alert is not displayed, and registration remains open.
as a temporary workaround I'm having to closely monitor registrations and manually turn off online registration and edit the event information to provide an 'event full' message when capacity is reached.https://lab.civicrm.org/dev/core/-/issues/77CiviCRM 5.0 angular pages conflict with mootools.js in Joomla 2.52020-02-10T15:44:32Zjoels341CiviCRM 5.0 angular pages conflict with mootools.js in Joomla 2.5Hello CiviCRM team,
I noticed that even though CiviCRM 5.0 claims to be compatible with Joomla 2.5 (we have some sites that we can't upgrade), some of the angular pages such as the "status" page and "new mailing" page show up blank.
If...Hello CiviCRM team,
I noticed that even though CiviCRM 5.0 claims to be compatible with Joomla 2.5 (we have some sites that we can't upgrade), some of the angular pages such as the "status" page and "new mailing" page show up blank.
If I yank mootools.js out of Joomla 2.5, then all these pages work.
Could someone with more experience please fix the compatibility issues?
Best,
Joelhttps://lab.civicrm.org/dev/core/-/issues/78Incorrect Payment Processor for Recurring Payments2018-11-17T02:47:01ZjitendraIncorrect Payment Processor for Recurring PaymentsThe issue arises due to there being two AuthNet payment processors, one for both A1 and A2. And the CiviCRM code is (naively) written assuming there'd be a maximum of one. So when AuthNet calls into CiviCRM to notify it of a successful r...The issue arises due to there being two AuthNet payment processors, one for both A1 and A2. And the CiviCRM code is (naively) written assuming there'd be a maximum of one. So when AuthNet calls into CiviCRM to notify it of a successful recurring payment, for the A1 payments it is loading the A2 payment processor — and then failing.
The attached patch uses information from the address that AuthNet posts its updates to, which can signal which payment processor to use.5.2.0https://lab.civicrm.org/dev/core/-/issues/79CiviEmail A/B testing unsubscribe issue2018-04-27T08:00:59Zpratik.joshiCiviEmail A/B testing unsubscribe issuehttps://docs.civicrm.org/user/en/latest/email/civimail-ab-testing/
What this feature does is it helps distributes recipients of a mailing group into 2 mailings A and B mailings. Now for the A mailing 'include group' has the mailing gro...https://docs.civicrm.org/user/en/latest/email/civimail-ab-testing/
What this feature does is it helps distributes recipients of a mailing group into 2 mailings A and B mailings. Now for the A mailing 'include group' has the mailing group attached to it, but for the B mailing no group is attached.
When the mailings gets sent out, if anyone receives email from B mailing, and if that user unsubscribes, the user ends up getting unsubscribed from all the groups (since no group exists in that particular mailing all groups are listed in unsubscribe confirm UI). This happens because 'where clause' consisting of mailing group id is not attached as group is not present.
Please can anyone let me know if i am missing something.
Thanks!https://lab.civicrm.org/dev/core/-/issues/80Current Employer is not reset after relationship is updated2018-05-14T22:46:20ZjitendraCurrent Employer is not reset after relationship is updatedReplicated on dmaster.
- Add an employer relationship for a contact.
- Current Employer is correctly set.
- Edit the relationship to some other type eg. "Volunteer For" -> Save.
- Current Employer Field is still set to the previous value.Replicated on dmaster.
- Add an employer relationship for a contact.
- Current Employer is correctly set.
- Edit the relationship to some other type eg. "Volunteer For" -> Save.
- Current Employer Field is still set to the previous value.5.3.0jitendrajitendrahttps://lab.civicrm.org/dev/core/-/issues/81Warnings from CustomGroup and CustomField create functions2018-04-30T22:08:39ZmichaelWarnings from CustomGroup and CustomField create functionsBoth CustomGroup and CustomField seem to treat `create` as a method only for creating new entities. Although updates do work, a few places in the code expect that you have included some value in the params that you don't intend to update...Both CustomGroup and CustomField seem to treat `create` as a method only for creating new entities. Although updates do work, a few places in the code expect that you have included some value in the params that you don't intend to update.
For example:
```
$params = ['id' => 1, 'is_active' => 0];
civicrm_api3('CustomField', 'create', $params);
```
Will produce a warning (from a test I wrote for this):
```
Failure in api call for CustomGroup create: Undefined index: extends
#0 /repos/civicrm-core/CRM/Core/BAO/CustomGroup.php(64): PHPUnit_Util_ErrorHandler::handleError(8, 'Undefined index...', '/repos/civicrm-...', 64, Array)
```
---
https://github.com/civicrm/civicrm-core/pull/12033/files5.2.0https://lab.civicrm.org/dev/core/-/issues/82Get/set UF locale/language is not supported (ex: for inheritLocale)2018-04-26T18:40:02ZbgmGet/set UF locale/language is not supported (ex: for inheritLocale)The option for `inhericLocale` does not seem to be working. To reproduce:
* In Drupal, enable translation and enable a second language, set language-detection using the URL prefix.
* Create a multi-lingual site (admin > locale > languag...The option for `inhericLocale` does not seem to be working. To reproduce:
* In Drupal, enable translation and enable a second language, set language-detection using the URL prefix.
* Create a multi-lingual site (admin > locale > languages, enable multilingual, then enable a second language)
* Enable the "inherit CMS language" option.
![Capture_d_écran_de_2018-04-26_14-35-12](/uploads/89038ae28d2c10fd75ac925e7693693c/Capture_d_écran_de_2018-04-26_14-35-12.png)
Result: no matter whether accessing CiviCRM in English or French, the site is always in the default language.bgmbgmhttps://lab.civicrm.org/dev/core/-/issues/83Related Contacts in Advanced Search2018-04-29T12:11:16ZjrolfsRelated Contacts in Advanced SearchWhen running an Advanced Search and displaying the results as Related Contacts, there was once another dropdown box that showed up that allowed you to select the type of relationship that you wanted to see. That additional dropdown box ...When running an Advanced Search and displaying the results as Related Contacts, there was once another dropdown box that showed up that allowed you to select the type of relationship that you wanted to see. That additional dropdown box is no longer there.
![Related_Contacts_in_Advanced_Search](/uploads/997a28922c4fa511cfbcab647f5789c8/Related_Contacts_in_Advanced_Search.jpg)jitendrajitendrahttps://lab.civicrm.org/dev/core/-/issues/84Error when searching for Participants2018-04-28T07:22:36ZPradeep Nayakpradpnayak@gmail.comError when searching for Participantshttps://civicrm.stackexchange.com/questions/24671/error-when-searching-for-participants
It seems that there is regression because of https://github.com/civicrm/civicrm-core/pull/11706
Commenting line 4912(self::getGroupByFromOrderBy($g...https://civicrm.stackexchange.com/questions/24671/error-when-searching-for-participants
It seems that there is regression because of https://github.com/civicrm/civicrm-core/pull/11706
Commenting line 4912(self::getGroupByFromOrderBy($groupBy, $orderBys);) in CRM/Contact/BAO/Query.php seems to fix the issue.https://lab.civicrm.org/dev/core/-/issues/85mail() backend fails when empty Cc and Bcc parameters are passed2018-05-21T02:22:12Zmattwiremjw@mjwconsult.co.ukmail() backend fails when empty Cc and Bcc parameters are passedOn some servers the PHP mail() function fails to send email if empty 'Cc' or 'Bcc' headers are set.On some servers the PHP mail() function fails to send email if empty 'Cc' or 'Bcc' headers are set.5.3.0https://lab.civicrm.org/dev/core/-/issues/86CIVICRM_MAIL_LOG_AND_SEND does not work properly2018-11-18T21:03:25Zmattwiremjw@mjwconsult.co.ukCIVICRM_MAIL_LOG_AND_SEND does not work properlyIn the packages/Mail it is mistyped as "CIVICRM_MAIL_LOG_AND SEND" (ie. missing an underscore): https://github.com/civicrm/civicrm-packages/pull/204
In CiviCRM core the administrator is not notified if it is set: https://github.com/civi...In the packages/Mail it is mistyped as "CIVICRM_MAIL_LOG_AND SEND" (ie. missing an underscore): https://github.com/civicrm/civicrm-packages/pull/204
In CiviCRM core the administrator is not notified if it is set: https://github.com/civicrm/civicrm-core/pull/12037
In the docs it is missing altogether: https://github.com/civicrm/civicrm-dev-docs/pull/5265.2.0https://lab.civicrm.org/dev/core/-/issues/87PayPal Pro missing parameters (add standard getters)2022-08-10T05:03:38Zmattwiremjw@mjwconsult.co.ukPayPal Pro missing parameters (add standard getters)Overview
----------------------------------------
state_province, country and ip_address are not always set properly for paypal pro due to inconsistency with parameters being passed.
https://github.com/civicrm/civicrm-core/pull/12038
Be...Overview
----------------------------------------
state_province, country and ip_address are not always set properly for paypal pro due to inconsistency with parameters being passed.
https://github.com/civicrm/civicrm-core/pull/12038
Before
----------------------------------------
state_province, country and ip_address may not be passed to payment processor.
After
----------------------------------------
This applies to ALL payment processors:
* If state_province and country were passed from the payment form in one way or another, they will be presented in a consistent format to the payment processor.
* Add client ip_address to the list of parameters so payment processors don't have to retrieve this manually if they require it (paypal pro wants it but was not retrieving it).
Technical Details
----------------------------------------
This PR adds three generic "getters" to CRM_Core_Payment per @eileenmcnaughton suggestion. For compatibility, no parameters are removed but additional parameters may be set depending on what is passed in. For example if only country_id is defined, then country will be set as well.
Comments
----------------------------------------
This fixes a real issue identified with the paypal pro processor in core, but the inconsistency of parameters passed affects other processors and means each processor has to do extra coding to make sure that the parameters are in the right format when they are passed in.
See for example: https://civicrm.stackexchange.com/questions/24316/paypal-pro-billing-address-state-province-country-not-being-passed