Error on codes section after fresh install

corybrown wrote on Thursday, December 12, 2013:

Warning: in_array() expects parameter 2 to be array, null given in interface/patient_file/encounter/superbill_custom_full.php on line 529 > ICD9 Diagnosis

Warning: in_array() expects parameter 2 to be array, null given in interface/patient_file/encounter/superbill_custom_full.php on line 529 > CPT4 Procedure/Service

I’ve installed with xampp previously and have not experienced this. This is my first regular install on a linux server. Any idea what is causing this.

Thanks in advance.

tmccormi wrote on Thursday, December 12, 2013:

instructions for php.ini config indicate turning off warnings and notices.
openemr is full of that and needs someone to clean it up. any college
interns out there?

Tony McCormick

503-330-2239
On Dec 11, 2013 6:53 PM, “Cory Brown” corybrown@users.sf.net wrote:

Warning: in_array() expects parameter 2 to be array, null given in
interface/patient_file/encounter/superbill_custom_full.php on line 529 >
ICD9 Diagnosis

Warning: in_array() expects parameter 2 to be array, null given in
interface/patient_file/encounter/superbill_custom_full.php on line 529 >
CPT4 Procedure/Service

I’ve installed with xampp previously and have not experienced this. This
is my first regular install on a linux server. Any idea what is causing
this.

Thanks in advance.

Error on codes section after fresh installhttps://sourceforge.net/p/openemr/discussion/202505/thread/4c79cf0c/?limit=25#e31d

Sent from sourceforge.net because you indicated interest in
OpenEMR / Discussion / Help

To unsubscribe from further messages, please visit
SourceForge.net: Log In to SourceForge.net

corybrown wrote on Friday, December 13, 2013:

This did indeed fix the problem. I’m concerned with the recommendation of turning off warnings and notices. Seems like this would prevent us from seeing an real problem if one occurred. Thanks again for the info.

yehster wrote on Friday, December 13, 2013:

Turning display_error=off is a standard thing to do in a non-development environment. It only prevents that only prevents them from being sent to stdout.

Such warning and notices are still sent to the Apache log file for review.

tmccormi wrote on Saturday, December 14, 2013:

turning off warnings and notices in a production system only prevents the log file from getting to outrageously large and hard to read when there’s a real error.

developers should leave warnings on and fix them which they don’t.

tony