Answers.Body: <p>See if <a href="https://github.com/cividesk/com.cividesk.email.sparkpost/pull/77" rel="nofollow noreferrer">https://github.com/cividesk/com.cividesk.email.sparkpost/pull/77</a> fixes your problem.  It's been merged but there has not been a release of the sparkpost extension since then so either pull from git or apply the fix manually - it's only one line of code.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-06-10T15:52:38.707Z
Answers.Text: Thank you so much @Aidan. That worked and I was hoping it was as simple as an overlooked include in Sparkpost.setting.php. Hope they make this an official update as I can't be the only one to encounter this.
Answers.UserDisplayName: Karl Rudnick
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-13T10:43:13.760Z
Answers.Text: To confirm for anyone else the above change is now merged.
Answers.UserDisplayName: EagleUK
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-06-10T09:10:30.663Z
Answers.LastActivityDate: 2019-06-10T09:10:30.663Z
Answers.UserDisplayName: Aidan
Body: <p>We are running Wordpress 5.2.1 with CiviCRM 5.12.4. In trying to upgrade to 5.13.5, the database runs through the updates, but then we get the message: "The site is experiencing technical difficulties. Please check your site admin email inbox for instructions." Afterwards, the bottom of the page says "Powered by CiviCRM 5.13.5", but under System Status we get the warning "CiviCRM 5.12 has reached its end of life." indicating the upgrade process didn't run through to the end. Looking at the error_log, there is a fatal PHP error and stack trace which looks like" "PHP Fatal error:  Uncaught Error: Class 'CRM_Sparkpost' not found in /home/britstatt/test.sdcbcdream.org/wp-content/uploads/civicrm/ext/com.cividesk.email.sparkpost/settings/Sparkpost.setting.php:8, referer: <a href="https://test.sdcbcdream.org/wp-admin/admin.php?page=CiviCRM&amp;q=civicrm%2Fupgrade%2Fqueue%2Frunner&amp;reset=1&amp;qrid=CRM_Upgrade" rel="nofollow noreferrer">https://test.sdcbcdream.org/wp-admin/admin.php?page=CiviCRM&amp;q=civicrm%2Fupgrade%2Fqueue%2Frunner&amp;reset=1&amp;qrid=CRM_Upgrade</a>"</p>
  
  <p>We have been using the Sparkpost mail extension since summer of 2016 and have never experienced an issue during the many CiviCRM upgrades since then, so I don't think this is a particular issue with that extension, although I will also ping cividesk. Since the upgrade process has always worked seamlessly, I wanted to throw this out there to find out what might be the matter.</p>
  
  <p>Fwiw, I originally encountered the issue when upgrading from 5.10.3 to 5.13.5, but didn't dive into the error logs. So I ran the upgrade from 5.10.3 to 5.12.4 successfully, thinking doing the upgrade in steps might help. That worked fine, but the subsequent attempt to upgrade 5.12.4 to 5.13.5 generated the error again and I finally looked into the error log.</p>
  
  <p>Our live site is running fine at 5.10.3, but I always run upgrades on a test mirror site, so this is not critical except we really want to move to 5.13.x which is supposed to be the next ESR, I thought.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-06-10T04:55:09.580Z
Comments.Text: I posted the issue with cividesk at https://github.com/cividesk/com.cividesk.email.sparkpost/issues/79  There I attached the error log with the full stack trace so you can see what the upgrade script triggers to get to the fatal error point.
Comments.UserDisplayName: Karl Rudnick
Tags: <upgrade><sparkpost>
Title: Upgrade from CiviCRM 5.12.4 to 5.13.5 generates Sparkpost PHP fatal error
ThreadText: # Upgrade from CiviCRM 5.12.4 to 5.13.5 generates Sparkpost PHP fatal error
  
  (Asked by: username_0 on 2019-06-10)
  
  We are running Wordpress 5.2.1 with CiviCRM 5.12.4. In trying to upgrade to 5.13.5, the database runs through the updates, but then we get the message: "The site is experiencing technical difficulties. Please check your site admin email inbox for instructions." Afterwards, the bottom of the page says "Powered by CiviCRM 5.13.5", but under System Status we get the warning "CiviCRM 5.12 has reached its end of life." indicating the upgrade process didn't run through to the end. Looking at the error\_log, there is a fatal PHP error and stack trace which looks like" "PHP Fatal error: Uncaught Error: Class 'CRM\_Sparkpost' not found in /home/britstatt/test.sdcbcdream.org/wp-content/uploads/civicrm/ext/com.cividesk.email.sparkpost/settings/Sparkpost.setting.php:8, referer: <https://test.sdcbcdream.org/wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fupgrade%2Fqueue%2Frunner&reset=1&qrid=CRM_Upgrade>"
  
  We have been using the Sparkpost mail extension since summer of 2016 and have never experienced an issue during the many CiviCRM upgrades since then, so I don't think this is a particular issue with that extension, although I will also ping cividesk. Since the upgrade process has always worked seamlessly, I wanted to throw this out there to find out what might be the matter.
  
  Fwiw, I originally encountered the issue when upgrading from 5.10.3 to 5.13.5, but didn't dive into the error logs. So I ran the upgrade from 5.10.3 to 5.12.4 successfully, thinking doing the upgrade in steps might help. That worked fine, but the subsequent attempt to upgrade 5.12.4 to 5.13.5 generated the error again and I finally looked into the error log.
  
  Our live site is running fine at 5.10.3, but I always run upgrades on a test mirror site, so this is not critical except we really want to move to 5.13.x which is supposed to be the next ESR, I thought.
  
  **Tags:** upgrade, sparkpost
  
  > **Comments:**
  > **username_0**: I posted the issue with cividesk at https://github.com/cividesk/com.cividesk.email.sparkpost/issues/79  There I attached the error log with the full stack trace so you can see what the upgrade script triggers to get to the fatal error point.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-06-10. Score: 3 | Accepted answer
  
  See if <https://github.com/cividesk/com.cividesk.email.sparkpost/pull/77> fixes your problem. It's been merged but there has not been a release of the sparkpost extension since then so either pull from git or apply the fix manually - it's only one line of code.
  
  > **Comments:**
  > **username_0**: Thank you so much @username_1. That worked and I was hoping it was as simple as an overlooked include in Sparkpost.setting.php. Hope they make this an official update as I can't be the only one to encounter this.  
  > **username_2**: To confirm for anyone else the above change is now merged.  
  
  ---
  
  