Answers.Body: <p>It's nothing to be worried about, though it is a minor bug.  The <a href="https://github.com/civicrm/civicrm-core/blob/4.6.9/CRM/Contact/Form/Contact.php#L216" rel="nofollow">code there</a> happens to look for the value of <code>$defaults['is_deceased']</code> without checking to see if the <code>$defaults</code> array has a value with the key <code>is_deceased</code>.  Two things:</p>
  
  <ol>
  <li><p>You might record an issue at <a href="https://issues.civicrm.org" rel="nofollow">https://issues.civicrm.org</a> so it gets fixed.</p></li>
  <li><p>You should probably turn off the error messages if this is a production site.  In the Drupal admin menu, go to Configuration, then under Development see Logging and Errors.  Select <code>none</code> under "Error messages to display" and save the configuration.  (This, by the way, is why a notice like this goes unnoticed.)</p></li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-09T21:38:45.960Z
Answers.Text: I saw that advice on another error. Can I assume that by turning this off i will not miss other error messages that may be important?
Answers.UserDisplayName: Hock
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-09T22:34:29.590Z
Answers.Text: By turning this off, you and any other site admins won't see the errors on screen.  However, they will still be logged.  It's good to periodically check your Drupal and Apache/Nginx logs for issues like this.  The reason the default is to display the errors is that you probably want to see them while you're building the site.
Answers.UserDisplayName: Andie Hunt
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-10T06:18:47.833Z
Answers.Text: Thank you for your help. I now have identical copies on my Laptop and Desktop and feel confident with backup!...and no error messages. Thanks.
Answers.UserDisplayName: Hock
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-09T20:36:15.170Z
Answers.LastActivityDate: 2015-11-09T20:36:15.170Z
Answers.UserDisplayName: Andie Hunt
Body: <p>I get this message whenever I edit a contact:</p>
  
  <p>Notice: Undefined index: is_deceased in CRM_Contact_Form_Contact->preProcess() (line 216 of C:\Bitnami\civicrm-4.6.9-1\apps\civicrm\htdocs\sites\all\modules\civicrm\CRM\Contact\Form\Contact.php).</p>
  
  <p>Is this something I should be concerned about?</p>
  
  <p>Thanks, Ian</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-10-10T13:06:34.043Z
Comments.Text: I am seeing a variant of this: Notice: Undefined index: group in CRM_Contact_Form_Contact->postProcess() (line 880 of /var/www/website/sites/all/modules/civicrm/CRM/Contact/Form/Contact.php). I can't log in at https://lab.civicrm.org/ ...
Comments.UserDisplayName: regit55
Tags: <contacts><error>
Title: Notice: Undefined index: is_deceased
ThreadText: # Notice: Undefined index: is_deceased
  
  (Asked by: username_0 on 2015-11-09)
  
  I get this message whenever I edit a contact:
  
  Notice: Undefined index: is\_deceased in CRM\_Contact\_Form\_Contact->preProcess() (line 216 of C:\Bitnami\civicrm-4.6.9-1\apps\civicrm\htdocs\sites\all\modules\civicrm\CRM\Contact\Form\Contact.php).
  
  Is this something I should be concerned about?
  
  Thanks, Ian
  
  **Tags:** contacts, error
  
  > **Comments:**
  > **username_1**: I am seeing a variant of this: Notice: Undefined index: group in CRM_Contact_Form_Contact->postProcess() (line 880 of /var/www/website/sites/all/modules/civicrm/CRM/Contact/Form/Contact.php). I can't log in at https://lab.civicrm.org/ ...  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2015-11-09. Score: 2
  
  It's nothing to be worried about, though it is a minor bug. The [code there](https://github.com/civicrm/civicrm-core/blob/4.6.9/CRM/Contact/Form/Contact.php#L216) happens to look for the value of `$defaults['is_deceased']` without checking to see if the `$defaults` array has a value with the key `is_deceased`. Two things:
  
  1. You might record an issue at <https://issues.civicrm.org> so it gets fixed.
  2. You should probably turn off the error messages if this is a production site. In the Drupal admin menu, go to Configuration, then under Development see Logging and Errors. Select `none` under "Error messages to display" and save the configuration. (This, by the way, is why a notice like this goes unnoticed.)
  
  > **Comments:**
  > **username_0**: I saw that advice on another error. Can I assume that by turning this off i will not miss other error messages that may be important?  
  > **username_2**: By turning this off, you and any other site admins won't see the errors on screen.  However, they will still be logged.  It's good to periodically check your Drupal and Apache/Nginx logs for issues like this.  The reason the default is to display the errors is that you probably want to see them while you're building the site.  
  > **username_0**: Thank you for your help. I now have identical copies on my Laptop and Desktop and feel confident with backup!...and no error messages. Thanks.  
  
  ---
  
  