CiviCRM Core issueshttps://lab.civicrm.org/dev/core/-/issues2022-06-11T14:58:02Zhttps://lab.civicrm.org/dev/core/-/issues/3644Delivery summary doesn't show2022-06-11T14:58:02ZLoganBearDelivery summary doesn't showUpdated to CiviCRM 5.19 - ran one of our biweekly mailings last night and I wanted to check the open count. But Civi says that the mailing isn't completed,![Screen_Shot_2019-11-08_at_10.23.56_AM](/uploads/9723b265e4f977ffebce0033575d5291...Updated to CiviCRM 5.19 - ran one of our biweekly mailings last night and I wanted to check the open count. But Civi says that the mailing isn't completed,![Screen_Shot_2019-11-08_at_10.23.56_AM](/uploads/9723b265e4f977ffebce0033575d5291/Screen_Shot_2019-11-08_at_10.23.56_AM.png)
but the summary shows it's completed.![Screen_Shot_2019-11-08_at_10.23.41_AM](/uploads/24352601bef0fce245cc4198826cb937/Screen_Shot_2019-11-08_at_10.23.41_AM.png)5.19.1https://lab.civicrm.org/dev/core/-/issues/3589Report on scheduled mailing fails with Notice: Undefined property: CRM_Mailin...2022-06-11T14:55:03ZspalmstromReport on scheduled mailing fails with Notice: Undefined property: CRM_Mailing_BAO_Mailing::$mailing_job_start_date in <joomla_root>/administrator/components/com_civicrm/civicrm/CRM/Mailing/BAO/Mailing.php on line 2031This occurs in Joomla after upgrading to CiviCRM 5.19.0. Line 175 in /administrator/components/com_civicrm/civicrm/CRM/Mailing/DAO/MailingJob.php should read:
'start_date' => [
not
'mailing_job_start_date' => [This occurs in Joomla after upgrading to CiviCRM 5.19.0. Line 175 in /administrator/components/com_civicrm/civicrm/CRM/Mailing/DAO/MailingJob.php should read:
'start_date' => [
not
'mailing_job_start_date' => [5.19.1https://lab.civicrm.org/dev/core/-/issues/1371E Notice 'info' Extension.php:248 -> When installing via cv2019-11-08T01:28:44Zluke.stewartE Notice 'info' Extension.php:248 -> When installing via cvOn a wordpress install running 5.19.beta1 I get the following E Notice when running cv ext:download
`
Notice: Undefined variable: info in /wp-content/plugins/civicrm/civicrm/api/v3/Extension.php on line 248
`
This looks like it ...On a wordpress install running 5.19.beta1 I get the following E Notice when running cv ext:download
`
Notice: Undefined variable: info in /wp-content/plugins/civicrm/civicrm/api/v3/Extension.php on line 248
`
This looks like it was introduced in https://github.com/civicrm/civicrm-core/commit/19ec0aa50bafbe5748fba71a7d94b2e891051717
Which introduces a new parameter to the checkRequirements function, which defaults to NULL.
My reading of this is that the new Check Requirements functionality is only designed to work if executed via the UI. However, it looks like the info parameter is only populated if the 'url' param doesn't exist. If it does exist then the info parameter is not created.
As long as the UI doesn't call this function with a url param then this should be fine, but I'm wondering if it makes sense to populate the $info variable if a url is passed as a parameter to civicrm_api3_extension_download, a quick fix for the E Notice would be to simply initialise this variable to NULL.5.19.1https://lab.civicrm.org/dev/core/-/issues/1376Upgrade failure with 5.19 involving interaction between APIv4 and extensions2019-11-12T22:02:11ZjohnkUpgrade failure with 5.19 involving interaction between APIv4 and extensionsI have a Drupal based CiviCRM installation. Drupal is 8.7.9 and I've just upgraded (on my dev site) to 5.19.0. I found that I got an error:
```
Uncaught PHP Exception InvalidArgumentException: "The directory "/var/www/dev.acreresidency....I have a Drupal based CiviCRM installation. Drupal is 8.7.9 and I've just upgraded (on my dev site) to 5.19.0. I found that I got an error:
```
Uncaught PHP Exception InvalidArgumentException: "The directory "/var/www/dev.acreresidency.org/web/sites/default/files/civicrm/ext/org.civicrm.shoreditch/Civi/Api4/Service/Spec/Provider/" does not exist." at /var/www/dev.acreresidency.org/vendor/symfony/config/Resource/DirectoryResource.php line 36
```
I was able to get the site up and running, but I had to manually create a symlink within each of my CiviCRM extension directories (starting with org.civicrm.shoreditch, as in the log message here), named 'Civi' and pointing to my vendor/civicrm/civicrm-core/Civi directory.
There's something that's not got the right path set, I suppose. This seems like a bug, but it could also be something unusual about my installation environment. I use a composer setup. I'd like to better understand what the issue is, before I upgrade the main site to 5.19.5.19.1