My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 439: timestamp issues
1 person starred this issue and may be notified of changes. Back to list
Status:  Done
Owner:  ----
Closed:  Apr 2010


Sign in to add a comment
 
Reported by jprof...@gmail.com, Apr 6, 2010
Having a strange issue for the last 2 versions  I'm sending ISO8601
date/time values back to the client.  It works well, except for
times that start in the AM and end in the PM - if the start time is in the
AM and the end time is in the PM, it
will set the end time in AM instead of PM.

Screenshot attached
Sample code attached

pic1.png
87.0 KB   View   Download
index.html
17.2 KB   Download
Apr 8, 2010
#2 jprof...@gmail.com
seriously?  been trying to get an answer on this apparently very serious issue with
FullCalendar since March 26th.

This definitely isn't an issue with my code, it's with FullCalendar, so it's
affecting everyone.   I tried using timestamps, the problem persisted. I checked my
timestamp value to make sure the time actually ended in the afternoon (e.g. 12:35
PM), and it does.  So my data is correct, but FullCalendar is not parsing it correctly.  
Apr 8, 2010
Project Member #3 adamrs...@gmail.com
i will take a look at this today. sorry i haven't been able to work on fullcalendar 
very much lately (it is done solely in my free time and i am the only developer)
Apr 8, 2010
#4 jprof...@gmail.com
Thank you, I'd really appreciate it.  We're using it for our calendaring system and
its scheduled to go into test mode this Friday.  I havent had time to look into this
bug myself since I'm the only developer here so it's kind of nerve-wrecking bec it
makes me look bad for choosing FullCalendar :) 

FYI I'd love to help out with this project when I have more time in about a month or
so, if you're taking submissions.
Apr 8, 2010
Project Member #5 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Duplicate
Mergedinto: 426
Apr 8, 2010
Project Member #6 adamrs...@gmail.com
this is a problem with the timeFormat string you've provided.
it was "h:mm tt { - h:mm} tt "
it should be "h:mm tt { - h:mm tt} "
Status: Done
Mergedinto: -426
Sign in to add a comment

Powered by Google Project Hosting