Development issues
https://lab.civicrm.org/groups/dev/-/issues
2018-11-29T06:16:04Z
https://lab.civicrm.org/dev/drupal/-/issues/32
Drupal8: Can't add JS resources to footer
2018-11-29T06:16:04Z
JonGold
Drupal8: Can't add JS resources to footer
This manifests most obviously with Shoreditch - some JS is intended to load in `page-footer` and fails.
This was first documented as CRM-21374(https://github.com/civicrm/civicrm-core/pull/11504#issuecomment-356837051), which was closed ...
This manifests most obviously with Shoreditch - some JS is intended to load in `page-footer` and fails.
This was first documented as CRM-21374(https://github.com/civicrm/civicrm-core/pull/11504#issuecomment-356837051), which was closed with a quick fix.
Also related are [civicrm-core#11504](https://github.com/civicrm/civicrm-core/pull/11504) which removes the D8 `addScriptUrl()` function. It seems to be relying on [drupal#504](https://github.com/civicrm/civicrm-drupal/pull/504) to add scripts to the header, but not to the footer.
@dsnopek mentioned [in passing](https://github.com/civicrm/civicrm-core/pull/11504#issuecomment-356837051) that CiviCRM D8 can't yet add resources to the footer.
Fixing this requires an understanding of D8 Services, which I don't have. It seems like the `CivicrmPageState` class needs a different data structure for `$js`. Whether that's a separate `$jsFooter` property or a multidimensional array I'm not sure.
https://lab.civicrm.org/dev/core/-/issues/3572
Deduping test email is case sensitive
2022-06-11T14:54:27Z
Martin
Deduping test email is case sensitive
Tested on 4.6.38 and 5.6.1.
When composing a mailing, the email address used in the "send test email to" field at the bottom is deduped. This is case sensitive, so fails to match emails that are the same but have different upper/lower c...
Tested on 4.6.38 and 5.6.1.
When composing a mailing, the email address used in the "send test email to" field at the bottom is deduped. This is case sensitive, so fails to match emails that are the same but have different upper/lower case combinations. In this case, it will create a new contact with this interesting property: the value in the "email" field shows with the email address flattened to all lowercase, but the display name for the contact shows with the upper/lower case mix used when it was entered to test the mailing.
The upshot of all this is that if I'm putting together a mailing and send 6 test to the same email address (with an uppercase letter), I get 6 new duplicate contacts because it fails to match it each time.
Request to make the dedupe test for this mailing field case insensitive, since in general civi seems to want email addresses to be lowercase when they're used.
I can potentially make this change if someone can point me in the right direction.
Thanks!
5.11
https://lab.civicrm.org/dev/core/-/issues/33
CiviCRM-WordPress - Do not parse shortcodes in REST context
2023-04-28T01:39:33Z
kcristiano
CiviCRM-WordPress - Do not parse shortcodes in REST context
WordPress 5.0 will introduce a new default editing experience. The code name is 'Gutenberg' . Gutenberg is built on blocks and the method of handling modals in the editing experience is changing.
The existing modal for inserting shor...
WordPress 5.0 will introduce a new default editing experience. The code name is 'Gutenberg' . Gutenberg is built on blocks and the method of handling modals in the editing experience is changing.
The existing modal for inserting shortcodes will not work with Gutenberg. We will need to rework inserting the shortcode to a new block for the new release. Expected Merge Request for Gutenberg will be April 2018 and the release will be sometime thereafter.
However, this week WP 4.9.5 will ship and in this release will be a call to action to all users to install the Gutenberg plugin to test.
Currently if a CiviCRM shortcode is put into the 'Shortcode Block' there will be an error and the post will not save properly. As [bastienho](https://github.com/bastienho) points out in [PR 126](https://github.com/civicrm/civicrm-wordpress/pull/126) the following error is thrown: ``Notice: Trying to get property of non-object in civicrm/civicrm/CRM/Utils/System/WordPress.php on line 221``
For now we should fix this error and then work on full Gutenberg Compatibility once the official merge request is approved to WP.
https://lab.civicrm.org/dev/financial/-/issues/33
Proposal - Add in hook alterPostIpn or similar
2018-10-27T04:12:13Z
seamuslee
Proposal - Add in hook alterPostIpn or similar
As discussed in Mattermost https://chat.civicrm.org/civicrm/pl/xt83abz75pbwtr5k4em4thhp1r the proposal is to add in a hook like hook_civicrm_alterIPNData or similar that would allow developers to utilise data that comes back in via IPNs ...
As discussed in Mattermost https://chat.civicrm.org/civicrm/pl/xt83abz75pbwtr5k4em4thhp1r the proposal is to add in a hook like hook_civicrm_alterIPNData or similar that would allow developers to utilise data that comes back in via IPNs especially in this case PayPal.
The usecase here is that we would use the AlterPaymentProcessorParams hook to include a googleAnalytics token which includes utm codes etc, then use the alterIPNData hook to then extract that when the IPN is processed by CiviCRM sending a GA event so that when the transaction is recorded the UTM codes etc that were associated with the link are also passed up to GA so we can link back to the original hit on the site that the IPN relates to.
I plan to leave this for about a week for people to comment if no objections raised then i will work on writing the hook,
@jamienovick1 @JoeMurray @justinfreeman @mattwire @eileen et all
5.8
seamuslee
seamuslee
https://lab.civicrm.org/dev/drupal/-/issues/33
Implement userFrameworkFrontend Configuration for Drupal
2019-11-24T05:41:04Z
seamuslee
Implement userFrameworkFrontend Configuration for Drupal
This is to support the concept of Separate frontend and backend themes
This is to support the concept of Separate frontend and backend themes
5.16.0
https://lab.civicrm.org/dev/core/-/issues/3610
Jira Issue CRM-21666 still exists in 5.8.1
2022-06-11T14:56:07Z
jeffmikels
Jira Issue CRM-21666 still exists in 5.8.1
https://issues.civicrm.org/jira/browse/CRM-21666
CRM/Mailing/DAO/Mailing.php
and
CRM/Mailing/BAO/Mailing.php
still have a discrepancy regarding the naming of the mailing_date field
messageNotice: Undefined property: CRM_Mailing_BAO...
https://issues.civicrm.org/jira/browse/CRM-21666
CRM/Mailing/DAO/Mailing.php
and
CRM/Mailing/BAO/Mailing.php
still have a discrepancy regarding the naming of the mailing_date field
messageNotice: Undefined property: CRM_Mailing_BAO_Mailing::$mailing_modified_date in CRM_Mailing_BAO_Mailing::report()
5.9
https://lab.civicrm.org/dev/core/-/issues/34
Split edit/view access on permissioned relationships
2023-04-28T01:39:33Z
ayduns
aidan.saunders@squiffle.uk
Split edit/view access on permissioned relationships
Currently, relationships can be 'permissioned' such that one contact in the relationship can access the other. This access is both view and edit. It is not possible to provide 'view-only' access via a relationship.
The proposed approa...
Currently, relationships can be 'permissioned' such that one contact in the relationship can access the other. This access is both view and edit. It is not possible to provide 'view-only' access via a relationship.
The proposed approach is to create an 'edit related contacts' permission that works in conjunction with the existing permissioning:
- for users with the 'edit related contacts' permission, behaviour is unchanged
- for users without the 'edit related contacts' permission, contacts that they have access to via permissioned relationships will be viewable (as now), but not editable (change).
5.5.0
ayduns
aidan.saunders@squiffle.uk
ayduns
aidan.saunders@squiffle.uk
https://lab.civicrm.org/dev/drupal/-/issues/34
Drupal8: Missing Date format in views configuration
2019-08-23T13:10:14Z
magnolia61
Drupal8: Missing Date format in views configuration
In the views configuration for events, using CiviCRM 5.5.2 on Drupal 8 the date format cannot be configured. Not sure what causes this, but thought it would be good to report.
**In CiviCRM/Drupal7 ** <br>
![Screenshot_from_2018-10-22_13...
In the views configuration for events, using CiviCRM 5.5.2 on Drupal 8 the date format cannot be configured. Not sure what causes this, but thought it would be good to report.
**In CiviCRM/Drupal7 ** <br>
![Screenshot_from_2018-10-22_13-38-49](/uploads/8e33c20c5252ab9a9efcd9f073059f4a/Screenshot_from_2018-10-22_13-38-49.png)
**In CiviCRM/Drupal8** <br>
![Screenshot_from_2018-10-22_13-38-50](/uploads/de3dc32c9cc66f4d5caea15d73552ea6/Screenshot_from_2018-10-22_13-38-50.png)
https://lab.civicrm.org/dev/core/-/issues/3546
Recipients in smart group are less than actual in group
2023-02-08T16:54:07Z
Ghost User
Recipients in smart group are less than actual in group
For some reason smart group is only sending to five people even though group has 47 and none have opted out of bulk mailing or email so not sure why the mailing interface is only calculating 5 recipients.
![Screen_Shot_2018-12-20_at_1.0...
For some reason smart group is only sending to five people even though group has 47 and none have opted out of bulk mailing or email so not sure why the mailing interface is only calculating 5 recipients.
![Screen_Shot_2018-12-20_at_1.05.06_PM](/uploads/03674ebbecba86a4c8c585f305bfe515/Screen_Shot_2018-12-20_at_1.05.06_PM.png)
![Screen_Shot_2018-12-20_at_1.05.35_PM](/uploads/d5054897492805c5403c6967df77edbb/Screen_Shot_2018-12-20_at_1.05.35_PM.png)
https://lab.civicrm.org/dev/core/-/issues/35
avoid template variable leakage when processing more than one recurring contr...
2023-04-28T01:39:33Z
jamie
avoid template variable leakage when processing more than one recurring contribution in a session
This bug happens if you have more than one iATS recurring contribution and an earlier contribution is assigned to a soft credit, but one or more later contributions are not assigned to a soft credit.
The later contributions have the sof...
This bug happens if you have more than one iATS recurring contribution and an earlier contribution is assigned to a soft credit, but one or more later contributions are not assigned to a soft credit.
The later contributions have the soft credit information inserted into their receipt because the email message template variables are not properly cleared.
iATS processes multiple recurring contributions in a single session via a cron job, so may be uniquely triggering this error (although the bug is with CiviCRM Core).
5.3.0
https://lab.civicrm.org/dev/drupal/-/issues/35
Drupal8: CiviCRM checks assume a single-database installation
2020-10-26T15:25:58Z
JonGold
Drupal8: CiviCRM checks assume a single-database installation
I typically set up CiviCRM in a separate database, with a single MySQL user granted the minimum necessary permissions to change both CMS and CRM.
Drupal8 is incorporating CiviCRM checks into Drupal - but I get the error message (with th...
I typically set up CiviCRM in a separate database, with a single MySQL user granted the minimum necessary permissions to change both CMS and CRM.
Drupal8 is incorporating CiviCRM checks into Drupal - but I get the error message (with the permissions below) that I don't have permission to create triggers on my database.
What's actually happening is I don't have permission to create triggers on the Drupal database. I can create triggers on the Civi db.
Below you can see the command I ran that bypassed the issue.
Since this blocks Drupal upgrades, it feels reasonably serious to resolve. I feel a little lost in D8 though - I was looking for `hook_requirement`, which is how I'd ordinarily add a status check in D7, but couldn't find it (except in the install file).
```
mysql> show grants for myorg_test@localhost;
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Grants for myorg_test@localhost |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'myorg_test'@'localhost' |
| GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, TRIGGER ON `myorg_test_civi`.* TO 'myorg_test'@'localhost' |
| GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES ON `myorg_test_drupal`.* TO 'myorg_test'@'localhost' |
| GRANT EXECUTE, ALTER ROUTINE ON FUNCTION `myorg_test_civi`.`civicrm_strip_non_numeric` TO 'myorg_test'@'localhost' |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
4 rows in set (0.00 sec)
mysql> GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, TRIGGER ON `myorg_test_drupal`.* TO 'myorg_test'@'localhost';
Query OK, 0 rows affected (0.00 sec)```
https://lab.civicrm.org/dev/financial/-/issues/35
Refunding a Contribution that has Sales Tax associated produces Validation Error
2018-11-10T13:56:41Z
KarinG
Refunding a Contribution that has Sales Tax associated produces Validation Error
Trying to isolate / reproduce some issues with Sales Taxes breaking them down into small bits; this is on 5.3.0
Add Contribution $100 -> Financial Type has Sales Tax associated with it 5% -> Contribution gets recorded as $105 (correctly...
Trying to isolate / reproduce some issues with Sales Taxes breaking them down into small bits; this is on 5.3.0
Add Contribution $100 -> Financial Type has Sales Tax associated with it 5% -> Contribution gets recorded as $105 (correctly):
![image](/uploads/fb7908806ae278e41fada823681616bf/image.png)
Edit -> change Contribution Status -> from Completed to Refunded -> hit Save;
![image](/uploads/c847a51745cedf80901b5d8d657293ae/image.png)
Net Amount really is $105 and Fee Amount really is $0 - changing them to anything else would be incorrect.
See https://github.com/civicrm/civicrm-core/pull/9948 for original discussion
https://lab.civicrm.org/dev/core/-/issues/3566
Public View link does not show from Scheduled and Sent screen
2022-06-11T14:54:15Z
seamuslee
Public View link does not show from Scheduled and Sent screen
When you view a list of scheduled and sent mailings you cannot access the Public View url link even tho the code suggests it should be available
When you view a list of scheduled and sent mailings you cannot access the Public View url link even tho the code suggests it should be available
5.10
https://lab.civicrm.org/dev/core/-/issues/36
send_reminder causes database error
2023-04-28T01:39:33Z
gremblebean
send_reminder causes database error
When running the send_reminder job on CiviCRM 4.7.31 on MariaDB 10.1.26-0+deb9u1 using:
`cli.php -s my.3ca.org.uk -u admin -p*** -e Job -a send_reminder`
It fails with:
```
DB Error: syntax error
Died during callApi
```
The full erro...
When running the send_reminder job on CiviCRM 4.7.31 on MariaDB 10.1.26-0+deb9u1 using:
`cli.php -s my.3ca.org.uk -u admin -p*** -e Job -a send_reminder`
It fails with:
```
DB Error: syntax error
Died during callApi
```
The full error log reads:
```
Mar 30 07:26:59 [info] $Fatal Error Details = Array
(
[callback] => Array
(
[0] => CRM_Core_Error
[1] => exceptionHandler
)
[code] => -2
[message] => DB Error: syntax error
[mode] => 16
[debug_info] => INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_schedule_id)
SELECT e.contact_id as contact_id, e.id as entity_id, "civicrm_participant" as entity_table, 21 as action_schedule_id
FROM civicrm_participant e
INNER JOIN civicrm_event_en_GB r ON e.event_id = r.id
INNER JOIN civicrm_contact c ON c.id = e.contact_id AND c.is_deleted = 0 AND c.is_deceased = 0
LEFT JOIN civicrm_action_log reminder ON reminder.contact_id = e.contact_id AND
reminder.entity_id = e.id AND
reminder.entity_table = 'civicrm_participant' AND
reminder.action_schedule_id = 21
WHERE (r.id IN ("84")) AND (r.is_active = 1) AND (r.is_template = 0) AND (e.status_id IN (1)) AND (reminder.id IS NULL) AND ('20180330072659' >= DATE_SUB(r.start_date, INTERVAL hour)) AND (DATE_SUB(20180330072659, INTERVAL 1 DAY ) <= r.start_date)
[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 ')) AND (DATE_SUB(20180330072659, INTERVAL 1 DAY ) <= r.start_date)' at line 10]
[type] => DB_Error
[user_info] => INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_schedule_id)
SELECT e.contact_id as contact_id, e.id as entity_id, "civicrm_participant" as entity_table, 21 as action_schedule_id
FROM civicrm_participant e
INNER JOIN civicrm_event_en_GB r ON e.event_id = r.id
INNER JOIN civicrm_contact c ON c.id = e.contact_id AND c.is_deleted = 0 AND c.is_deceased = 0
LEFT JOIN civicrm_action_log reminder ON reminder.contact_id = e.contact_id AND
reminder.entity_id = e.id AND
reminder.entity_table = 'civicrm_participant' AND
reminder.action_schedule_id = 21
WHERE (r.id IN ("84")) AND (r.is_active = 1) AND (r.is_template = 0) AND (e.status_id IN (1)) AND (reminder.id IS NULL) AND ('20180330072659' >= DATE_SUB(r.start_date, INTERVAL hour)) AND (DATE_SUB(20180330072659, INTERVAL 1 DAY ) <= r.start_date)
[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 ')) AND (DATE_SUB(20180330072659, INTERVAL 1 DAY ) <= r.start_date)' at line 10]
[to_string] => [db_error: message="DB Error: syntax error" code=-2 mode=callback callback=CRM_Core_Error::exceptionHandler prefix="" info="INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_schedule_id)
SELECT e.contact_id as contact_id, e.id as entity_id, "civicrm_participant" as entity_table, 21 as action_schedule_id
FROM civicrm_participant e
INNER JOIN civicrm_event_en_GB r ON e.event_id = r.id
INNER JOIN civicrm_contact c ON c.id = e.contact_id AND c.is_deleted = 0 AND c.is_deceased = 0
LEFT JOIN civicrm_action_log reminder ON reminder.contact_id = e.contact_id AND
reminder.entity_id = e.id AND
reminder.entity_table = 'civicrm_participant' AND
reminder.action_schedule_id = 21
WHERE (r.id IN ("84")) AND (r.is_active = 1) AND (r.is_template = 0) AND (e.status_id IN (1)) AND (reminder.id IS NULL) AND ('20180330072659' >= DATE_SUB(r.start_date, INTERVAL hour)) AND (DATE_SUB(20180330072659, INTERVAL 1 DAY ) <= r.start_date)
[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 ')) AND (DATE_SUB(20180330072659, INTERVAL 1 DAY ) <= r.start_date)' at line 10]"]
)
Mar 30 07:26:59 [info] $backTrace = #0 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/CRM/Core/Error.php(948): CRM_Core_Error::backtrace("backTrace", TRUE)
#1 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/packages/PEAR.php(921): CRM_Core_Error::exceptionHandler(Object(DB_Error))
#2 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/packages/DB.php(985): PEAR_Error->__construct("DB Error: syntax error", -2, 16, (Array:2), "INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_s...")
#3 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/packages/PEAR.php(575): DB_Error->__construct(-2, 16, (Array:2), "INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_s...")
#4 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/packages/PEAR.php(223): PEAR->_raiseError(Object(DB_mysqli), NULL, -2, 16, (Array:2), "INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_s...", "DB_Error", TRUE)
#5 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/packages/DB/common.php(1905): PEAR->__call("raiseError", (Array:7))
#6 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/packages/DB/mysqli.php(933): DB_common->raiseError(-2, NULL, NULL, "INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_s...", "1064 ** You have an error in your SQL syntax; check the manual that correspon...")
#7 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/packages/DB/mysqli.php(403): DB_mysqli->mysqliRaiseError()
#8 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/packages/DB/common.php(1216): DB_mysqli->simpleQuery("INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_s...")
#9 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/packages/DB/DataObject.php(2446): DB_common->query("INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_s...")
#10 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/packages/DB/DataObject.php(1635): DB_DataObject->_query("INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_s...")
#11 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/CRM/Core/DAO.php(392): DB_DataObject->query("INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_s...")
#12 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/CRM/Core/DAO.php(1348): CRM_Core_DAO->query("INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_s...", TRUE)
#13 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/Civi/ActionSchedule/RecipientBuilder.php(215): CRM_Core_DAO::executeQuery("INSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_s...")
#14 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/Civi/ActionSchedule/RecipientBuilder.php(156): Civi\ActionSchedule\RecipientBuilder->buildRelFirstPass()
#15 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/CRM/Core/BAO/ActionSchedule.php(360): Civi\ActionSchedule\RecipientBuilder->build()
#16 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/CRM/Core/BAO/ActionSchedule.php(375): CRM_Core_BAO_ActionSchedule::buildRecipientContacts(3, "20180330072659", (Array:3))
#17 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/api/v3/Job.php(186): CRM_Core_BAO_ActionSchedule::processQueue("20180330072659", (Array:3))
#18 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/Civi/API/Provider/MagicFunctionProvider.php(89): civicrm_api3_job_send_reminder((Array:3))
#19 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/Civi/API/Kernel.php(169): Civi\API\Provider\MagicFunctionProvider->invoke((Array:9))
#20 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/Civi/API/Kernel.php(100): Civi\API\Kernel->runRequest((Array:9))
#21 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/api/api.php(23): Civi\API\Kernel->runSafe("Job", "send_reminder", (Array:2), NULL)
#22 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/bin/cli.class.php(113): civicrm_api("Job", "send_reminder", (Array:2))
#23 /var/www/my.3ca.org.uk/web/wp-content/plugins/civicrm/civicrm/bin/cli.php(32): civicrm_cli->callApi()
#24 {main}
```
https://lab.civicrm.org/dev/core/-/issues/389
When using custom fields for smart group criteria with relative dates the gro...
2019-12-03T07:22:12Z
jasonobrown
When using custom fields for smart group criteria with relative dates the group does not respect the relative date over time
If you create a smart group using the relative (dynamic, rolling, "this week", etc...) dates for a custom field, once you save the smart group the dates are no longer relative. It creates/updates the group with static dates that match yo...
If you create a smart group using the relative (dynamic, rolling, "this week", etc...) dates for a custom field, once you save the smart group the dates are no longer relative. It creates/updates the group with static dates that match your relative dates at the time you save it.
https://issues.civicrm.org/jira/browse/CRM-20499e
5.8
https://lab.civicrm.org/dev/financial/-/issues/36
Bug, cannot import Contributions because the import requires the payment meth...
2019-07-31T20:48:05Z
justinfreeman (Agileware)
Bug, cannot import Contributions because the import requires the payment method, payment instrument ID, not the payment instrument label
Bug, cannot import Contributions because the import requires the payment method, payment instrument ID, not the payment instrument label.
For example: Contributions being imported with payment instrument (payment method) of "Credit card...
Bug, cannot import Contributions because the import requires the payment method, payment instrument ID, not the payment instrument label.
For example: Contributions being imported with payment instrument (payment method) of "Credit card", "Cheque" will fail to import. However if these labels are replaced with the values, 1 (Credit card) and 4 (Cheque) then the import will succeed.
Importing contribution payment_instrument_id is formatted in following line of code.
https://github.com/agileware/civicrm-core/blob/master/CRM/Utils/DeprecatedUtils.php#L246
Code gets the option Value instead of a Name, the contribution API accepts the payment_instrument by Value. Logic is updated in Utils to consider name instead of ID. This function is getting called from only Contribution import.
PR submitted, see https://github.com/civicrm/civicrm-core/pull/13125
Agileware Ref: CIVICRM-1103
5.17.0
justinfreeman (Agileware)
justinfreeman (Agileware)
https://lab.civicrm.org/dev/drupal/-/issues/36
Unfork zetacomponents/mail (also helps Drupal8)
2019-01-08T14:53:17Z
bgm
Unfork zetacomponents/mail (also helps Drupal8)
zetacomponents/mail was [forked](https://github.com/civicrm/zetacomponents-mail/tree/1.7-civi) in early 2017 for PHP 7 compatibility. However, the base branch has had updates since which fix the PHP issues, and also add a new features fo...
zetacomponents/mail was [forked](https://github.com/civicrm/zetacomponents-mail/tree/1.7-civi) in early 2017 for PHP 7 compatibility. However, the base branch has had updates since which fix the PHP issues, and also add a new features for STARTTLS that might be interesting (and solves issues such as: https://github.com/civicrm/zetacomponents-mail/pull/2)
I encounted this issue while playing around with composer and Drupal8 from scratch:
```
$ composer create-project drupal-composer/drupal-project:8.x-dev myproject --stability dev --no-interaction
$ cd myproject
$ composer require civicrm/civicrm-core:5.7.2 --prefer-dist
./composer.json has been updated
> DrupalProject\composer\ScriptHandler::checkComposerVersion
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for civicrm/civicrm-core 5.7.2 -> satisfiable by civicrm/civicrm-core[5.7.2].
- civicrm/civicrm-core 5.7.2 requires zetacomponents/mail dev-1.7-civi -> no matching package found.
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
[...]
```
This can be fixed by specifying the URL of CiviCRM's fork, but eh, if we can remove it, why not?
cc @jackrabbithanna @dsnopek
https://lab.civicrm.org/dev/core/-/issues/3602
Bounce processing fails for invalid unicode characters
2022-06-11T14:55:40Z
tschuettler
Bounce processing fails for invalid unicode characters
We received some bounces that where containing invalid unicode characters. Due to MySQL not accepting to write those incorrect string values to the database, the bounces are moved to the processed folder although they are not actually re...
We received some bounces that where containing invalid unicode characters. Due to MySQL not accepting to write those incorrect string values to the database, the bounces are moved to the processed folder although they are not actually recorded.
Error Log:
```
[info] $backTrace = #0 /var/www/drupal/sites/all/modules/civicrm/CRM/Core/Error.php(912): CRM_Core_Error::backtrace("backTrace", TRUE)
#1 [internal function](): CRM_Core_Error::exceptionHandler(Object(DB_Error))
#2 /var/www/drupal/sites/all/modules/civicrm/packages/PEAR.php(931): call_user_func((Array:2), Object(DB_Error))
#3 /var/www/drupal/sites/all/modules/civicrm/packages/DB.php(976): PEAR_Error->PEAR_Error("DB Error: unknown error", -1, 16, (Array:2), "INSERT INTO civicrm_mailing_event_bounce (event_queue_id , bounce_type_id , b...")
#4 /var/www/drupal/sites/all/modules/civicrm/packages/PEAR.php(564): DB_Error->DB_Error(-1, 16, (Array:2), "INSERT INTO civicrm_mailing_event_bounce (event_queue_id , bounce_type_id , b...")
#5 /var/www/drupal/sites/all/modules/civicrm/packages/DB/common.php(1905): PEAR->raiseError(NULL, -1, NULL, NULL, "INSERT INTO civicrm_mailing_event_bounce (event_queue_id , bounce_type_id , b...", "DB_Error", TRUE)
#6 /var/www/drupal/sites/all/modules/civicrm/packages/DB/mysql.php(895): DB_common->raiseError(-1, NULL, NULL, NULL, "1366 ** Incorrect string value: '\x81hrt ' for column 'bounce_reason' at row 1")
#7 /var/www/drupal/sites/all/modules/civicrm/packages/DB/mysql.php(328): DB_mysql->mysqlRaiseError()
#8 /var/www/drupal/sites/all/modules/civicrm/packages/DB/common.php(1216): DB_mysql->simpleQuery("INSERT INTO civicrm_mailing_event_bounce (event_queue_id , bounce_type_id , b...")
#9 /var/www/drupal/sites/all/modules/civicrm/packages/DB/DataObject.php(2438): DB_common->query("INSERT INTO civicrm_mailing_event_bounce (event_queue_id , bounce_type_id , b...")
#10 /var/www/drupal/sites/all/modules/civicrm/packages/DB/DataObject.php(1060): DB_DataObject->_query("INSERT INTO civicrm_mailing_event_bounce (event_queue_id , bounce_type_id , b...")
#11 /var/www/drupal/sites/all/modules/civicrm/CRM/Core/DAO.php(468): DB_DataObject->insert()
#12 /var/www/drupal/sites/all/modules/civicrm/CRM/Mailing/Event/BAO/Bounce.php(81): CRM_Core_DAO->save()
#13 /var/www/drupal/sites/all/modules/civicrm/api/v3/Mailing.php(316): CRM_Mailing_Event_BAO_Bounce::create((Array:6))
#14 /var/www/drupal/sites/all/modules/civicrm/Civi/API/Provider/MagicFunctionProvider.php(89): civicrm_api3_mailing_event_bounce((Array:5))
#15 /var/www/drupal/sites/all/modules/civicrm/Civi/API/Kernel.php(96): Civi\API\Provider\MagicFunctionProvider->invoke((Array:9))
#16 /var/www/drupal/sites/all/modules/civicrm/api/api.php(23): Civi\API\Kernel->run("Mailing", "event_bounce", (Array:5), NULL)
#17 /var/www/drupal/sites/all/modules/civicrm/CRM/Utils/Mail/EmailProcessor.php(381): civicrm_api("Mailing", "event_bounce", (Array:5))
#18 /var/www/drupal/sites/all/modules/civicrm/CRM/Utils/Mail/EmailProcessor.php(58): CRM_Utils_Mail_EmailProcessor::_process(TRUE, Object(CRM_Core_DAO_MailSettings))
#19 /var/www/drupal/sites/all/modules/civicrm/api/v3/Job.php(361): CRM_Utils_Mail_EmailProcessor::processBounces()
#20 /var/www/drupal/sites/all/modules/civicrm/Civi/API/Provider/MagicFunctionProvider.php(89): civicrm_api3_job_fetch_bounces((Array:1))
#21 /var/www/drupal/sites/all/modules/civicrm/Civi/API/Kernel.php(96): Civi\API\Provider\MagicFunctionProvider->invoke((Array:9))
#22 /var/www/drupal/sites/all/modules/civicrm/api/api.php(23): Civi\API\Kernel->run("Job", "fetch_bounces", (Array:1), NULL)
#23 /var/www/drupal/sites/all/modules/civicrm/CRM/Core/JobManager.php(134): civicrm_api("Job", "fetch_bounces", (Array:1))
#24 /var/www/drupal/sites/all/modules/civicrm/CRM/Core/JobManager.php(79): CRM_Core_JobManager->executeJob(Object(CRM_Core_ScheduledJob))
#25 /var/www/drupal/sites/all/modules/civicrm/api/v3/Job.php(99): CRM_Core_JobManager->execute(FALSE)
#26 /var/www/drupal/sites/all/modules/civicrm/Civi/API/Provider/MagicFunctionProvider.php(89): civicrm_api3_job_execute((Array:1))
#27 /var/www/drupal/sites/all/modules/civicrm/Civi/API/Kernel.php(96): Civi\API\Provider\MagicFunctionProvider->invoke((Array:9))
#28 /var/www/drupal/sites/all/modules/civicrm/api/api.php(23): Civi\API\Kernel->run("job", "execute", (Array:1), NULL)
#29 /var/www/drupal/sites/all/modules/civicrm/drupal/drush/civicrm.drush.inc(1560): civicrm_api("job", "execute", (Array:1))
#30 [internal function](): drush_civicrm_api("job.execute")
#31 /usr/share/php/drush/includes/command.inc(334): call_user_func_array("drush_civicrm_api", (Array:1))
#32 /usr/share/php/drush/includes/command.inc(208): _drush_invoke_hooks("civicrm-api", (Array:1), "civicrm")
#33 [internal function](): drush_command("job.execute")
#34 /usr/share/php/drush/includes/command.inc(175): call_user_func_array("drush_command", (Array:1))
#35 /usr/share/php/drush/drush.php(92): drush_dispatch((Array:27))
#36 /usr/share/php/drush/drush.php(61): _drush_bootstrap_and_dispatch()
#37 /usr/share/php/drush/drush.php(16): drush_main()
#38 {main}
```
I will create PR with a unit test.
5.11
https://lab.civicrm.org/dev/core/-/issues/37
Payment never completed when localizing Contribution statuses
2023-04-28T01:39:33Z
samuelsov
Payment never completed when localizing Contribution statuses
Same kind of problem that https://issues.civicrm.org/jira/browse/CRM-21791, in CRM_Core_Payment, the label is used instead of the name which cause problems when localizing / customizing contribution status label.
To reproduce :
* go to...
Same kind of problem that https://issues.civicrm.org/jira/browse/CRM-21791, in CRM_Core_Payment, the label is used instead of the name which cause problems when localizing / customizing contribution status label.
To reproduce :
* go to /civicrm/admin/options?gid=11&reset=1
* change the "Completed" label to anything else, e.g. "Terminé"
* make a payment using a contribution form page that goes through CRM_Core_Payment::doPayment (e.g. use Stripe extension processor)
* the transaction status is never set to "Completed"/"Terminé"
https://lab.civicrm.org/dev/drupal/-/issues/37
Drupal8: Clear Drupal caches after enabling extension
2021-03-26T10:46:30Z
colemanw
Drupal8: Clear Drupal caches after enabling extension
After enabling an extension (e.g. KAM) new menu callbacks are registered in `civicrm_menu` but not in Drupal, resulting in a 404 Not Found error when visiting pages provided by the extension. Manually clearing the Drupal cache fixes this...
After enabling an extension (e.g. KAM) new menu callbacks are registered in `civicrm_menu` but not in Drupal, resulting in a 404 Not Found error when visiting pages provided by the extension. Manually clearing the Drupal cache fixes this.
I suspect that Drupal caches are not being adequately cleared by CiviCRM, which is probably a low-level problem affecting more than just this.