Body: <p>I installed the Transactional Mail Extension and after adjusting a needed Drupal CiviMail permission got it working.  </p>
  
  <p>After testing, I deleted the Transactional Mail pseudo mailing, to start fresh, but find that after doing that I get the yellow-screen-of-death and a missing ID error when an event registration or contribution is submitted.  I disabled the extension for now-- how do I fix this?</p>
  
  <p>Also, oddly in my tests, each sent email had a duplicate record with an unknown status.  Anyone know why?  Thanks.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-28T20:24:56.440Z
Comments.Text: Hi Larry - welcome to Civi SE!  It would probably be helpful for folks if you could include what versions of CiviCRM and Drupal you're using (as well as the extension version).
Comments.UserDisplayName: Lesley Carter - BackOffice
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-29T01:31:51.137Z
Comments.Text: Hi Larry. As well as the CiviCRM and drupal versions could you include the version of the extension you are using. I've just tried following you steps above (first by deleting a specific Transactional Mail pseudo mailing, then by deleting all of them). I wasn't able to replicate the error message. If you are able to identify the error in your civicrm ConfigAndLog log file that would be great too. There is a great extension https://civicrm.org/extensions/civicrm-log-viewer that enables you to easily view this file, that I would recommend installing if you haven't already.
Comments.UserDisplayName: Luke Stewart
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-29T22:06:43.407Z
Comments.Text: Thanks-- we are on Drupal 7.61 and CiviCRM 5.4.0.  The Transactional Mail extension is 1.0.1.  
  
  I did find this warning in the log: Nov 27 21:44:51  [warning] Deprecated Path: There is a setting (transactional_mailings) not correctly defined. You may see unpredictability due to this. CRM_Core_Setting::setItems
Comments.UserDisplayName: Larry K.
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-04T03:22:12.687Z
Comments.Text: are you on PHP 7.1 (or greater) by any chance? I've tracked down that depreciation warning and it looks to have been introduced to cope with changes in php. (Feel free to @ me in the reply so I get notified)
Comments.UserDisplayName: Luke Stewart
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-04T08:54:56.897Z
Comments.Text: Larry - can you paste the error statement that you get after event registration or after submitting the contribution?
Comments.UserDisplayName: jitendra - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-04T09:17:59.027Z
Comments.Text: Also - are you using the updated zip downloaded from https://github.com/fuzionnz/nz.co.fuzion.transactional? There were some fixes done recently to the extension eg https://github.com/fuzionnz/nz.co.fuzion.transactional/pull/26
Comments.UserDisplayName: jitendra - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-06T01:35:36.287Z
Comments.Text: @luke-stewart: We are still on PHP 5.6.31.  Planning to upgrade soon.
Comments.UserDisplayName: Larry K.
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-06T01:49:43.460Z
Comments.Text: The error we get is:  Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred.
  job_id is not valid : 16895
Comments.UserDisplayName: Larry K.
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-06T01:52:37.237Z
Comments.Text: Yes, using 1.0.1 from GitHub with 5/14/2018 dates.
Comments.UserDisplayName: Larry K.
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-07T10:53:41.473Z
Comments.Text: @LarryK. It seems related to the issue fixed https://github.com/fuzionnz/nz.co.fuzion.transactional/pull/26. Can you apply this patch and try again?
Comments.UserDisplayName: jitendra - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-07T10:54:22.790Z
Comments.Text: Or else you can click https://github.com/fuzionnz/nz.co.fuzion.transactional/archive/master.zip link and replace your extension with the same.
Comments.UserDisplayName: jitendra - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-11T02:13:11.453Z
Comments.Text: OK-- I removed the extension and replaced the existing files with the new ones, however now the extension list says it in not installed, and when I try to reinstall, I get a yellow screen: DB Error: already exists.  If I remove the folder and try to reinstall from Drush, I get Extension nz.co.fuzion.transactional could not be installed.
Comments.UserDisplayName: Larry K.
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-06-04T05:57:07.910Z
Comments.Text: @LarryK. The error during re-installation was a known problem which got fixed in https://github.com/fuzionnz/nz.co.fuzion.transactional/pull/36. Can you get the master version again and install https://github.com/fuzionnz/nz.co.fuzion.transactional/archive/master.zip?
Comments.UserDisplayName: jitendra - fuzion
Tags: <civimail><extension>
Title: Transactional Mail Extension Problem
ThreadText: # Transactional Mail Extension Problem
  
  (Asked by: username_0 on 2018-11-28)
  
  I installed the Transactional Mail Extension and after adjusting a needed Drupal CiviMail permission got it working.
  
  After testing, I deleted the Transactional Mail pseudo mailing, to start fresh, but find that after doing that I get the yellow-screen-of-death and a missing ID error when an event registration or contribution is submitted. I disabled the extension for now-- how do I fix this?
  
  Also, oddly in my tests, each sent email had a duplicate record with an unknown status. Anyone know why? Thanks.
  
  **Tags:** civimail, extension
  
  > **Comments:**
  > **username_1**: Hi Larry - welcome to Civi SE!  It would probably be helpful for folks if you could include what versions of CiviCRM and Drupal you're using (as well as the extension version).  
  > **username_2**: Hi Larry. As well as the CiviCRM and drupal versions could you include the version of the extension you are using. I've just tried following you steps above (first by deleting a specific Transactional Mail pseudo mailing, then by deleting all of them). I wasn't able to replicate the error message. If you are able to identify the error in your civicrm ConfigAndLog log file that would be great too. There is a great extension https://civicrm.org/extensions/civicrm-log-viewer that enables you to easily view this file, that I would recommend installing if you haven't already.  
  > **username_0**: Thanks-- we are on Drupal 7.61 and CiviCRM 5.4.0.  The Transactional Mail extension is 1.0.1.    I did find this warning in the log: Nov 27 21:44:51  [warning] Deprecated Path: There is a setting (transactional_mailings) not correctly defined. You may see unpredictability due to this. CRM_Core_Setting::setItems  
  > **username_2**: are you on PHP 7.1 (or greater) by any chance? I've tracked down that depreciation warning and it looks to have been introduced to cope with changes in php. (Feel free to @ me in the reply so I get notified)  
  > **username_3**: Larry - can you paste the error statement that you get after event registration or after submitting the contribution?  
  > **username_3**: Also - are you using the updated zip downloaded from https://github.com/fuzionnz/nz.co.fuzion.transactional? There were some fixes done recently to the extension eg https://github.com/fuzionnz/nz.co.fuzion.transactional/pull/26  
  > **username_0**: @luke-stewart: We are still on PHP 5.6.31.  Planning to upgrade soon.  
  > **username_0**: The error we get is:  Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred. job_id is not valid : 16895  
  > **username_0**: Yes, using 1.0.1 from GitHub with 5/14/2018 dates.  
  > **username_3**: @LarryK. It seems related to the issue fixed https://github.com/fuzionnz/nz.co.fuzion.transactional/pull/26. Can you apply this patch and try again?  
  > **username_3**: Or else you can click https://github.com/fuzionnz/nz.co.fuzion.transactional/archive/master.zip link and replace your extension with the same.  
  > **username_0**: OK-- I removed the extension and replaced the existing files with the new ones, however now the extension list says it in not installed, and when I try to reinstall, I get a yellow screen: DB Error: already exists.  If I remove the folder and try to reinstall from Drush, I get Extension nz.co.fuzion.transactional could not be installed.  
  > **username_3**: @LarryK. The error during re-installation was a known problem which got fixed in https://github.com/fuzionnz/nz.co.fuzion.transactional/pull/36. Can you get the master version again and install https://github.com/fuzionnz/nz.co.fuzion.transactional/archive/master.zip?  
  
  ---
  
  ## 0 answers
  
  