By: Peter
Date: 2015-10-20
Time: 10:21
|
BUG? Time formatted incorrectlyIt seems the form date parsing is incorrect. What can i do to correct this?
TBS: [row.Zeit] => [row.Zeit;frm='dd.mm.yyyy'] TEST: 1424905200 => 26.02.2015 RIGHT TEST: 1420412400 => 20.10.2400 WRONG TEST: 1416524400 => 20.10.4400 WRONG |
||
By: Peter
Date: 2015-10-20
Time: 10:53
|
Re: BUG? Time formatted incorrectlyi got it working, but don't know if its a safe fix:
|
||
By: Sheepy
Date: 2015-10-22
Time: 07:29
|
Re: BUG? Time formatted incorrectlyCannot reproduce:
Result:
|
||
By: Peter
Date: 2015-10-22
Time: 09:51
|
Re: BUG? Time formatted incorrectlyIts on only when the timestamp is a string
|
||
By: Sheepy
Date: 2015-10-23
Time: 08:39
|
Re: BUG? Time formatted incorrectlyAh, I see. A better fix may be to move up the negated is_numeric check at line 3442?
|
||
By: Peter
Date: 2015-10-26
Time: 08:27
|
Re: BUG? Time formatted incorrectlyI don't know. Better would be an check if the string/int is already an timestamp. It could be, that sometime writes this as date 20141121 => 21.11.2014
http://stackoverflow.com/questions/2524680/check-whether-the-string-is-a-unix-timestamp Something like this:
|
||
By: Skrol29
Date: 2015-10-28
Time: 11:33
|
Re: BUG? Time formatted incorrectlyThe problem is a value such as 20141121 can be a formated date as well as a timestamp.
So TBS looks at the type of the value to make a choice. |
||
By: Peter
Date: 2015-11-03
Time: 09:39
|
Re: BUG? Time formatted incorrectlyHow was it solved before? It seem one of the last version introduced this, because i upgraded the lib and dates got wrong.
|