Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[SkGe]

As of now we have two dates, one for first rated and second one for the last rated. The logic of these two is to determine when was the first date and last date. If I rate a track for the first time, the date is populated in both of those fields. Is this the behaviour behind these two, or is something else?
If the [date first rated] is populated means it was first rated, not last.
Because if I rate the track again, the date it will change only on [date last rated].

[BryanC]

As of now we have two dates, one for first rated and second one for the last rated. The logic of these two is to determine when was the first date and last date. If I rate a track for the first time, the date is populated in both of those fields. Is this the behaviour behind these two, or is something else?
If the [date first rated] is populated means it was first rated, not last.
Because if I rate the track again, the date it will change only on [date last rated].

I requested these fields years ago so I'll explain: the Date First Rated tag is set the first time that you rate a track. The Date Last Rated is set the last time that you rated a track. So the first time you rate a track it will set both fields, and then subsequent ratings only update Date Last Rated.

It's working as intended and properly reflects the naming of both fields.

[SkGe]

Thanks for explanation. (my brain was in a loop and don't want to accept this logic )

[lepa]

i will tell you the first time and last time that the first time is also the last time at the first time