CiviCRM Community Forums (archive)

Hi,

All was well in CiviCRM 4.4.0 on WP 3.7.1 (once I inserted to patch to print case reports).  But when I upgraded to 4.4.1, CiviCase was disabled by the upgrade process.  After I enabled it and copied my Case Type xml files, I get these errors on the dashboard when I choose to display all cases (only the other user has created any cases):

Warning: Invalid argument supplied for foreach() in /home/neapplec/public_html/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php on line 148

Warning: Invalid argument supplied for foreach() in /home/neapplec/public_html/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php on line 148

Warning: Cannot modify header information - headers already sent by (output started at /home/neapplec/public_html/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php:148) in /home/neapplec/public_html/wp-includes/option.php on line 563

Warning: Cannot modify header information - headers already sent by (output started at /home/neapplec/public_html/wp-content/plugins/civicrm/civicrm/CRM/Case/XMLProcessor/Process.php:148) in /home/neapplec/public_html/wp-includes/option.php on line 564

And, when I attempt to create a new case, it hangs on a blank screen when I click Save.

Please Help!

Thanks,
e.

hey e:

1. can u apply this patch:

https://github.com/dlobo/civicrm-core/commit/28c8781b81cf9ae0c37a67b9fb4b4986fa733c24.patch

this might give u more details regarding the white scren

2. Can you check your case xml and ensure that you have some caseRoles there. No caseRoles triggers the notice, which in turn triggers the php warning. Alternatively you can turn notices off in your php.ini

lobo

Thanks for the quick replies!

Found the problem: I had copied the case xml files out of their old 'configuration' directory directly into the new 'xml' directory.  Once I moved 'configuration' into new 'xml' and moved the case xml files, the errors disappeared and I could create new cases.  Your patch allowed me to see that - thank you!  I then restored the code in Error.php after I confirmed all this worked.  Was I correct in restoring that error code?

The disabling of components happened to me on two separate installations, one specifically set up for case management and using pretty much only CiviCase so I would not have disabled it.  The other is our fundraising db, so campaigns are a big deal and would not have been disabled.  That had not happened to me in the past - hopefully, you good folks can track it down.

Thanks again - a case management db is my big project to complete by the end of the year and you really saved my bacon!
e.