bradymiller wrote on Monday, March 30, 2009:
Aron,
Regarding issue of upgrading your gacl from 2.9 to 3.0, check out this post (same for version 3.0.1):
https://sourceforge.net/forum/message.php?msg_id=6878373
-brady
drbowen wrote on Monday, March 30, 2009:
I am using the current development demo and it calculates the age
wrong. 10-05-1977 is coming up as 32 years old. Great little system
you have there though!
-brian
Who has been working on this section? It needs to be fixed.
Sam Bowen, MD
rabbai wrote on Monday, March 30, 2009:
I looked at the post regarding the age. I noticed that it isnt wrong, What happens is that, it calculates the age that way until that date is reached and it then updates. I doesnt look at the year of birth but looks to be sure the 3 constants in the date of birth are met.
sunsetsystems wrote on Monday, March 30, 2009:
Sorry I was out of town for a few days. I’ll make a release 3.0.1 this evening if nobody objects. This will include some contributed forms from the mi-squared folks.
drbowen wrote on Monday, March 30, 2009:
The age of a person born 10-05-1977 is 31.
Brian is getting 32.
"It doesn’t look at the year of birth but looks to be sure the 3 constants in the date of birth are met. "
Normally the system calculates the date correctly. What Brian is describing is the behavior is now incorrect?
Sam Bowen, MD
rabbai wrote on Monday, March 30, 2009:
If someone is born in 1977 and this is 2009 then the person is 32 not 31, if the date was 1978 then it would be 31. Look at it correctly.
whimmel wrote on Monday, March 30, 2009:
In the example given, the birthday was in October. The person in question is not 32 yet, but they will be later this year 
drbowen wrote on Monday, March 30, 2009:
The convention in US English usage is for the person to be "31" until they reach their birthday. The individual is reported to be "31" all the way through 10-04-1977. At 00:01 10-05-1977 they reach their birth and they are by convention "32".
The function in mysql should return "31" until date not less ( !< ) than 1977-10-05 is true.
This is the same as saying the date is greater than or equal to 1977-10-05 is true.
Sorry, I’ve been calculating birthdays in my head as a physician since 1980.
Sam Bowen, MD
rabbai wrote on Monday, March 30, 2009:
yeah u r right, just looked at it now, it should calculate it properly. Now i see d error
blankev wrote on Monday, March 30, 2009:
Dear all,
Sam is right in this, today I feel like 59 since my birthday will be 24-05-2009. After that day I will feel like old human being, 60 years of age. So it is of some significance top straighten out this problem!
It can be solved by calculating with dates, but if you need to calculate with numbers every four years the amount of days is somewhat different. So stop this insignificant discussion. Lets calculate birthday and days of existence the right way. So "I" will not be offended seeing my age as sixty when I feel like an active youthful 59-ner…
Keep up the good spirit. What is in an age???
Calculating age is one of the principal free codes for many software types, but remember the date of your system has to be right for the calculation or we need to use the International Computer Time schedule.
Sorry if I offended some these fine programmers, but I needed to show my little programming knowledge, and this is as far as it gets for now.
Pimm
bradymiller wrote on Monday, March 30, 2009:
hey
age bug previously discussed here:
http://sourceforge.net/forum/forum.php?thread_id=3132192&forum_id=202506
I think Jason posted the best fix strategy. Postponing fix until after 3.0.1 release.
-brady
orions_empire wrote on Tuesday, March 31, 2009:
Pple GREAT work, thank you for the release.
mike-h30 wrote on Thursday, April 02, 2009:
The latest release displays "OpenEMR v3.0.0.1" on the login screen.
Should it be "OpenEMR v3.0.1"?
bradymiller wrote on Thursday, April 02, 2009:
yep,
I can live with that bug though.
ideaman911 wrote on Thursday, April 02, 2009:
Guys;
Just wanted you to know that there is a problem possibly related to Windows, but might be more universal. The initial login screen is getting the following error:
ERROR: query failed: select user, date, comments from log where event like ‘login’ and comments like ‘%127.0.0.1’ order by date desc limit 1
Error: Got error 127 from storage engine
It certainly looks like it could be caused by requiring a look at 127.0.0.1 even though the browser call I used is "localhost" and not the IP equivalent.
It causes no further problem, however, as the login screen comes up and displays fine (with the error on it in red) and then after entering the correct login user and password it works fine.
One other thing - I did not notice if I had the problem when I was doing my database updates, and my process (which was intended to verify RESTORE simultaneously) was to first create new install databases, then copy my upgraded 2.9 data and gacl_ prefixed files to the …/mysql/data/openemr/ directory.
Joe Holzer Idea Man
http://www.holzerent.com
bradymiller wrote on Friday, April 03, 2009:
hey,
Turn display_errors off in your php.ini . This was recommended during installation script. If this is on, you will have strange behavior during ajax stuff (for example, acl administration). In your php.ini file, I’d probably ensure following settings:
short_open_tag = On
max_execution_time = 60
max_input_time = 90
memory_limit = 128M
display_errors = Off
log_errors = On
register_globals = Off
post_max_size = 30M
magic_quotes_gpc = On
file_uploads = On
upload_max_filesize = 30M
When copying/backing up the mysql databases, isn’t there a safer mysql function rather than directly copying them? (I don’t know, I’m just wondering)
What do you see in your openemr admin->log after click Refresh ?
-brady
cfapress wrote on Friday, April 03, 2009:
Hi Joe,
That error is coming from <oemr>/interface/login/login.php. In early February some new code was added. See this URL for the CVS comments:
http://openemr.cvs.sourceforge.net/viewvc/openemr/openemr/interface/login/login.php?view=log
Brady might have it right that you’re seeing all error and warning messages. Perhaps I’m not seeing the problem because of a PHP config setting? I’m not sure.
Jason
rachoac wrote on Saturday, April 04, 2009:
Hi guys,
I’ve successfully migrated one of our prod 2.9 instances to 3.0.1, and we’re going to be going through and testing extensively. Looking good so far!
Aron