Development issueshttps://lab.civicrm.org/groups/dev/-/issues2023-06-23T17:54:22Zhttps://lab.civicrm.org/dev/core/-/issues/19disabled optionvalues are not shown in participant export2023-06-23T17:54:22ZJoostdisabled optionvalues are not shown in participant exporta participant field has a custom field containing option values. Participants choose one of these option values. The option value that the participants chose gets disabled after they chose it. In a participant export containing this cust...a participant field has a custom field containing option values. Participants choose one of these option values. The option value that the participants chose gets disabled after they chose it. In a participant export containing this custom field the participants who chose for the disabled option will have a blanc space in the table on that location. Expected is having the option they chose over there, all-tough it has been disabled, and isn't available to choose any more.
to recreate this on a demo site:
1. create a participant to the fall fundraiser dinner with a soup preference
1. go to custom fields and edit the food preference custom field
1. deactivate the soup selection you chose in step 1
1. find participants to the fall fundraiser dinner
1. select all participants and export them using 'select fields to export'
1. select the fields to export:
- individual - display name to find the person you gave the food selection to
- participant - food preference: soup selection the field we are interested in
1. open the exported file. The soup selection for the disabled field isn't in there. When there are participants who chose for a soup that is still active the soup selection is in there for themhttps://lab.civicrm.org/dev/core/-/issues/21Regression: Public-facing contribution pages appearance changes on 4.7.312023-06-23T17:54:22ZJonGoldRegression: Public-facing contribution pages appearance changes on 4.7.31This is best expressed with screenshots. The first screenshot is 4.7.29 (sorry I don't have an easy 4.7.30 pic to show). The second screenshot is 4.7.31. This is replicable on the demo and I've noted the issue on Drupal, Backdrop and ...This is best expressed with screenshots. The first screenshot is 4.7.29 (sorry I don't have an easy 4.7.30 pic to show). The second screenshot is 4.7.31. This is replicable on the demo and I've noted the issue on Drupal, Backdrop and WP sites alike.
![Selection_428](/uploads/9511293346d743e242e48c10badb9478/Selection_428.png)
![Selection_429](/uploads/88d20617d122fe578bfa3087f6aead1b/Selection_429.png)https://lab.civicrm.org/dev/core/-/issues/22Unable to delete Smart Group2023-06-23T17:54:22ZKarinGUnable to delete Smart Groupcivicrm mysqli.php(933): DB_common->raiseError(-1, NULL, NULL, "CREATE TEMPORARY TABLE civicrm_temp_group_contact_cache1416 (SELECT 565 as gr...", "1139 ** Got error 'empty (sub)expression' from regexp")
post upgrade from 4.6 -> 4.7 -> ...civicrm mysqli.php(933): DB_common->raiseError(-1, NULL, NULL, "CREATE TEMPORARY TABLE civicrm_temp_group_contact_cache1416 (SELECT 565 as gr...", "1139 ** Got error 'empty (sub)expression' from regexp")
post upgrade from 4.6 -> 4.7 -> Smart Groups with Children are broken (can't view Contacts; can't Delete; can't edit Search Criteria); relevant part of the critical Error in ConfigAndLog:
#6 /var/www/civicrm/4.7/packages/DB/mysqli.php(933): DB_common->raiseError(-1, NULL, NULL, "CREATE TEMPORARY TABLE civicrm_temp_group_contact_cache1416 (SELECT 565 as gr...", "1139 ** Got error 'empty (sub)expression' from regexp")
Have advised client to recreate these Smart Groups; raising here for awareness;https://lab.civicrm.org/dev/core/-/issues/23Upgrade to version 4.7.31 seems to have broken DAO.PHP2023-06-23T17:54:22ZhetclubUpgrade to version 4.7.31 seems to have broken DAO.PHPVersion 4.7.31 was installed and now an hourly cron job is erroring like this:
"Parse error: syntax error, unexpected '[' in /.../administrator/components/com_civicrm/civicrm/CRM/Core/DAO.php on line 651.Version 4.7.31 was installed and now an hourly cron job is erroring like this:
"Parse error: syntax error, unexpected '[' in /.../administrator/components/com_civicrm/civicrm/CRM/Core/DAO.php on line 651.https://lab.civicrm.org/dev/core/-/issues/25Wrap split_jobs in a transaction2023-06-23T17:54:22ZseamusleeWrap split_jobs in a transactionThe split_jobs function should be wrapped in a MySQL transaction to ensure that no mailing can be delivered whilst we are still trying to populate the mailing_job table with all the necessary jobs.The split_jobs function should be wrapped in a MySQL transaction to ensure that no mailing can be delivered whilst we are still trying to populate the mailing_job table with all the necessary jobs.5.1.0seamusleeseamusleehttps://lab.civicrm.org/dev/core/-/issues/26On behalf form fails to create new organisation2023-04-28T01:39:32ZjitendraOn behalf form fails to create new organisationRelated SE - https://civicrm.stackexchange.com/questions/23137/existing-organization-getting-updated-instead-a-new-organization/24190
Steps to replicate -
- Set up Contribution page using 'on behalf of'
- Submit the form a first time,...Related SE - https://civicrm.stackexchange.com/questions/23137/existing-organization-getting-updated-instead-a-new-organization/24190
Steps to replicate -
- Set up Contribution page using 'on behalf of'
- Submit the form a first time, create your 'on behalf of' Org.
- Submit the form a second time for New Org, using new name/email
- Outcome the original Org now has the new email but the old name. Both contributions are on their record.https://lab.civicrm.org/dev/core/-/issues/27Move check for presence of the phone strip function to a Check (currently don...2023-04-28T01:39:33ZeileenMove check for presence of the phone strip function to a Check (currently done whenever a phone number is edited)5.40.0https://lab.civicrm.org/dev/core/-/issues/3568Improve process for creating plain text version of mailing2024-02-13T05:03:24ZMichael McAndrewImprove process for creating plain text version of mailing## Overview
Convert any html contained in tokens to plain text for plain text emails
## Before
HTML in tokens that contained HTML was being outputted to plain text versions of emails.
## After
HTML in tokens is converted to plain te...## Overview
Convert any html contained in tokens to plain text for plain text emails
## Before
HTML in tokens that contained HTML was being outputted to plain text versions of emails.
## After
HTML in tokens is converted to plain text.
## Technical Details
This issue is NOT about generating plain text and HTML versions of tokens. It is about converting an entire email from HTML to plain text when no plain text version is given. This conversion currently proceeds as follows:
1. Check to see if a plain text version has been submitted. If not
2. Convert the HTML to plain text
3. Do token substitution
The problem is that if the token contains html, that HTML persists in the email. The proposed solution is to do the conversion from HTML to plain text after token substitution, i.e.
1. Check to see if a plain text version has been submitted. If not
2. Convert the HTML to plain text
3. Do token substitution
This patch is split between [PR 12061 on core](https://github.com/civicrm/civicrm-core/pull/12061) and [PR 20 on flexmailer](https://github.com/civicrm/org.civicrm.flexmailer/pull/20).
The flexmailer patch will continue to report a single failure until the core patch is merged, at which point we can hopefully run the tests against flexmailer again and merge this patch.
@totten suggested defining tokens with TokenProcessor, whose tokens auto-convert from HTML to plain text and visa versa. However, I am not sure this is going to work for the following reason. When you convert from HTML to plain text (at least with the HTML to plain text converter that we are using) the structure of the text is altered and links appear at the bottom of the converted text. Therefore, if you run multiple conversions, you will get multiple lists of links scattered throughout the email. Best to do html to plain text conversion at the end of the process.
All this is not to say that one shouldn't define plain text and HTML versions of tokens. I think it is fine to do that if you want to. I just think that automatic conversion of HTML to plain text should happen one time only, after the entire email has been assembled.
Note that [PR 12061 on core](https://github.com/civicrm/civicrm-core/pull/12061) removes the check for nofollow in the email html output of the test CRM_Mailing_BaseMailingSystemTest::testHtmlWithOpenAndUrlTracking. The intent of https://issues.civicrm.org/jira/browse/CRM-21768 is not affected. nofollow still appears in the public view (e.g. http://example.org/civicrm/mailing/view) but it is not tested.
I would have added it to a test of civicrm/mailing/view but I could not find any tests there.
This issue was originally discussed here: https://issues.civicrm.org/jira/browse/CRM-21197 and a PR submitted here: https://github.com/civicrm/civicrm-core/pull/10998. But the PR was rejected because it caused issues with Flexmailer.
Also, on the seperate issue of click tracking plain text emails. @totten - you said [here](https://github.com/civicrm/civicrm-core/pull/10998#discussion_r158175327) that you thought it was a significant policy change. It isn't as significant as you think. *Links that are tracked in HTML continue to be tracked in plain text*. Links that are not tracked in HTML (because they were not in an `<a>` tag) are not tracked in plain text either. i.e. there is no significant loss of functionality.https://lab.civicrm.org/dev/core/-/issues/28For repeating Events, the absolute Registration Start / End date is transferr...2023-04-28T01:39:33Zjustinfreeman (Agileware)For repeating Events, the absolute Registration Start / End date is transferred to each of the repeated events which causes future events to be closed for sign-ups on creationFor repeating Events, the absolute Registration Start / End date is transferred to each of the repeated events which causes future events to be closed for sign-ups on creation.
The fields are:
Registration Start Date / Time
Registration...For repeating Events, the absolute Registration Start / End date is transferred to each of the repeated events which causes future events to be closed for sign-ups on creation.
The fields are:
Registration Start Date / Time
Registration End Date / Time
It makes more sense for repeating events, that these dates need to be set relative to the event date.
This could be an overall enhancement to make these date fields relative for all events, not just repeating. Which would make more sense. Especially since that applies also to copying an event as well as setting up a repeating event.
As it stands now, repeating events with Registration Start and Registration End need to be manually updated after creation. Otherwise, no one can register for those events.
Agileware Ref: CIVICRM-841https://lab.civicrm.org/dev/core/-/issues/29Joomla Menu Item - Event Registration - Unable to choose event2023-04-28T01:39:33ZADG CreativeJoomla Menu Item - Event Registration - Unable to choose eventWhen creating a Joomla Menu Item to point to an Event Registration page, the dropdown for choosing an event is empty although there are current active events that should be populating.
This is affecting version 4.7.31, our sites running...When creating a Joomla Menu Item to point to an Event Registration page, the dropdown for choosing an event is empty although there are current active events that should be populating.
This is affecting version 4.7.31, our sites running 4.7.30 are not encountering this problem.
Type Event Registration is the only one that seems to be having an issue, all other types work as expected.
Joomla Versions: 3.8.4, 3.8.6Monish DebMonish Debhttps://lab.civicrm.org/dev/core/-/issues/30Exporting master address contact even if no master address contact is defined2023-04-28T01:39:33ZsamuelsovExporting master address contact even if no master address contact is definedExporting "Master address contact" should give the master contact only if there is a master_id defined for this address but currently, if there is no master_id, the first master address id found for this contact is used.
```php
class C...Exporting "Master address contact" should give the master contact only if there is a master_id defined for this address but currently, if there is no master_id, the first master address id found for this contact is used.
```php
class CRM_Contact_BAO_Contact extends CRM_Contact_DAO_Contact {
...
public static function getMasterDisplayName($masterAddressId = NULL, $contactId = NULL) {
$masterDisplayName = NULL;
$sql = NULL;
if (!$masterAddressId && !$contactId) {
return $masterDisplayName;
}
if ($masterAddressId) {
$sql = "
SELECT display_name from civicrm_contact
LEFT JOIN civicrm_address ON ( civicrm_address.contact_id = civicrm_contact.id )
WHERE civicrm_address.id = " . $masterAddressId;
}
// ==> is there any reason to do that ?
elseif ($contactId) {
$sql = "
SELECT display_name from civicrm_contact cc, civicrm_address add1
LEFT JOIN civicrm_address add2 ON ( add1.master_id = add2.id )
WHERE cc.id = add2.contact_id AND add1.contact_id = " . $contactId;
}
$masterDisplayName = CRM_Core_DAO::singleValueQuery($sql);
return $masterDisplayName;
}
```5.3.0https://lab.civicrm.org/dev/core/-/issues/32Add option to disable cancel button on a profile form2023-04-28T01:39:33ZjitendraAdd option to disable cancel button on a profile formWhile setting up "subscribe" and "contact us" forms for a site, the default behaviour for a wordpress profile form of type "create" embedded via a shortcode is to show a cancel button.
This isn't really necessary for a single page form...While setting up "subscribe" and "contact us" forms for a site, the default behaviour for a wordpress profile form of type "create" embedded via a shortcode is to show a cancel button.
This isn't really necessary for a single page form with no existing data in it - but there doesn't appear to be a way to disable it.5.4.0https://lab.civicrm.org/dev/wordpress/-/issues/1CiviCRM-WordPress - Gutrenberg Compatibility: Do not parse shortcodes in REST...2023-01-25T14:59:08ZkcristianoCiviCRM-WordPress - Gutrenberg Compatibility: Do not parse shortcodes in REST contextWordPress 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/core/-/issues/33CiviCRM-WordPress - Do not parse shortcodes in REST context2023-04-28T01:39:33ZkcristianoCiviCRM-WordPress - Do not parse shortcodes in REST contextWordPress 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/core/-/issues/34Split edit/view access on permissioned relationships2023-04-28T01:39:33Zaydunsaidan.saunders@squiffle.ukSplit edit/view access on permissioned relationshipsCurrently, 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.0aydunsaidan.saunders@squiffle.ukaydunsaidan.saunders@squiffle.ukhttps://lab.civicrm.org/dev/core/-/issues/35avoid template variable leakage when processing more than one recurring contr...2023-04-28T01:39:33Zjamieavoid template variable leakage when processing more than one recurring contribution in a sessionThis 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.0https://lab.civicrm.org/dev/core/-/issues/36send_reminder causes database error2023-04-28T01:39:33Zgremblebeansend_reminder causes database errorWhen 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/37Payment never completed when localizing Contribution statuses2023-04-28T01:39:33ZsamuelsovPayment never completed when localizing Contribution statusesSame 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/core/-/issues/38Recurring Contribution Information on Membership Modal2018-05-29T18:22:20ZCamilo RodríguezRecurring Contribution Information on Membership Modal## Overview
Currently, when viewing a membership from contact's detailed view (on memberships tab), it is hard to tell if a membership has any recurring contributions associated to it, even though you can see all payments done for the me...## Overview
Currently, when viewing a membership from contact's detailed view (on memberships tab), it is hard to tell if a membership has any recurring contributions associated to it, even though you can see all payments done for the membership. It would be good if you could see both payments and recurring contributions associated to the membership, similar to how both are shown on Contact's contribution tab.
## How it Works Currently
1. Go to a contact with that has memberships, contributions and recurring contributions.
2. Click on memberships tab.
3. Click the **view** action on a membership.
4. Membership details are shown, including payments. Recurring contributions are not shown.
## How it Should Work
1. Go to a contact with that has memberships, contributions and recurring contributions.
2. Click on memberships tab.
3. Click the **view** action on a membership.
4. Membership details are shown, including payments. Recurring contributions are also shown, just after the table with membership contributions.
## Accepatance Criteria
* Relabel the "Related Contributions" accordion to "Related Contributions and Recurring Contributions".
* A contributions section is shown on the accordion showing a table of all contributions that are linked to the membership.
* A recurring contribution section showing a table of all recurring contributions that are linked to the membership.
* The recurring contributions section should reuse the recurring contribution table structure in Contact's contribution tab.
* Actions for recurring contributions work as in contributions Tab.5.3.0https://lab.civicrm.org/dev/core/-/issues/39Feature: Price set expire on/active on dates relative to event2023-12-14T05:03:25ZjiryuFeature: Price set expire on/active on dates relative to eventMigrated from https://issues.civicrm.org/jira/browse/CRM-21860
I reuse one price set for many similar events throughout the year; for each event, people can register early and get a discount, or register closer to the event's start date...Migrated from https://issues.civicrm.org/jira/browse/CRM-21860
I reuse one price set for many similar events throughout the year; for each event, people can register early and get a discount, or register closer to the event's start date at full price. A price set's active/expire dates works for this, but because they are absolute dates this prevents the price set from being reused for events with different start dates.
I propose active/expire dates for a price set that are relative to the event start date.