Issue 71: UNIX timestamp's not working
Status:  Released
Owner: ----
Closed:  Aug 2013
Reported by kyle.mcn...@gmail.com, Jul 30, 2009
What steps will reproduce the problem?
1. json_events.php is returning this: (after I hooked it to mysql)
Array
(
    [0] => Array
        (
            [id] => 3
            [title] => Test 1
            [start] => 1247202000
            [className] => test
            [url] => This is a test
        )

    [1] => Array
        (
            [id] => 4
            [title] => Test 2
            [start] => 2009-07-10
            [className] => test2
            [url] => This is hopefully a multiday
        )

)

What is the expected output? What do you see instead?
I expect both of them to show up on July 10, 2009. Instead only the second
one (with the yyyy-mm-dd) is working

What version of the product are you using? On what operating system?
1.2.1 / xp (apache 2.2 w/ php 5.3 & mysql 5.1.3)
Jul 31, 2009
#1 Max.Kama...@gmail.com
Because you need not take unixtimestamp in seconds, and microsecond. 

Ie normal unixtimestamp () * 1000.

// WRONG string =  [start] => 2009-07-10

Jul 31, 2009
#2 kyle.mcn...@gmail.com
i don't understand. 

in the first array, start is 1247202000 which is the unix timestamp for july 10,
2009, but it is not displaying on my calendar. however, when i use 2009-07-10
(instead of the unix timestamp) it displays properly.
Jul 31, 2009
Project Member #3 adamrs...@gmail.com
kyle, this is a bug in fullcalendar. it thinks your date is in ISO8601 format and 
parses it accordingly (year 1247). will fix in the next release.

however, there is a workaround. ensure the timestamp being returned from your script is 
a number, NOT a string. in PHP, run it through intval() before you pass it to 
json_encode()
Status: Accepted
Sep 21, 2009
Project Member #4 adamrs...@gmail.com
1.3 has this issue fixed. if your start/end is a unix timestamp, whether string or
int, it will get parsed correctly.
Status: Fixed
Aug 13, 2013
Project Member #5 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Implemented
Aug 13, 2013
Project Member #6 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Released