Answers.Body: <p>php8 is more noisy so that's part of it. Also your php.ini error_reporting is probably E_ALL, and you might even have WP_DEBUG_DISPLAY turned on (<a href="https://codex.wordpress.org/WP_DEBUG" rel="nofollow noreferrer">https://codex.wordpress.org/WP_DEBUG</a>)</p>
  <p>The install itself is probably fine, it's just that civi has tons of old code that needs bringing up to date and it's time-consuming to do that and to get it reviewed, so it happens slowly.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-04-02T19:07:29.080Z
Answers.Text: Thank you, we decided to downgrade to 7.4 for now, no need to be on 8.0 - all the errors are gone now.
Answers.UserDisplayName: themak
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-06-30T09:52:37.977Z
Answers.Text: Unfortunately support for PHP 7.4 will end on 28 Nov 2022. So there will be a need to be on 8.0.
Answers.UserDisplayName: Philipp Michael
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-06-30T10:12:39.017Z
Answers.Text: @Demerit Is there an CiviCRM official statement or at least an issue about those warnings? We don't want to change the error reporting level, because otherwise we might not notice "real" problematic warnings.
Answers.UserDisplayName: Philipp Michael
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-06-30T14:04:48.357Z
Answers.Text: I can't speak for CiviCRM LLC, I can just repeat what I wrote that "civi has tons of old code that needs bringing up to date and it's time-consuming to do that and to get it reviewed, so it happens slowly". If people are able to fund someone to do the code changes and then get someone to review those changes, that would help speed it up. The initial lab ticket was https://lab.civicrm.org/dev/core/-/issues/2201#note_68029.
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-04-02T02:20:59.523Z
Answers.LastActivityDate: 2022-04-02T02:20:59.523Z
Answers.UserDisplayName: Demerit
Body: <p>Latest Civi and WP - PHP 8 - Database is utf8mb4 and utf8mb4_unicode_ci</p>
  <p>I am getting these Undefined Array Key Warnings everywhere. Did I set up the database incorrectly or could it be something else?</p>
  <p>Examples:</p>
  <p>Warning: Undefined array key &quot;email&quot; in /home/prinyc/www/www/wp-content/uploads/civicrm/templates_c/en_US/%%6F/6F7/6F7BB438%%Contribution.tpl.php on line 42</p>
  <p>Warning: Undefined array key &quot;parseStreetAddress&quot; in /home/prinyc/www/www/wp-content/uploads/civicrm/templates_c/en_US/%%05/056/056C19FD%%street_address.tpl.php on line 23</p>
  <p><a href="https://i.sstatic.net/KgK12.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/KgK12.png" alt="enter image description here" /></a></p>
  
Tags: <wordpress><error><installation><install>
Title: Fresh Install WP & Civi - Undefined Array Key Warnings Everywhere
ThreadText: # Fresh Install WP & Civi - Undefined Array Key Warnings Everywhere
  
  (Asked by: username_0 on 2022-04-02)
  
  Latest Civi and WP - PHP 8 - Database is utf8mb4 and utf8mb4\_unicode\_ci
  
  I am getting these Undefined Array Key Warnings everywhere. Did I set up the database incorrectly or could it be something else?
  
  Examples:
  
  Warning: Undefined array key "email" in /home/prinyc/www/www/wp-content/uploads/civicrm/templates\_c/en\_US/%%6F/6F7/6F7BB438%%Contribution.tpl.php on line 42
  
  Warning: Undefined array key "parseStreetAddress" in /home/prinyc/www/www/wp-content/uploads/civicrm/templates\_c/en\_US/%%05/056/056C19FD%%street\_address.tpl.php on line 23
  
  [![enter image description here](https://i.sstatic.net/KgK12.png)](https://i.sstatic.net/KgK12.png)
  
  **Tags:** wordpress, error, installation, install
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-04-02. Score: 1 | Accepted answer
  
  php8 is more noisy so that's part of it. Also your php.ini error\_reporting is probably E\_ALL, and you might even have WP\_DEBUG\_DISPLAY turned on (<https://codex.wordpress.org/WP_DEBUG>)
  
  The install itself is probably fine, it's just that civi has tons of old code that needs bringing up to date and it's time-consuming to do that and to get it reviewed, so it happens slowly.
  
  > **Comments:**
  > **username_0**: Thank you, we decided to downgrade to 7.4 for now, no need to be on 8.0 - all the errors are gone now.  
  > **username_2**: Unfortunately support for PHP 7.4 will end on 28 Nov 2022. So there will be a need to be on 8.0.  
  > **username_2**: @username_1 Is there an CiviCRM official statement or at least an issue about those warnings? We don't want to change the error reporting level, because otherwise we might not notice "real" problematic warnings.  
  > **username_1**: I can't speak for CiviCRM LLC, I can just repeat what I wrote that "civi has tons of old code that needs bringing up to date and it's time-consuming to do that and to get it reviewed, so it happens slowly". If people are able to fund someone to do the code changes and then get someone to review those changes, that would help speed it up. The initial lab ticket was https://lab.civicrm.org/dev/core/-/issues/2201#note_68029.  
  
  ---
  
  