4.0 patching

aethelwulffe wrote on Tuesday, March 22, 2011:

Hey guys,
I am looking for some advice on patching 4.0.  The first “release” is about a week away, and I hope to take advantage of it.

My 4.0 files on my active install are dated FEB 9.  I have attempted several methods of wiping out the openemr directory, replacing the documents, edi/era directories etc… and running on the new files, I wind up with a new database.  I have tried changing the setup bool from 0 to 1 and it leaves me with either the new database, or being unable to connect “make sure mysqldb.exe is running”.   I have THOUGHT I had the correct passwords and such, but perhaps I am just the idiot I was raised to be.
  I have tried to use a file merge utility to update versions, but the darn thing keeps locking up (too many files).  What is the “real” way to patch a file set? 

aethelwulffe wrote on Tuesday, March 22, 2011:

OK, I guess I have not been getting my sqlconf.php right.  I also thought there MIGHT be some changes to the DB structure since February, but I guess not, Ja?  If not, then I imagine I have worked everything out and can proceed to altering some of the files I have customized from previous versions….

bradymiller wrote on Wednesday, March 23, 2011:

hey,
Can’t use setup script for an upgrade.
Here are upgrade instructions for 3.2 through 4.0:
LINUX: http://www.openmedsoftware.org/wiki/Linux_Upgrade_3.2.0_to_4.0.0
WINDOWS: http://www.openmedsoftware.org/wiki/Windows_Upgrade_3.2.0_to_4.0.0

If your going from a previous 4.0 to a new 4.0 then following above instructions (with some path modifications to step 3) should work just fine.

-brady

bradymiller wrote on Wednesday, March 23, 2011:

Also,
If you can learn git, then managing your customizations (to avoid needing to manually enter them whenever you upgrade your code) should be much easier.
-brady