blankev wrote on Tuesday, August 20, 2013:
What seems to be confusing is just a matter of wording. OpenEMR is called OpenEMR, this said you might understand the wording of Moving, Delete and my preference for Copy and Rename.
Step 1. Rename the old OpenEMR folder/map, make it OpenEMRV11118 (Version 4.1.1 with 18th patch, or give it the date you Rename your working version20130820). For Windows Upper case characters and Lower case characters is the same. For Linux you have to use exact the same characters for the Map name or Linux won’t see what you tried to type. Linux sees the difference between Upper and Lower case)
For the Software-structure of OpenEMR this is the same as moving and deleting but for your safety the working version of OpenEMR can be renamed back again and is still working. (If needed you can open the old version and use the new directory-name that is changed from OpenEMR into http://localhost/OpenEMRV41118).
Now import the new version of OpenEMR. Place this version in the root directory, the Directory where you find the map with Version 4.1.1 that used to be named openemr comes up with the name OpenEMRV4.1.2 after extracting. The new map is in the same place has the name OpenEMRV4.1.2 to get it working you have to Rename this folder into openemr.
What I do is FOLLOW the advise for Version upgrading with Copy <=> Paste. (Using this method of working you only have to correct the name of the map before pasting. Copy …/localhost/openemrv11118/sites/default/… into Paste …/localhost/openemr/sites/default…
(This works for Local personal computer settings and also for Linux Website Servers)
Be sure to change the “0” (Zero) in the steps mentioned into “1” without this step it won’t work. If you do it to late you can’t get OpenEMR to work without a reinstall. (Redo all steps following the instructions “UPGRADE VERSION” again will cover any mistakes.)
Now follow the steps indicating the latest upgrade …sql-file. Upgrade from Version 4.1.1 to Version 4.1.2 (This is for Version update not for Patch updates)
This did do the trick for me … almost… I had some tables that were not complete, for example I could not work in my local version with LBV-Forms as in the Demo Version. But by careful comparison of the Tables, there was a difference of one field missing. (Comparison can be done with two open PhPMyAdmin open. One for LocalVersion one for DemoVersion) Added the field in local version and the V4.2.1 is working flow-less.
Hope this Copy <=> Paste solution solves your upgrade problems, as it did for me. Once the New version is working, you can if needed delete the old renamed version. I do this after two month working without problems and the first few new patches have taken place. Every new version has it Patches due to problems encountered. This even while many testers did their work and added corrections before publication of the new version. (The first correction will follow within a week is my guess, the date in Vitals is not working as should and this is going to be corrected)
(I did this review and explanation to re-define the steps. I also had my trial and error following the official steps with Move and Delete and had to do my re-installs many times to get thing working. I started somewhere back with V3.1 and that was not as nice as the few steps to take with latest upgrade. Might include these steps in the WIKI-Upgrade version instructions, if so is indicated by the Deciders)