| Issue 773: | Better docs for json feed format | |
| 3 people starred this issue and may be notified of changes. | Back to list |
on page: http://arshaw.com/fullcalendar/docs/event_data/events_json_feed/ you need an example of the expected json. I started with: [{"start": "new Date( 2010, 12, 25)", "title": "1"}] then: "event" [{"start": "new Date( 2010, 12, 25)", "title": "1"}] then: "event" [ { "title": "1", "start": "2010-12-25T00:00:00" } ] and several other variations, finally gave up and searched for examples on stackoverflow.
Jan 2, 2011
Doc. said Unix time stamp is accepted, but only iso8601 date format works.
Feb 12, 2011
idbill.p...@gmail.com,
just reread your comment and the reason it was not working was b/c you had your new Date() declaration in a string. should be:
[{"start": new Date( 2010, 12, 25), "title": "1"}]
instead of
[{"start": "new Date( 2010, 12, 25)", "title": "1"}]
Feb 12, 2011
davidweilei, can you post a separate issue with an example of your code?
Aug 13, 2013
(No comment was entered for this change.)
Summary:
Better docs for json feed format
(was: better docs for json feed format)
Status: Accepted Labels: Type-Docs
Mar 18, 2015
Here is a JSBin attempting to use a unix time stamp: http://jsbin.com/buredoleqe/1/edit?js,output Unquoted, quoted, then as a ISO 1809 string (which works), using the debugging template.
Aug 21, 2015
Discussion for this issue has moved to the following URL: https://github.com/fullcalendar/fullcalendar/issues/1042 This is because Google Code is shutting down. Apologies if you are being pestered with these notifications. This is a one-time event. Happy coding, Adam
Status:
ExportedToGithub
|
|
| ► Sign in to add a comment |
Status: Misc
Labels: -Type-Defect