Thomas Hochstein 697e3306ff Catch wrong last_modified dates. (#95) ... My database has some last_modified entries just containing the year (2004, as it is) or "0", leading to wrong "last modified" dates in January, 1970 (2004) or displaying the current date and time for "last modified". A simple check can catch those wrong entries, as there can't be any valid modification dates before 1990 (not even after an import from some older blog software). Signed-off-by: Thomas Hochstein <thh@inter.net>		2019-06-09 16:28:05 +02:00
..
UTF-8	Add/enhance German translation.	2019-06-09 13:49:29 +02:00
ChangeLog	Add/enhance German translation.	2019-06-09 13:49:29 +02:00
lang_bg.inc.php	also remove $Revision$	2013-08-12 10:27:53 +02:00
lang_cs.inc.php	czech translations - removed leading slash from first line (introduced erroneously in previous commit)	2013-12-28 21:43:44 +01:00
lang_cz.inc.php	czech translations - removed leading slash from first line (introduced erroneously in previous commit)	2013-12-28 21:43:44 +01:00
lang_de.inc.php	Add/enhance German translation.	2019-06-09 13:49:29 +02:00
lang_en.inc.php	also remove $Revision$	2013-08-12 10:27:53 +02:00
lang_ja.inc.php	also remove $Revision$	2013-08-12 10:27:53 +02:00
serendipity_event_entrylastmodified.php	Catch wrong last_modified dates. (#95)	2019-06-09 16:28:05 +02:00