You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But I see what's happening, 10 years ago wasn't a leap year, so the error is valid. But also the max and min dates are set during startup and not dynamically which in this case is alright, but not very clean
But I see what's happening, 10 years ago wasn't a leap year, so the error is valid. But also the max and min dates are set during startup and not dynamically which in this case is alright, but not very clean
Wouldn't that make it increasingly harder each year to set a date of birth? (Of course, only if you'd never stop the server, which isn't very likely).
This is an issue found with the docker image, however this bug seems to originate from the code.
Steps to Reproduce
Expected results:
Wger server starts normally
Actual results:
Wger server could not start due to incorrect date constraint in Date of Birth field.
Logs
Copied from Dozzle, please excuse the timestamps.
The text was updated successfully, but these errors were encountered: