Incorrect display of invalid/unset last_login dates
Summary
When „0000-00-00 00:00:00“ is stored for last_login in the database, the value „30.11.2“ is shown at the members list and „30.11.-0001“ on the profile page.
And even worse: When last_login is NULL, the current date is displayed as last activity always, despite the user obviously has logged in never.
Steps to reproduce
First case with last_loggin=„0000-00-00 00:00:00“: With orga rights look for example at district Baden-Württemberg, go to the member list and change the sort order to last activity. In Webkit/Chrome you will see users with „30.11.2“ displayed in the column last activity, in Firefox it says „Invalid Date“. If you go to their profiles, you will see „Last activity: 30.11.-0001“ in all usual browsers.
Second case with last_login=NULL: Open https://foodsharing.de/profile/182906 and look at her last activity – looks like today everyday, but is NULL indeed.
What is the current bug behavior?
as mentioned above
What is the expected correct behavior?
some kind of „unknown“, „never“ or the registration date.
Relevant error messages and/or screenshots
Possible fixes
none yet