bradymiller wrote on Thursday, August 08, 2013:
Looks like I didn’t have enough coffee on board when I made that header change 
Just fixed this and committed to sourceforge (both master and rel-412 branch)
-brady
OpenEMR
bradymiller wrote on Thursday, August 08, 2013:
Hi,
Sounds like we should delay the e-lab improvements for a patch after testing by MD Support. Still unsure of release date; it’s pretty much dependent at this point on when I can set aside a couple good blocks of time (for some simple sanity testing with the packages and then the release).
That being said, please keep TESTING, TESTING, TESTING.
-brady
OpenEMR
bradymiller wrote on Friday, August 09, 2013:
Hi,
Keep TESTING, TESTING, TESTING. Likely will release next week (mid-week).
Here is the complete list of Release Feature (feel free to modify):
http://www.open-emr.org/wiki/index.php/Release_Features#Version_4.1.2
Note I placed the following at top with the goal of stressing the Interoperability features:
Interoperability Support with Electronic Transfer and Incorporation of Patient Records via Standardized Continuity of Care Records
If there’s a clearer way of stating this, let me know (it is describing the combination of EMRDirect’s electronic transfer feature of CCR documents via Direct combined with ZH Healthcare’s feature of incorporating CCR documents into OpenEMR’s database).
-brady
OpenEMR
bradymiller wrote on Friday, August 09, 2013:
Also,
While we are at it here is the planned release statement (again, feel free to modify/improve it):
http://www.open-emr.org/wiki/index.php/QA/Release_Process#Release_Statement
As above, again placing emphasis on the interoperability stuff.
-brady
OpenEMR
cmswest wrote on Sunday, August 11, 2013:
http://www.open-emr.org/wiki/index.php/Windows_Upgrade_4.1.1_to_4.1.2
just a minor note but it seems that #'s 6 & 7 are taken care of as single step:
so acl is updated at same time as database meaning can remove # 7?
bradymiller wrote on Monday, August 12, 2013:
Hi Stephen,
They are two different scripts. ACL is not updated/upgraded in the sql upgrade script and has it’s own upgrade mechanism.
-brady
OpenEMR
mdsupport wrote on Thursday, August 15, 2013:
In sql_upgrade output we get the following error:
UPGRADING ACCESS CONTROLS TO VERSION 1:
Checking to ensure all the proper ACL(access control list) are present:
ERROR, Multiple ‘Administrators’ group ‘write’ ACLs are present.
ERROR, Multiple ‘Physicians’ group ‘write’ ACLs are present.
ERROR, Multiple ‘Clinicians’ group ‘write’ ACLs are present.
Does ‘ERROR’ mean something was skipped or deleted?
Is it likely to cause any issues?
Thx.
bradymiller wrote on Thursday, August 15, 2013:
hi,
Remember making the acl_upgrade code rather fool proof with the goal of not messing customized settings up. But very odd to have duplicate ACL’s like that.
What does rest of the output look like?
-brady
OpenEMR
mdsupport wrote on Thursday, August 15, 2013:
Here is the complete log.
bradymiller wrote on Friday, August 16, 2013:
Hi,
No other glaring issues, but not sure what happens if you try to add an ACO to one of the ACL’s that is duplicated in future. Also, having duplicate ACL’s may cause odd behavior in OpenEMR. May want to clean that up, which can likely be done in Adminsitration->ACL->Advanced->ACL List.
-brady
OpenEMR
mdsupport wrote on Friday, August 16, 2013:
Thx. Will try it in test system.
bradymiller wrote on Saturday, August 17, 2013:
Hi Stephen,
To correct myself, we can remove step number 7, which I just did (I forgot that we are now doing this in step 6 script also).
Thanks,
-brady
OpenEMR
mdsupport wrote on Wednesday, August 28, 2013:
Hi Brady,
When PHP warnings are ‘ON’, the sql_upgrade showed PHP warnings on line 70. It relates to field_type clearly expecting to be a string but getting an array as the attached file var_dump shows.
Is this expected or with warnings off, just gets ignored?
Thx.
tmccormi wrote on Thursday, August 29, 2013:
It is important to clear up warnings like that during development. That kind of thing, particularly, can cause unexpected results.
–Tony
bradymiller wrote on Sunday, September 08, 2013:
Hi,
Warnings are usually benign, but always good to fix. Looks like it has to do with the globals inserts. If you have a fix, feel free to post it and then will get it into the codebase.
-brady
OpenEMR