Answers.Body: <p>I began to examine the case types more closely. Some had matching Name and Title, others did not. Previously, you could change titles but not the Name as they were created in the program files and had to remain as they were.</p>
  
  <p>In any case, next to the Name display there is a lock. I unlocked the lock and then saved. After doing this for each case type, everything began to work fine again. 
  I do not know why this worked nor if it will be permanent but for now, the program works fine.
  (btw, I had upgraded to Civicrm 4.7.4 before doing this, but the upgrade did not solve the problems at all)</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-22T02:20:31.480Z
Answers.LastActivityDate: 2016-03-22T02:20:31.480Z
Answers.UserDisplayName: Leslie
Answers.Body: <p>Woah! It looks like you've found a bug :(</p>
  
  <p>These critters pop up every now and again. The thing to do is to add it as an issue on issues.civicrm.org - stating:</p>
  
  <ol>
  <li><p>the error.</p></li>
  <li><p>which versions you're on.</p></li>
  <li><p>what you search for when it occurs.</p></li>
  <li><p>how to reproduce the same error.</p></li>
  <li><p>whether or not you are using any extensions - either custom made or generic.</p></li>
  </ol>
  
  <p>If you are using CiviCRM in a production environment, there's a case to be made for using the "Long Term Support" version (currently 4.6). This will have fewer new features being added, but is well-established and stable, unless there's a feature that you need on 4.7.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-16T14:56:15.887Z
Answers.Text: JohnFF, were you able to reproduce this?  Are you sure that this isn't an ACL permissions issue?
Answers.UserDisplayName: G H
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-16T17:40:56.263Z
Answers.Text: An acl issue causing a code warning? This is likely a null being pushed into a for loop. If perms it should fail nicely.
Answers.UserDisplayName: JohnFF
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-16T18:11:01.880Z
Answers.Text: I agree, but Leslie asked another question that looked like a potentail ACL problem:  http://civicrm.stackexchange.com/questions/10477/unable-to-access-clients-in-civicase
Answers.UserDisplayName: G H
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-16T14:40:36.910Z
Answers.LastActivityDate: 2016-03-16T14:40:36.910Z
Answers.UserDisplayName: JohnFF
Body: <p>I am using Wordpress 4.4.2 and recently upgraded to CiviCrm 4.7.3. 
  When I try to search for cases under the "find cases" menu, I keep getting the following error messages:</p>
  
  <p>Warning: Invalid argument supplied for foreach() in /home/hillcrest/www/www/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php on line 186</p>
  
  <p>Warning: Invalid argument supplied for foreach() in /home/hillcrest/www/www/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php on line 186</p>
  
  <p>Warning: Invalid argument supplied for foreach() in /home/hillcrest/www/www/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php on line 186</p>
  
  <p>Warning: Cannot modify header information - headers already sent by (output started at /home/hillcrest/www/www/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php:186) in /home/hillcrest/www/www/wp-content/plugins/civicrm/civicrm/CRM/Utils/System/Base.php on line 895</p>
  
Tags: <civicase>
Title: Why am I getting error messages when trying to search for cases in CiviCase?
ThreadText: # Why am I getting error messages when trying to search for cases in CiviCase?
  
  (Asked by: username_0 on 2016-03-16)
  
  I am using Wordpress 4.4.2 and recently upgraded to CiviCrm 4.7.3.
  When I try to search for cases under the "find cases" menu, I keep getting the following error messages:
  
  Warning: Invalid argument supplied for foreach() in /home/hillcrest/www/www/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php on line 186
  
  Warning: Invalid argument supplied for foreach() in /home/hillcrest/www/www/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php on line 186
  
  Warning: Invalid argument supplied for foreach() in /home/hillcrest/www/www/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php on line 186
  
  Warning: Cannot modify header information - headers already sent by (output started at /home/hillcrest/www/www/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php:186) in /home/hillcrest/www/www/wp-content/plugins/civicrm/civicrm/CRM/Utils/System/Base.php on line 895
  
  **Tags:** civicase
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2016-03-22. Score: 1
  
  I began to examine the case types more closely. Some had matching Name and Title, others did not. Previously, you could change titles but not the Name as they were created in the program files and had to remain as they were.
  
  In any case, next to the Name display there is a lock. I unlocked the lock and then saved. After doing this for each case type, everything began to work fine again.
  I do not know why this worked nor if it will be permanent but for now, the program works fine.
  (btw, I had upgraded to Civicrm 4.7.4 before doing this, but the upgrade did not solve the problems at all)
  
  
  ---
  
  ### Answer by username_1 on 2016-03-16. Score: 0
  
  Woah! It looks like you've found a bug :(
  
  These critters pop up every now and again. The thing to do is to add it as an issue on issues.civicrm.org - stating:
  
  1. the error.
  2. which versions you're on.
  3. what you search for when it occurs.
  4. how to reproduce the same error.
  5. whether or not you are using any extensions - either custom made or generic.
  
  If you are using CiviCRM in a production environment, there's a case to be made for using the "Long Term Support" version (currently 4.6). This will have fewer new features being added, but is well-established and stable, unless there's a feature that you need on 4.7.
  
  > **Comments:**
  > **username_2**: username_1, were you able to reproduce this?  Are you sure that this isn't an ACL permissions issue?  
  > **username_1**: An acl issue causing a code warning? This is likely a null being pushed into a for loop. If perms it should fail nicely.  
  > **username_2**: I agree, but username_0 asked another question that looked like a potentail ACL problem:  http://civicrm.stackexchange.com/questions/10477/unable-to-access-clients-in-civicase  
  
  ---
  
  