Answers.Body: <p>Those are warnings, not errors. It's simply PHP telling you that CiviCRM 4.2 is a rather old piece of software (which it is!). They will not prevent CiviCRM from working normally, certainly not for the brief time between now and when you get it upgraded further.</p>
  
  <p>I recommend you ignore them and proceed with the upgrade. The latest version of CiviCRM is more up-to-date so will not trigger php warnings.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-24T19:24:33.127Z
Answers.LastActivityDate: 2015-05-24T19:24:33.127Z
Answers.UserDisplayName: Coleman
Answers.Body: <p>Can you upgrade to a later version than 4.2.20? <a href="http://forum.civicrm.org/index.php?topic=26411.0" rel="nofollow">Some Googling</a> indicates this error may be solved in later versions.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-24T03:08:59.847Z
Answers.Text: It was suggested in an answer to another question that I update the 4.1.5 database in 4.2.xx then upgrade to a later release after that.
Answers.UserDisplayName: Vietyank
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-24T03:10:13.003Z
Answers.Text: Assuming you are on a dev/testing server with a copy of the database, I would now try to upgrade to the next version (despite these Strict warnings).
Answers.UserDisplayName: Laryn
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-24T03:12:41.807Z
Answers.Text: Okay. I'll try to update the database now then upgrade.
Answers.UserDisplayName: Vietyank
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-26T14:38:22.100Z
Answers.Text: Did it work? :)
Answers.UserDisplayName: Laryn
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-26T14:41:34.093Z
Answers.Text: update did not work.
Answers.UserDisplayName: Vietyank
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-26T14:46:36.947Z
Answers.Text: Sorry to hear it. Feel free to update the question above with more info in that case.
Answers.UserDisplayName: Laryn
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-24T03:07:21.253Z
Answers.LastActivityDate: 2015-05-24T03:07:21.253Z
Answers.UserDisplayName: Laryn
Body: <p>I am trying to upgrade from 4.1.5 to the latest CiviCRM but need to go through some intermediate releases to get there. I have installed 4.2.20 but get the following error dozens of times on each screen. </p>
  
  <blockquote>
    <p>Strict warning: Non-static method CRM_Core_Block::setTemplateValues()
    should not be called statically in CRM_Core_Block::setTemplateValues()
    (line 587 of</p>
  </blockquote>
  
  <p>Is there any way to get rid of it?</p>
  
Tags: <upgrade>
Title: Multiple error messages upon upgrade to CiviCRM 4.2.20
ThreadText: # Multiple error messages upon upgrade to CiviCRM 4.2.20
  
  (Asked by: username_0 on 2015-05-24)
  
  I am trying to upgrade from 4.1.5 to the latest CiviCRM but need to go through some intermediate releases to get there. I have installed 4.2.20 but get the following error dozens of times on each screen.
  
  > Strict warning: Non-static method CRM\_Core\_Block::setTemplateValues()
  > should not be called statically in CRM\_Core\_Block::setTemplateValues()
  > (line 587 of
  
  Is there any way to get rid of it?
  
  **Tags:** upgrade
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-05-24. Score: 2
  
  Those are warnings, not errors. It's simply PHP telling you that CiviCRM 4.2 is a rather old piece of software (which it is!). They will not prevent CiviCRM from working normally, certainly not for the brief time between now and when you get it upgraded further.
  
  I recommend you ignore them and proceed with the upgrade. The latest version of CiviCRM is more up-to-date so will not trigger php warnings.
  
  
  ---
  
  ### Answer by username_2 on 2015-05-24. Score: 1
  
  Can you upgrade to a later version than 4.2.20? [Some Googling](http://forum.civicrm.org/index.php?topic=26411.0) indicates this error may be solved in later versions.
  
  > **Comments:**
  > **username_0**: It was suggested in an answer to another question that I update the 4.1.5 database in 4.2.xx then upgrade to a later release after that.  
  > **username_2**: Assuming you are on a dev/testing server with a copy of the database, I would now try to upgrade to the next version (despite these Strict warnings).  
  > **username_0**: Okay. I'll try to update the database now then upgrade.  
  > **username_2**: Did it work? :)  
  > **username_0**: update did not work.  
  > **username_2**: Sorry to hear it. Feel free to update the question above with more info in that case.  
  
  ---
  
  