Now that it’s officially released I recommend that we put anything we find that is a ‘bug’ in the Tracker with “3.0.1” as the first thing on the subject line (unless one of the admins wants to add Release 3.0.1 to the Group selection).
That way we can separate Bugs that need to be fixed, qa’ed and released as patches from Enhancements and development experiments.
What do you think? It’s a decent tool, better that the forum for tracking this kind of stuff.
You are correct. The version on the production release 3.0.1 should be 3.0.1 (it’s a bug, should not be 3.0.0.1 which is what we use for development version).
We’ve been following it seems below:
3 = Supreme release
0 = Major release
1 = Minor release
1 = Development release
Looking at globals.php. there appears to be a typo?
[code]
//Version tags
$v_major = ‘3’;
$v_minor = ‘0’;
$v_patch = ‘1’;
$tag = ‘.1’; // minor revision number, should be empty for production releases
// This name appears on the login page and in the title bar of most windows.
// It’s nice to customize this to be the name of your clinic.
$openemr_name = ‘OpenEMR’;
$openemr_version = "$v_major.$v_minor.$v_patch".$tag; // Version tag used by program (line 179)
[/code]
Shouldn’t the double quote “.$tag by after the .$tag” ?
I don’t know that much but it seems wrong to me.
I got this to work in windows by commenting out line 173:
//$tag = ‘.1’; // minor revision number, should be empty for production releases
The coding is ugly, but it’s not a bug. The bug was we just forgot to change the version before packaging it up as a release. We usually just make $tag variable empty, no need to comment out.
It’s ok to change it in your xampp version since user is aware this is not original release with some modifications.
But, we definitely should not change anything in the openemr-3.0.1.zip release, since this is being downloaded with the tar.gz file as the official 3.0.1 release. I’d suggest making a openemr-3.0.1.zip release with no mods to place in sourceforge (download the tar.gz file, extract it, then make the zip); then everybody will be downloading the “official” release. I hope this makes sense.
Just a thought from a moron - if there are two files which are supposedly the same, inevitably one will get overlooked, at which point they won’t be.
Given that 7zip is free and can untar to a zip, would we not be FAR better to put a link and instruction to download 7zip for Windows users to make it easier on the programming community?
I know I am a great proponent of making things as simple as possible for the end user. But I am also a quality guy. Just a thought.
If the only difference between the tarball and the “Windows version” is the zip file format, then it’s not really a Windows version. As long as we have it why not really make the Windows version a Windows version by providing a proper path in the globals.php file? It wouldn’t take that much effort to do it, and it’s not like a Linux path will do a Windows user any good.
My testing suggests that the view will change with a globals.php change in the code (0-2) and a logout-login. Any reason we couldn’t put that preference for view on the login screen? That would allow “preferences” to work for all users, rather than limited to the preference of the “wizard of release”
