ToonArmy wrote:"As opposed to fixing this I sort of caused it by allowing birthdays in the same year r8807 for the reason I gave earlier. Adding a check would require language changes and such forth for a trivial thing in a trivial feature I really do not see the point."
I say since you broke it you fix it.
Sorry sparky but the birthday field is the user birthday field, not a general multipurpose date field. As such it should have a reasonable lower and upper limit as should all data entry fields. If anybody wants to re-purpose the BD field to track other dates that is their problem and exactly what custom profile fields are designed to allow. Just because someone wants to use something the wrong way does not mean you should accommodate them with bad design. The fact that you provided the birthday field in the first place presumes that you think there are users who want to utilize that data, therefore you have an obligation to implement it in such a way that prevents unreasonable data from being entered. While it is true that you cannot enforce the correct data be entered, if I wanted to shave 10 years off my age I could, but I should not be allowed to set parameters outside the natural human lifespan.
Of course the best solution would be to remove all system profile fields and allow them to be custom profile fields with the lower and upper thresholds definable by the board admin.