There a few new features, including import/export, shorthand billing code entry (thanks Mike and Alfonso), billing code lookup via search, and now clone and search functions use AJAX. See the help file (linked from the form) for some explanation of new features. Please report bugs in this thread. Thanks for testing!
would you be so kind as to give some directions on how to install/upload the new CAMOS files. Or is there in the tar/zip file a readme or help with relevant information that I canuse before making a mess of the alreasdy used CAMOS installation of a earlier release?
For all testers, this is what I found in an old "help forum" suggestion:
=====================================
Brady,
That would be great if we could get a second chance. What is in cvs now would be adequate for the release. With a day or two, I might straighten out a few other minor issues.
As far as cleaning up a bad install, just get the good files and start over. If the form is already installed from a previous version, don’t try to re-install in the admin section. Just copy the new files into the forms/CAMOS/ directory. The database structure has not changed.
few issues:
I used a test box Fedora 9:
First I replaced the old CAMOS folder with the new release–>, I got SQL duplicate error for forms_camos_subcategory table.
OK.
I cleaned up all CAMOS tables and then run new form installation,–> I got a blank white screen…
I assume there is an php error with missing semocolon or closing bracket of the index file (view.php?) .
I am not sure why you would get the SQL duplicate error. The tables form_CAMOS_category, form_CAMOS_subcategory and form_CAMOS_item have an auto-incrementing key (id), so this should not happen.
Did you get the files from my website, cvs or the 3.0.0 release?
Did you first try copying the files over without making any changes to the database?
hmmm…
Maybe if you had the form open at the moment you upgraded. That could possibly cause such an error.
I will try a fresh install again and see what happens.
Did you download the CAMOS files from CVS or Mark’s web site? The file permissions for new.php and content_parser.php downloaded from Mark’s web site differ from those downloaded from CVS. I experienced a white screen after I loaded the latest CAMOS files from Marks’ site. I resolved this by changing permissions on both of the files. I had to set the file permissions for “others” and “group” to “can read.” I also made sure the files were set to “is executable.”
Yes, I used Mark’s website to download.
I am not sure about permissions, since such error will display permission errors…
Mike: I did not try the your changes yet.
Overall, most users will have CAMOS already installed.
The steps I did:
1-UPGRADE: simply replacing the old CAMOS folder (OPENEMR V3.0)
This upgrade failed with SQL error ( I will restet later and give feedback).
2-FRESH INSTALL: I found the registry table and deleted row CAMOS registry, then deleted all CAMOS tables.
This allowed for a new fresh installation which resulted in white screen.
On my test system ( OpenSUSE 11.1 ), I did not have any permissions errors displayed, just a white screen. I only realized there was a difference in permissions when I compared the files that were not working with the ones that worked. Once I changed the permissions on Marks’ new files - everything worked.
My method of installation is:
1. Install latest version of OpenEMR via set up script.
2. Drop OpenEMR database created by set up script.
3. Import my production OpenEMR database ( CAMOS already installed).
4. Copy over latest CAMOS files.
Yes, I used Mark’s website to download.
I am not sure about permissions, since such error will display permission errors…
Mike: I did not try the your changes yet.
Overall, most users will have CAMOS already installed.
The steps I did:
1-UPGRADE: simply replacing the old CAMOS folder (OPENEMR V3.0)
This upgrade failed with SQL error ( I will restet later and give feedback).
2-FRESH INSTALL: I found the registry table and deleted row CAMOS registry, then deleted all CAMOS tables.
This allowed for a new fresh installation which resulted in white screen.