Development issueshttps://lab.civicrm.org/groups/dev/-/issues2022-12-13T17:36:37Zhttps://lab.civicrm.org/dev/core/-/issues/1997PayPal Standard redirect fails on WordPress2022-12-13T17:36:37ZkcristianoPayPal Standard redirect fails on WordPressStarting in CiviCRM 5.28 the following occurson any contribution or event page - shortcode, cleanurl, ugly url
- Complete a donation page using PayPal Standard
- Click continue
- Go To PayPal
- Make payment
- Return to merchant (either...Starting in CiviCRM 5.28 the following occurson any contribution or event page - shortcode, cleanurl, ugly url
- Complete a donation page using PayPal Standard
- Click continue
- Go To PayPal
- Make payment
- Return to merchant (either via auto return or clicking the return to merchant button)
![image](/uploads/bef50def6e6a1546e2a003c58e2b62fc/image.png)
Return URL is:
`https://wpcv.test/civicrm/?civiwp=CiviCRM&q=civicrm%2Fcontribute%2Ftransact&_qf_ThankYou_display=1&qfKey=1eeb07cdbc6ad45b89ca33a18ef246354bfffba1b89c76989d57f74685b5412a_1724`
**Contribution completes in CiviCRM, but the user is stuck on an error page**
From Log:
```
Sep 03 11:16:07 [info] $IDS Detector Details = Array
(
[0] => Array
(
[name] => custom
[value] => {"module":"contribute","contactID":"202","contributionID":160,"contributionPageID":1}
[page] => /civicrm/?civiwp=CiviCRM&q=civicrm%2Fcontribute%2Ftransact&_qf_ThankYou_display=1&qfKey=1eeb07cdbc6ad45b89ca33a18ef246354bfffba1b89c76989d57f74685b5412a_1724
[userid] =>
[session] => 59k48kf3tamh8oh6q1fo8220al
[ip] => x.x.x.x
[reaction] => 0
[impact] => 32
)
)
Sep 03 11:16:07 [error]
$Fatal Error Details = array(3) {
["message"]=>
string(627) "We can't load the requested web page. This page requires cookies to be enabled in your browser settings. Please check this setting and enable cookies (if they are
not enabled). Then try again. If this error persists, contact the site administrator for assistance.<br /><br />Site Administrators: This error may indicate that users are acce
ssing this page using a domain or URL other than the configured Base URL. EXAMPLE: Base URL is http://example.org, but some users are accessing the page via http://www.example.o
rg or a domain alias like http://myotherexample.org.<br /><br />Error type: Could not find a valid session key."
["code"]=>
NULL
["exception"]=>
object(CRM_Core_Exception)#2525 (10) {
["errorData":"CRM_Core_Exception":private]=>
array(1) {
["error_code"]=>
int(0)
}
["cause":protected]=>
NULL
["_trace":"PEAR_Exception":private]=>
NULL
["message":protected]=>
string(627) "We can't load the requested web page. This page requires cookies to be enabled in your browser settings. Please check this setting and enable cookie[1270/99292]
re not enabled). Then try again. If this error persists, contact the site administrator for assistance.<br /><br />Site Administrators: This error may indicate that users are ac
cessing this page using a domain or URL other than the configured Base URL. EXAMPLE: Base URL is http://example.org, but some users are accessing the page via http://www.example
.org or a domain alias like http://myotherexample.org.<br /><br />Error type: Could not find a valid session key."
```
```
Sep 03 11:16:09 [debug] PayPalIPN: Received (ContactID: 202; trxn_id: XXXXXXXXX).
Sep 03 11:16:09 [info] Contribution record updated successfully
Sep 03 11:16:09 [info] Receipt sent
Sep 03 11:16:09 [info] Success: Database updated
```
The session Id above matches the session ID in my browser console.5.30.0https://lab.civicrm.org/dev/core/-/issues/1996New CustomField structure causes issues with APIv32020-09-05T17:33:22ZBjörn EndresNew CustomField structure causes issues with APIv3Overview
----------------------------------------
It looks like the recent change in ``5.27`` in the way custom fields store multi-value information has had an impact on the APIv3. There has been some compatibility layer added to the API...Overview
----------------------------------------
It looks like the recent change in ``5.27`` in the way custom fields store multi-value information has had an impact on the APIv3. There has been some compatibility layer added to the APIv3, but that doesn't cover the search. So if an extension tries to find out whether a custom field has multiple values through the API, it used to ask for
```
html_type=>['IN'=>['CheckBox','Multi-Select','Multi-Select State/Province','Multi-Select Country']]
```
but that doesn't return any fields any more.
Reproduction steps
----------------------------------------
1. Create a multi-value custom field
1. Go to ``civicrm/api3``
1. Do ``CustomField.get`` with the ``html_type`` outlined above.
Current behaviour
----------------------------------------
Currently our multi-value custom field is not returned, even though in a search by ``id`` the ``html_type`` is listed as the ``Multi-*`` type we searched for in the first place.
Expected behaviour
----------------------------------------
The API compatibility wrapper should extend to the search parameters as well, i.e. the query should return the fields matching the query.
Environment information
----------------------------------------
__CiviCRM 5.27/5.28https://lab.civicrm.org/dev/core/-/issues/1994LineItem pre Hook non-standard on edit2020-09-06T19:44:12ZeileenLineItem pre Hook non-standard on editThe pre hook passes $params['entity_id'] for 'id' when it should pass null
```
$id = $params['id'] ?? NULL;
if ($id) {
CRM_Utils_Hook::pre('edit', 'LineItem', $id, $params);
}
else {
CRM_Utils_Hook::pre('crea...The pre hook passes $params['entity_id'] for 'id' when it should pass null
```
$id = $params['id'] ?? NULL;
if ($id) {
CRM_Utils_Hook::pre('edit', 'LineItem', $id, $params);
}
else {
CRM_Utils_Hook::pre('create', 'LineItem', $params['entity_id'], $params);
}
```
@lcdweb @JoeMurray @seamuslee @pradeep @monish.deb - can we fix this?5.30.0https://lab.civicrm.org/dev/core/-/issues/1993Proposal for CivICRM buttons to inherit the button styles from the website ra...2020-09-03T07:28:26Zjustinfreeman (Agileware)Proposal for CivICRM buttons to inherit the button styles from the website rather than injecting their own “CiviCRM” stylesProposal for CivICRM buttons to inherit the button styles from the website rather than injecting their own “CiviCRM” styles. This would make CiviCRM pages fit in visually with the website.Proposal for CivICRM buttons to inherit the button styles from the website rather than injecting their own “CiviCRM” styles. This would make CiviCRM pages fit in visually with the website.https://lab.civicrm.org/dev/core/-/issues/1992Proposal to remove the duplication of buttons that CiviCRM displays on Contri...2020-09-17T09:47:23Zjustinfreeman (Agileware)Proposal to remove the duplication of buttons that CiviCRM displays on Contribution and Event pages, often appearing both at the top and bottom of the page.Proposal to remove the duplication of buttons that CiviCRM displays on Contribution and Event pages, often appearing both at the top and bottom of the page. Many users think this is a bug and ask for the duplicate button(s) to be removed.Proposal to remove the duplication of buttons that CiviCRM displays on Contribution and Event pages, often appearing both at the top and bottom of the page. Many users think this is a bug and ask for the duplicate button(s) to be removed.https://lab.civicrm.org/dev/core/-/issues/1991Fix the counter-intuitive steps required to save a new CiviCRM Report, which ...2020-09-17T09:47:10Zjustinfreeman (Agileware)Fix the counter-intuitive steps required to save a new CiviCRM Report, which currently requires: Clicking the View the results button and then selecting Save Report from the Actions menuFix the counter-intuitive steps required to save a new CiviCRM Report, which currently requires: Clicking the View the results button and then selecting Save Report from the Actions menu.
What users actually expect to see as a button on...Fix the counter-intuitive steps required to save a new CiviCRM Report, which currently requires: Clicking the View the results button and then selecting Save Report from the Actions menu.
What users actually expect to see as a button on the CiviCRM Report page is just simple "Save report" as a button.
Having the action only shown after the results of the report are visible is the problem. This also prevents a report from being saved which does not currently show any results now, but may show results in the future - when the criteria is met.https://lab.civicrm.org/dev/core/-/issues/1990Installer: Fix URL-based installation for D7 (etc)2020-09-15T07:27:10ZtottenInstaller: Fix URL-based installation for D7 (etc)Overview
----------------------------------------
The current docs advise that you can install on Drupal by pasting the URL of the tarball:
![Screenshot_from_2020-09-02_21-09-41](/uploads/606118fc20edf3875046c932eea6cfa1/Screenshot_fro...Overview
----------------------------------------
The current docs advise that you can install on Drupal by pasting the URL of the tarball:
![Screenshot_from_2020-09-02_21-09-41](/uploads/606118fc20edf3875046c932eea6cfa1/Screenshot_from_2020-09-02_21-09-41.png)
This is not currently working.
Reproduction steps
----------------------------------------
1. Create an empty D7 site
1. Login as admin
1. Navigate to "Modules => Install New Module"
1. Give a URL like `https://download.civicrm.org/latest/civicrm-STABLE-drupal.tar.gz`
Current behavior
----------------------------------------
It shows an error, "Symbolic links are not allowed. Unable to extract"
![Screenshot_from_2020-09-02_20-23-59](/uploads/6ce32abfa465983f3e9cb880cf4eef56/Screenshot_from_2020-09-02_20-23-59.png)
Expected behavior
----------------------------------------
It downloads and extracts the tarball.
Environment information
----------------------------------------
<!-- Some of the items below may not be relevant for every bug - if in doubt please include more information than you think is neccessary. -->
* __CiviCRM:__ 5.28 or 5.29 (Most likely everything since 5.13 / 2f0db03468f8b0813e8e551e6674fda938b7b76a)
* __CMS:__ Drupal 7.x-devhttps://lab.civicrm.org/dev/drupal/-/issues/137D8 Install checks run via Drupal Status Report - give misleading warnings.2020-10-14T13:50:13Zluke.stewartD8 Install checks run via Drupal Status Report - give misleading warnings.**Problem:**
If the civicrm.settings.php file is not writable, a warning is showing on Drupal Status Report indicating that the civicrm.settings.php file should be writable by the webserver user. This also shows on the command line when...**Problem:**
If the civicrm.settings.php file is not writable, a warning is showing on Drupal Status Report indicating that the civicrm.settings.php file should be writable by the webserver user. This also shows on the command line when running some drush commands.
**Ideal solution:**
The reverse behaviour should be present. Ideally we should warn if civicrm.settings.php is writable by the web server user.
The drupal hook requirements is what is generating this error message.
**Details:**
There is an argument passed to this hook `$phase` that would allow us to target this behaviour.
Currently the behaviour is to use \Civi\Setup checkRequirements() which runs Civicrm Core's install requirements checks.
There is possibly some use in some of these requirements being checked and warnings displayed on the Drupal Status Report page - however there is currently no easy way to differentiate between checks that should only run at install time like the writability of civicrm.settings.php and those that make sense to run post install as well.
Currently the check to see if the user is authorised to run the install only runs when phase is set to install.
An initial solution is potentially to only run the check requirements on install. Then if additional metadata can be returned by `$setup->checkRequirements()->getMessages()` as to whether the warning should run on install or runtime, or checks performed inside civicrm core requirements checks to test for if civi is installed the change could be reverted.5.32.0https://lab.civicrm.org/dev/core/-/issues/1989E_WARNING when editing custom field with trigger-based logging turned on2020-09-06T20:47:11ZDaveDE_WARNING when editing custom field with trigger-based logging turned on1. Turn on logging (admin - system settings - misc).
2. Turn off popups so you can see the warning (admin - customize - display prefs) (or install the loudnotices extension).
3. Edit an existing custom field, e.g. just change the label, ...1. Turn on logging (admin - system settings - misc).
2. Turn off popups so you can see the warning (admin - customize - display prefs) (or install the loudnotices extension).
3. Edit an existing custom field, e.g. just change the label, or don't even do anything and just click save.
`Notice: Undefined index: ADD in CRM_Logging_Schema->fixSchemaDifferencesFor() (line 444 of .../CRM/Logging/Schema.php).`
`Warning: Invalid argument supplied for foreach() in CRM_Logging_Schema->fixSchemaDifferencesFor() (line 444 of .../CRM/Logging/Schema.php).`
This might be sort of recent just not sure yet when it started.5.31.0https://lab.civicrm.org/dev/core/-/issues/1988api attachment.get gives fatal error for custom file fields on cases2020-09-21T21:45:54ZDaveDapi attachment.get gives fatal error for custom file fields on casesI don't really believe in custom fields on cases, but if you happen to have one of type file, api attachment get fails on it with a fatal error "Failed to match record to related entity".
1. Create a custom field of type file for case...I don't really believe in custom fields on cases, but if you happen to have one of type file, api attachment get fails on it with a fatal error "Failed to match record to related entity".
1. Create a custom field of type file for cases.
2. Create a case and upload a file in the custom field.
3. Run something like `cv ev "var_dump(civicrm_api3('attachment', 'get', ['id' => 1]));"` where 1 is the corresponding id from civicrm_file. You'll get a fatal error.
4. You can also see it by:
1. Going to Find Cases.
1. Select the case you created.
1. Choose export from the actions dropdown.
1. Choose selected fields (ignore the E_WARNINGs).
1. Pick your custom field.
1. Click Download File.
1. Aside: I don't know why you would do this csv export because if it were working the column output is a time-limited url, so maybe is useful as input to another process, but I'm not sure what else.
It happens because the api goes through a couple central functions including Civi\API\Subscriber\DynamicFKAuthorization which tries to do a lookup by calling CRM_Core_BAO_CustomGroup::getTableNameByEntityName() to find out what table the custom field "extends", but it doesn't know about cases.
This appears to be a quick fix, but I'm not sure what weirdness this might introduce elsewhere, or whether the cases omission is on purpose.
```diff
diff --git a/CRM/Core/BAO/CustomGroup.php b/CRM/Core/BAO/CustomGroup.php
index 3a0dac33f1..435982d336 100644
--- a/CRM/Core/BAO/CustomGroup.php
+++ b/CRM/Core/BAO/CustomGroup.php
@@ -1164,6 +1164,10 @@ ORDER BY civicrm_custom_group.weight,
$tableName = 'civicrm_grant';
break;
+ case 'Case':
+ $tableName = 'civicrm_case';
+ break;
+
```5.31.0https://lab.civicrm.org/dev/wordpress/-/issues/73Trailing slash in Base Page URL resulting in 4042020-09-03T06:24:53ZgharrisTrailing slash in Base Page URL resulting in 404I'm not exactly sure where this bug showed up, but it was working before upgrading to WordPress 5.5/5.5.1 on CiviCRM 5.27.x. After upgrades, public pages using the Base Page resulted in 404 errors. Pages containing shortcodes continue ...I'm not exactly sure where this bug showed up, but it was working before upgrading to WordPress 5.5/5.5.1 on CiviCRM 5.27.x. After upgrades, public pages using the Base Page resulted in 404 errors. Pages containing shortcodes continue to work correctly. Removing the trailing slash from the Base Page URL, wp-admin/admin.php?page=CiviCRM&q=civicrm/admin/setting/uf&reset=1, immediately fixed the problem and the pages loaded as expected. (No cache clearing was necessary. Every form of cache clearing had been tried before making this change with no change in the results.) Adding the trailing slash back in resulted in 404's once again. This behavior was confirmed by Kevin. Here's the chat link with possibly a little more information: https://chat.civicrm.org/civicrm/pl/7rum7yt6jjgbjkw3ust4zmpfmh5.29.0https://lab.civicrm.org/dev/core/-/issues/1987Fix theme configuration section on Display preference and improve `isFrontend...2020-10-14T01:27:41Zswastik-compucorpFix theme configuration section on Display preference and improve `isFrontendPage` function for Drupal CMSProblem Motivation
----------------------------------------
While working on the Drupal web-forms, when we are using CiviCRM fields (like payment processors) on the Drupal webform pages, the CiviCRM current theme JS and CSS files were le...Problem Motivation
----------------------------------------
While working on the Drupal web-forms, when we are using CiviCRM fields (like payment processors) on the Drupal webform pages, the CiviCRM current theme JS and CSS files were leaking (rendering) on the Drupal webform page. This was making the page styling more difficult as one has to first reset the leaking CSS and then style on top of them. Also, there were some bootstrap JS libraries (when Shoreditch is the CiviCRM) file which was loading on the page. So, if a developer wants to develop a bootstrap based Drupal 7 themes and try to style the CiviCRM components, the Shoreditch bootstrap JS files conflicts with Drupal 7 bootstrap theme JS files.
To fix this we had to find a way to stop CiviCRM to apply its theme assets. The best way of it is to find a way in CiviCRM which will contextually select/deselect a CiviCRM theme on Drupal CMS pages. And apparently, the CiviCRM core provides such a feature under the display preference page to select different Front-end and Back-end theme. Unfortunately, this feature was not for Drupal CMS and hence the issue.
Problem Overview
----------------------------------------
For the Drupal CMS, the CiviCRM doesn't provide separate configurations for setting the frontend theme (FE) and the backend theme (BE). This is however present for other CMS integrations
For Drupal, on the Display Preference page, we only have one option for setting the global theme and it sets the BE only and the user can only set the BE.
![3ffa703e-9774-4224-abb0-c967b809dbef](/uploads/821e12db022a5accb4c5d8f7d8063ae3/3ffa703e-9774-4224-abb0-c967b809dbef.png)
The problem with this is that the Drupal User couldn't set the front end theme and the backend theme separately. So, to fix this we remove [the extra if logic](https://github.com/civicrm/civicrm-core/blob/master/templates/CRM/Admin/Form/Preferences/Display.tpl#L210-L225) just for Drupal CMS which hides the configuration for the FE-theme and BE-theme and loads the configuration for drupal as well. This will print both the configuration fields.
![3403e6d0-6a80-4e20-ac50-bd24190cc858](/uploads/d9efbd1d109e2bb15b0938debda8e32e/3403e6d0-6a80-4e20-ac50-bd24190cc858.png)
Also, the CiviCRM theme CSS was leaking on drupal pages too which uses the CiviCRM fields (and in turn called `civicrm_initialise()` function). This is because `$config->userSystem->isFrontEndPage()` function is buggy for Drupal CMS as it return `false` if the user opens a drupal public page. This is because [`isFrontEndPage()` function ](https://github.com/civicrm/civicrm-core/blob/master/CRM/Utils/System/DrupalBase.php#L658-L664))doesn't take care of the corner case of page URLs which are not CiviCRM's one. As it only checks if the URLs is a CiviCRM public URL
```
$item = CRM_Core_Menu::get($path);
// What if `$item` is empty?
return !empty($item['is_public']);
```
If `$item` is empty (that means it's a non-CiviCRM page) even then it returns `false` because the logic is incomplete. It doesn't check if the `$item` is empty.
This [fix](https://github.com/civicrm/civicrm-core/pull/18322) addresses both these issues.
Example use-case
----------------------------------------
1. Click on **Administration -> Customise data and screens -> Display preference**.
2. Go to `Theme` section
Current behaviour
----------------------------------------
![3ffa703e-9774-4224-abb0-c967b809dbef](/uploads/821e12db022a5accb4c5d8f7d8063ae3/3ffa703e-9774-4224-abb0-c967b809dbef.png)
Proposed behaviour
----------------------------------------
![3403e6d0-6a80-4e20-ac50-bd24190cc858](/uploads/d9efbd1d109e2bb15b0938debda8e32e/3403e6d0-6a80-4e20-ac50-bd24190cc858.png)5.31.0https://lab.civicrm.org/dev/core/-/issues/1986Propose altering the default of send notification to contributor checkbox on...2020-09-21T10:54:22ZeileenPropose altering the default of send notification to contributor checkbox on cancel or edit recurring to offWhen cancelling or updating a recurring contribution there is a checkbox to notify the contributor - this is checked by default.
I use this form a bit as a 'user' and often forget to uncheck it - which results in a pretty mindless commu...When cancelling or updating a recurring contribution there is a checkbox to notify the contributor - this is checked by default.
I use this form a bit as a 'user' and often forget to uncheck it - which results in a pretty mindless communication going out for what is usually either being done as part of a chain of communication with the donor (it's redundant) or an administrative change (the next scheduled date needs updating due to some oddity).
Because it's a rare-ish flow and 9 times out of 10 I mean to uncheck it I have never bothered to edit / maintain the message template.
I realise that I could add an extension to change the default - but my gut is that given I've seen it be problematic on 2 out of 2 sites it would probably be better that people actively choose to check the button rather than have to remember to uncheck it. If you forget to check it it's easy to send a quick email but impossible to recall if it you forget to uncheck it.5.31.0https://lab.civicrm.org/dev/core/-/issues/1985Reconsider logic for completing or cancelling contributions from Participant ...2023-04-25T05:03:23ZeileenReconsider logic for completing or cancelling contributions from Participant Batch UpdateOn digging into the code for participant batch status update in order to clean it up I found the logic rather esoteric.
If participation records are updated to have a different status contribution records are also updated IF all the fol...On digging into the code for participant batch status update in order to clean it up I found the logic rather esoteric.
If participation records are updated to have a different status contribution records are also updated IF all the following apply
1) the contribution has is_pay_later = 1
2) the contribution source is 'Online Event Registration'
3) the status is changed to one of 'Registered', 'Attended', 'Partially Paid', 'Pending Refund' - in which case the
contribution is updated to have a status of 'Completed'
OR
the status is changed to one of 'No Show', 'Cancelled', 'Rejected', 'Expired', 'Transferred' - in which case the
contribution is updated to have a status of 'Cancelled'
Given the diversity of flows through Civi now I rather wonder if this would not cause more confusion than leaving the contribution alone.....https://lab.civicrm.org/dev/core/-/issues/1995Profile and other forms user-friendly urls/aliases2023-04-25T05:03:24ZW01FProfile and other forms user-friendly urls/aliasesCurrently when you use a profile form (or contribute form, etc.) the path resembles something like:
/civicrm/profile/create?gid=15&reset=1
This is not very user-friendly or good for SEO, and there doesn't seem to be a way to fix this. F...Currently when you use a profile form (or contribute form, etc.) the path resembles something like:
/civicrm/profile/create?gid=15&reset=1
This is not very user-friendly or good for SEO, and there doesn't seem to be a way to fix this. For example, in a Drupal integration, attempting to set an alias for the path to something like "/register/blogger" will result in an access denied notice.
There are several reasons why a built-in path alias for profiles, contribute forms, etc. would be a good idea and I think it would be fairly simple to implement in the CiviCRM advanced settings for those forms.https://lab.civicrm.org/dev/drupal/-/issues/136Profile and other forms user-friendly urls/aliases2020-09-03T08:21:02ZW01FProfile and other forms user-friendly urls/aliasesCurrently when you use a profile form (or contribute form, etc.) the path resembles something like:
/civicrm/profile/create?gid=15&reset=1
This is not very user-friendly or good for SEO, and there doesn't seem to be a way to fix this. F...Currently when you use a profile form (or contribute form, etc.) the path resembles something like:
/civicrm/profile/create?gid=15&reset=1
This is not very user-friendly or good for SEO, and there doesn't seem to be a way to fix this. For example, in a Drupal integration, attempting to set an alias for the path to something like "/register/blogger" will result in an access denied notice.
There are several reasons why a built-in path alias for profiles, contribute forms, etc. would be a good idea and I think it would be fairly simple to implement in the CiviCRM advanced settings for those forms.https://lab.civicrm.org/dev/wordpress/-/issues/72register_rest_route was called incorrectly, missing permission_callback argum...2021-10-16T13:37:50Zryan_cogregister_rest_route was called incorrectly, missing permission_callback argument via wp-cliSeveral CiviCRM REST endpoints are being registered incorrectly with WordPress. The following messages occur when using wp-cli with Wordpress 5.5 and CiviCRM 5.28.3:
```
PHP Notice: register_rest_route was called <strong>incorrectly</s...Several CiviCRM REST endpoints are being registered incorrectly with WordPress. The following messages occur when using wp-cli with Wordpress 5.5 and CiviCRM 5.28.3:
```
PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/url</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/url</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/open</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/open</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/authorizeIPN</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/authorizeIPN</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/ipn</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/ipn</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/pxIPN</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/pxIPN</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/cxn</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/cxn</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/widget</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/widget</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/soap</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/soap</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
```https://lab.civicrm.org/dev/core/-/issues/1983Total Tax Amount on the Contribution (generated in backoffice/offline) no lon...2020-09-01T22:57:35ZKarinGTotal Tax Amount on the Contribution (generated in backoffice/offline) no longer adds up to sum of the Tax Amount for the individual line itemsThis is 5.28.x
![image](/uploads/95bbbea641887b9709aa6d28f16c472e/image.png)
I will look into this.
Issue: tax_amount on contribution = $0 -> but it should be: $35.09 in the screenshot above.This is 5.28.x
![image](/uploads/95bbbea641887b9709aa6d28f16c472e/image.png)
I will look into this.
Issue: tax_amount on contribution = $0 -> but it should be: $35.09 in the screenshot above.5.28.4https://lab.civicrm.org/dev/user-interface/-/issues/30Ability to Send Invoice with modified subject and CC it2020-09-22T02:41:28ZsunilAbility to Send Invoice with modified subject and CC itOverview
----------------------------------------
Ability to Send Invoice with CC email and with option to alter subject line.
Current behaviour
----------------------------------------
When Invoice Setting is Enabled at `CiviContribute...Overview
----------------------------------------
Ability to Send Invoice with CC email and with option to alter subject line.
Current behaviour
----------------------------------------
When Invoice Setting is Enabled at `CiviContribute Component Settings`, We get option to `Print Invoice` Or `Email Invoice`.
When we click on `Email Invoice`, we can choose From Address and Add additional Comment.
When Email Send:
For online payment form:
- Subject:`Contribution Invoice: Help Support CiviCRM!- Test User`
- BCC and CC emailed copied from Online page and used to send email.
For Offline Submission:
- Subject:`Invoice- Test User`
- BCC and CC : No possible
You can modify the subject, for that we need to alter the subject line in invoice template.
New behaviour
----------------------------------------
You can override Email Subject from UI, its optional, if you don't provide subject, default subject form invoice template get used.
CC Field is available. that will override online page CC email, and for offline payment its new option to send CC email.
![Screenshot_2020-08-29_at_7.54.52_AM](/uploads/0bcccfd49bc7a72697cdd97f604e12f3/Screenshot_2020-08-29_at_7.54.52_AM.png)
----------------------------------------
https://github.com/civicrm/civicrm-core/pull/182865.31.0https://lab.civicrm.org/dev/core/-/issues/1982Case open: doesn't respect case roles "creator" param if unset2020-09-01T22:57:35ZlcdwebCase open: doesn't respect case roles "creator" param if unsetto replicate:
1. create a new case type
2. in the list of case roles, uncheck the "assign to creator" checkbox for the default case coordinator role
3. create a new case on a contact record
**expected result:** no case roles created
*...to replicate:
1. create a new case type
2. in the list of case roles, uncheck the "assign to creator" checkbox for the default case coordinator role
3. create a new case on a contact record
**expected result:** no case roles created
**actual result:** case coordinator role is created and assigned to the logged in user5.29.0lcdweblcdweb