Still several issues after OpenEMR upgrade to 5.0.1

(Craig Sparks) #1

We continue to encounter problems since the upgrade from 4.2.0 to 5.0.1 (6). The upgrade as far as db upgrade and file replacement seemed to have gone well, but we have encountered the following issues still.

  1. When typing date for entering DOB or other date values, it must be entered as SQL format (YYYY-MM-DD), if not then it reverts to today’s date. On a similar note, when searching patients by DOB the format must also be in that form, while with 4.2.0 could be entered as YYYYMMDD. Is this just a current bug? There was a post referencing this issue on these forums, but no response.

  2. NewCrop has had issues, when selecting NewCrop Admin role for a user the NewCrop portal loads, but pharmacies do not get the orders, but when setting the user to Physician role (either 3 of those types) an error is encountred. That error is a PHP warning: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /xd1/homes/hash/42/60/a16042/17/59/u145917/xxx/www/openemr/interface/eRxXMLBuilder.php on line 808, referer: https://xxx/openemr/interface/patient_file/summary/demographics.php?set_pid=5005

  3. Getting a lot of notices in the log with this bit: PHP Warning: A non-numeric value encountered in /xd1/homes/hash/42/60/a16042/17/59/u145917/XXX/www/openemr/library/ on line 1919, referer: https://XXX/openemr/interface/main/tabs/main.php

  4. When trying to browse the logs from the administration menu the tab just appears to load but never actually loads anything. After that nothing in the admin will load and I have to clear cookies and open a new browser tab to reload openemr (refresh does not help).

OpenEMR Version
I’m using OpenEMR version 5.0.1(6)

I’m using: Chrome, Edge

Operating System
I’m using: Linux, Windows

I know that is a lot to unpack, so hopefully somebody can point me in the right direction of something that might have gotten missed in the upgrade or an explanation of the issues. I am going to pour over the open issues on Github as well to see if any of them are documented.

(Stephen Waite) #2

hi @jexmex

  1. known issue but not seeing in reported issues so started it here, When typing date for entering DOB or other date values, it must be entered as SQL format (YYYY-MM-DD), if not then it reverts to today’s date. · Issue #2116 · openemr/openemr · GitHub

  2. thankful to your use of NewCrop because there haven’t been many reports

  3. PHP Warnings should be fixed before they cause problems or are deprecated

  4. Logs will load all of the days activity and can take quite a while to show so needs to be addressed.

(Craig Sparks) #3

One other log entry I just seen (and I am not sure why, since nobody is prescribing anything atm is this:

[Tue Jan 08 02:36:11.987650 2019] [php7:notice] [pid 29983] [client] SQL Error with statement:query failed: INSERT INTO list_options\n\t\t\t\t(list_id, option_id, title, seq)\n\t\t\tVALUES\n\t\t\t\t(?, ?, ?, ?);--Duplicate entry 'drug_route-19' for key 'PRIMARY'==>/xd1/homes/hash/42/60/a16042/17/59/u145917/XXX/www/openemr/interface/eRxStore.php at 382:sqlQuery, referer: https://XXX/openemr/interface/patient_file/summary/demographics.php?set_pid=290

So that might be related to the issues with NewCrop we are seeing.

(Stephen Waite) #4

@sjpadgett pointed out that you just need to set admin->globals-locale date format to desired setting to deal with above issue #1

(Craig Sparks) #5

We have tried that, it changes the display of the dates, but not how searching or entering the dates work.

(Stephen Waite) #6

just demo’ed it

after changing admin->globals->locale->Date Display Format to MM/DD/YYYY can enter dates like 6-16-71 while creating a new pt and have it correctly interpret 06/16/1971

search works too :slight_smile: