| Issue 2079: | V2 - Problem with long event | |
| 4 people starred this issue and may be notified of changes. | Back to list |
You can see the fiddle here : http://jsfiddle.net/mediaslide/949Xy/5/ Long Event 2 : Appear one the calendar on 3days. Long event 3 : Appear only on two. But look at the dates both are : start: '2014-01-07', end: '2014-01-09' So both should be showing on the 3 days. The difference is the time Long event 3 has a end time until 9am. So all the end time until 9 am will not shown on the last day. On this page (http://arshaw.com/fullcalendar/docs2/timezone/timezone/) i can see that on timezone "defaut" the timezone offset will always be +09:00 so that can be a clue to resolve it. I've tried changing the timezone to UTC or specify one, but the problem is still here, everytime you specify a end time before 9.00am it will not shown on the last day. Thank you for your help.
Jan 29, 2014
#1
manuw...@gmail.com
Jan 29, 2014
Thanks for the report. This is actually because of some new behavior: https://code.google.com/p/fullcalendar/issues/detail?id=1049 Basically, if an event spans into another day, but it is before 9am (the default), it won't appear to be on that day. Docs for this setting: http://arshaw.com/fullcalendar/docs2/event_rendering/nextDayThreshold/ So, you can set it to `00:00` and it will restore the old behavior. Please let me know if you disagree with the setting/default-value in the first place. Would love to hear feedback.
Status:
Discussing
Labels: milestone-date
Jan 29, 2014
Ok thank you i've changed it to "00:00:00" and it's perfect now. Ok i've read the issue, and i think "00:00:00" would be a better default option, as 1am it's a new day when you're using date in the database, and you changed all timestamp to date. But keeping the option to change it is a good feature. Thanks again for this new version, we have many client worldwide and timezone was a headache (event were not showing depending of the zone), we use UTC on our server and database, so now it's perfect.
Jan 29, 2014
I don't know if i need to start a new issue for it, but previous version 1.6 was better about on think : When you refresh the calendar, no blink glitter appeared and the new elements were added smoothly. Now with v2 all the elements of the calendar disappeared and the all the elements are re-loaded again. It's very quick with few elements but not very user friendly with hundreds of element. Let me know if it will be change for final release :) Emmanuel
Jan 30, 2014
I've changed refetchEvents to :
function refetchEvents() { // can be called as an API method
// clearEvents();
fetchAndRenderEvents();
}
And now the events do not disappear anymore.
Why the purpose of adding clearEvents ?
Feb 2, 2014
hi @manuweb2, version 2 does not contain any changes to event rendering like that. I'm almost positive. Can you please investigate this a little further then submit as a separate issue? Please isolate the problem more and create a JSFiddle for both v1 and v2 demonstrating the difference. http://arshaw.com/fullcalendar/wiki/Report-a-Bug/ PS- the clearEvents call is very necessary
Status:
Done
Feb 3, 2014
Ok i will create a new issue, Regarding this issue event with nextDayThreshold set to 00:00 event with no time (all day) will not shown on all days... look at the jsfiddle : title: 'Long Event', start: '2014-01-07', end: '2014-01-10' It will show only until 2014-01-09 which is a bug because for exemple si someone is OUT until the 10 i want it shown until the 10 on the calendar. Manu
Feb 3, 2014
That is also a change in V2. When it comes to all-day dates, end dates are now *exclusive* http://arshaw.com/fullcalendar/wiki/Upgrading-to-2/ So you'll have to consider that and have your end actually be the day after. This is how most other libraries do it too. make sense?
Feb 3, 2014
Oki will have to dynamically add +1 day to all my event on your script. I just created an event on google calendar from 3 to 5 of february and it appear 3 to 5. When i click on detail it show start : 03 february and end 5 february (not 6)... I think this is very confusing.
Feb 3, 2014
When I say that other libraries do it exclusively, I mean under the hood in the way that they store event date. From a programming perspective. From the user perspective, yes, it is presented as an inclusive value. If you look Google Calendar's AJAX requests, or look at the iCalendar specification, you'll see that end times are in fact exclusive.
Feb 3, 2014
Ok thank you for your explanations.
Nov 28, 2014
Hi, It is possible to resize the event with a specific time.
Like this:
start: '2014-01-07T00:30:00',
end: '2014-01-09T08:30:00'
I've seen this fiddle http://jsfiddle.net/mediaslide/949Xy/9/
And I was wondering if I can resize those events with time.
Thanks.
Nov 28, 2014
@iamspauljamez18, please follow the discussion on Issue 2176
Nov 28, 2014
Alright Thanks.
Dec 20, 2014
how to reduse one day from even.end on resizing. because i want exact dates ..if i have selected 2-3 it gives me 2-4 date..
Feb 20, 2015
So if my events are allDay, there is no way to include the ending date when the event get put on the calendar. I am very confused about this. I have an event that lasts the entire day for multiple days (let's say start = 02-15-2015 and end = 02-17-2015). If the event takes place all day for the 15th, 16th, and 17th, why would the end date be excluded. It is not ending on the 18th (which would put the event object in the correct date boxes like I am trying to do), it occurs on the 17th and ends when the day is over on the 17th. Why would it be useful to have an end date for an event that nothing happens on? Is there no way at all to make an allDay event.end inclusive anymore?
Mar 5, 2015
I agree. Having an all day event I would think the event should render into the end date. So I have 2 options: I can take off the allDay: true from my events but then the event is rendered with a 12a at the beginning. So now I have to override the event render to remove the 12a. Also the users of my application do not enter times. They events they are creating are assumed to be all day. So now I need to manually add times onto the dates they have entered for this to work. Or I can manually add a day onto the events when I pull them back from my source. Then I need to be aware when I click on events and get their information I need to remove a day from the end date when I save the event back into my data source. Both see to be too hacky to be worth it in my opinion and if the behavior were to ever change in a future release my hacks could cause other issues.
Mar 17, 2015
yo, this sucks. end-dates should be inclusive |
|
| ► Sign in to add a comment |