I've had issues before with times being off for a day or so but that's usually been a problem with timezones. Now my dates are off for more than a week.

I have a Date of Birth date popup as a user field. I am displaying it as Time Ago with granularity set to 1 so it shows only the full years.

Currently for example a user has a DOB of 2/2/1982 so is in reality 30 years old. However it displays the person as 31 years old. I changed the dates and going as far as 4/2/1982 (I'm using dd/mm/yyyy btw.) it displays 31 years but 5/2/1982 and later it shows correctly as 30 years.

I'm a bit lost in trying to figure out where the problem lies. Could someone test this so we at least know if it's a general bug or just something strange on my setup? Thanks!

Comments

-Mania-’s picture

-Mania- CreditAttribution: -Mania- commented

Problem continues. Am I really the only one experiencing this?

jos_s’s picture

jos_s CreditAttribution: jos_s commented
Issue summary: View changes

I have seen behaviour also, and I am almost certain that this is because "time ago" doesn't take account of leap years.

If I know where to look, I might try to solve this. Where is the code that calculates and/or formats the "time ago"?

jpvosmeer’s picture

jpvosmeer CreditAttribution: jpvosmeer commented

We're also experiencing the same problem. As jos_s mentioned this looks like a leap year problem. Is there any progress according this issue?

Ronino’s picture

Ronino CreditAttribution: Ronino commented
Version: 7.x-2.6 » 7.x-2.x-dev
Status: Active » Needs review

#2875478-7: Leap year error should fix this.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Status: Needs review » Closed (duplicate)
Parent issue: » #2875478: Leap year error

Let's continue in #2875478: Leap year error.