So instructions make it seem easy…download the file, put in contrib\snomed and then install. If I don’t have the .zip file in the contrib\snomed folder it tells me that there are no installation files (which is right). When I download the .zip file and put it in the contrib\snomed folder (like it says) then it says it’s not installed and it’s blank under staged releases.
HI,
Where did you download the zip file from?
Also, did you unzip it once you placed it in the folder?
Sorry, I am just now finding this thread. I see no one has answered but I am looking for an answer too.
Also, if you click on the ? in the staging screen it will provide you with detailed instructions that include where to get the account and where to download the files etc.
Let us know if still have problems after doing above.
Hello Brady,
Well the work-around I stumbled upon is so bat-crap crazy I’m not sure it deserves to be called a “fix”.
It was apparent that the list_staged.php module was detecting a valid rxnorm/snomed file as when one was present it would change from outputting the “No files staged…” messages to outputting nothing at all (no file version message or install button). I was doing some cheesy debugging inserting echo() statements at strategic places and when I parked one after line 179 it cause the output to display correctly. Alternately, yanking the whitespace from between lines 180 and 181 had the same effect. I’d described it in messages 10-12 of the linked thread above.
I decided to see if I could still recreate the bug. Since the original post, we’ve updated to 4.1.1.9 (likely irrelevant since list_staged has had no changes) and we’ve installed Firefox 18 on all our machines and use it (only) when launching OpenEMR. I parked a valid snomed file in the appropriate /contrib folder and brought up the External Data Loads page using different browsers running under different operating systems.
Failed (the “staged releases” box contains no text or controls):
Windows Server 2003 R2 x64 & IE8 x32
Windows Server 2003 R2 x64 & IE8 x64
Windows XP & IE8 x32
Windows 7 x64 & IE9 x32
Windows 7 x64 & IE9 x64 (remote)
Success (rxnorm/snomed file versions and “install” button displayed):
All of the above OS’s & Firefox 18
So, whatever causes the HTML to get horked up and send STDOUT into oblivion only exhibits itself under IE.
It’s very odd, as I mentioned in the other thread adding an echo(“x”) statement after line 179 fixes it, adding an echo(" x") does not. And as I said above, crunching the whitespace between lines 180 and 181 also “fixes” it.