Answers.Body: <p>First of all, this is not really an error that would cause you any damage, so I would not classify it as an important bug. The name is 'strict warning', which means that it is a warning (not an error!) that the programmer has sinned against the PHP rules when a strict check has been done. So it should be fixed at some stage, but these type of warnings will never disappear entirely as they do not break anything.</p>
  
  <p>I assume you are now seeing those warning because you are a site admin? In most live sites 'normal' users will not see these warnings, but that needs to be configured in your CMS (Drupal, Joomla or Wordpress).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-16T12:45:39.820Z
Answers.Text: any suggestions on where we should log these ?  Clutter Jira?  A list somewhere?  I find many php notices can be useful to capture but not necessarily important.
Answers.UserDisplayName: Sonicthoughts
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-02T07:12:09.100Z
Answers.LastActivityDate: 2015-07-02T07:12:09.100Z
Answers.UserDisplayName: ErikH - CiviCooP
Answers.Body: <p>A fix can be made in the Drupal settings.php file.</p>
  
  <p>Add to the file: </p>
  
  <p>error_reporting(E_ALL &amp; ~E_STRICT);</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-02T20:22:16.870Z
Answers.LastActivityDate: 2015-07-02T20:22:16.870Z
Answers.UserDisplayName: joemaine
Body: <p>This seems to be a carry-over from:  <a href="http://forum.civicrm.org/index.php/topic,26411.0.html" rel="nofollow">http://forum.civicrm.org/index.php/topic,26411.0.html</a></p>
  
  <p>I'm now receiving this error:</p>
  
  <p>Strict warning: Non-static method CRM_Core_BAO_UFGroup::checkFieldsEmptyValues() should not be called statically, assuming $this from incompatible context in CRM_Profile_Form->postProcess() (line 1315 of /home//public_html/sites/all/modules/civicrm/CRM/Profile/Form.php)</p>
  
  <p>I just upgraded from 4.3</p>
  
  <p>now using
  - php 5.5
  - drupal 7.38
  - civiCRM 4.6.4 (a fresh install)</p>
  
  <p>Has a fix been found?</p>
  
  <hr>
  
  <h2>EDIT</h2>
  
  <p>...should have mentioned the php upgrade ;-)</p>
  
  <p>I was able to control the warnings in the php.ini in php5.4 - with php5.5 they reappeared and nothing I've been able to do in the php.ini or .htaccess has been able to remove them. (Drupal platform and the errors are only in the log...I'm just trying to reduce the numbers of "errors" I see)</p>
  
Tags: <profile>
Title: Strict warning: Non-static method CRM_Core_BAO_UFGroup
ThreadText: # Strict warning: Non-static method CRM_Core_BAO_UFGroup
  
  (Asked by: username_0 on 2015-07-02)
  
  This seems to be a carry-over from: <http://forum.civicrm.org/index.php/topic,26411.0.html>
  
  I'm now receiving this error:
  
  Strict warning: Non-static method CRM\_Core\_BAO\_UFGroup::checkFieldsEmptyValues() should not be called statically, assuming $this from incompatible context in CRM\_Profile\_Form->postProcess() (line 1315 of /home//public\_html/sites/all/modules/civicrm/CRM/Profile/Form.php)
  
  I just upgraded from 4.3
  
  now using
  - php 5.5
  - drupal 7.38
  - civiCRM 4.6.4 (a fresh install)
  
  Has a fix been found?
  
  ---
  
  ## EDIT
  
  ...should have mentioned the php upgrade ;-)
  
  I was able to control the warnings in the php.ini in php5.4 - with php5.5 they reappeared and nothing I've been able to do in the php.ini or .htaccess has been able to remove them. (Drupal platform and the errors are only in the log...I'm just trying to reduce the numbers of "errors" I see)
  
  **Tags:** profile
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-07-02. Score: 1 | Accepted answer
  
  First of all, this is not really an error that would cause you any damage, so I would not classify it as an important bug. The name is 'strict warning', which means that it is a warning (not an error!) that the programmer has sinned against the PHP rules when a strict check has been done. So it should be fixed at some stage, but these type of warnings will never disappear entirely as they do not break anything.
  
  I assume you are now seeing those warning because you are a site admin? In most live sites 'normal' users will not see these warnings, but that needs to be configured in your CMS (Drupal, Joomla or Wordpress).
  
  > **Comments:**
  > **username_2**: any suggestions on where we should log these ?  Clutter Jira?  A list somewhere?  I find many php notices can be useful to capture but not necessarily important.  
  
  ---
  
  ### Answer by username_0 on 2015-07-02. Score: 0
  
  A fix can be made in the Drupal settings.php file.
  
  Add to the file:
  
  error\_reporting(E\_ALL & ~E\_STRICT);
  
  
  ---
  
  