Closed (outdated)
Project:
Event
Version:
5.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Aug 2007 at 22:07 UTC
Updated:
13 Apr 2018 at 21:01 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
bluecobalt commentedI just realized that I don't even have the Event All Day module activated. This is happening on the Event module.
Comment #2
gerhard killesreiter commentedDid you mark the event as being "all day"? What is the DB entry for that evnt in the event table?
Comment #3
bluecobalt commentedHi Gerhard,
No I do not have these events marked "all day". As I said in the previous post, I don't even have the Event All Day module activated.
Here is one of the calendars if you would like to see - http://www.capitolhillarts.com/chac/event/2007/09/07/month
Events that go past midnight are showing as "all day" instead of showing the start and end times.
This is happening on every site where I am using event 5.x-2.x-dev.
Comment #4
michelleThe all day module isn't used anymore. There's a checkbox on there for use times now. Make sure that's checked if you don't want it to be all day.
Michelle
Comment #5
bluecobalt commentedHey Michelle,
Thanks. With all the changes to the events module, I'm having a hard time keeping it all straight.
Do you mean the "Event has time" checkbox that appears in the edit form for the event? It says "Is time important for this event? Uncheck if event takes all day." next to it.
That checkbox is checked for these events, and each of these events has "1" in the has_time and has_end_date fields in the database, but they are still showing as "all day" in the calendar.
Again, this is only happening for events that go past midnight.
thanks,
blue
Comment #6
vhle commentedJust a "me too" post...
I'm experiencing the same problem as "bluecobalt", where start and end times are not displaying on the calendar for multi-day events.
This is with the latest snapshot of event 5.x-2.x-dev (released Jan 6, 2008)
For an example, please go to http://rrcv-dev.digiflex-solutions.com/event, and have a look at the event titled "Portland Dune Buggy" that goes from 9am 26 Jan to 3pm 28 Jan (http://rrcv-dev.digiflex-solutions.com/node/310)
Expected Behaviour: the calendar view (http://rrcv-dev.digiflex-solutions.com/event) should display "Start: 9:00" for Sat, "all day" for Sun and "End: 15:00 " for Mon.
Actual Behaviour: the calendar view displays "all day" for Sat, Sun and Mon.
Comment #7
vhle commentedSetting status to active - please let me know if there is any other info I can provide!
Comment #8
gthing commentedAny progress on this issue? The latest dev build is not showing any changes... Do we at least know where it is coming from? It seems like it would be a simple fix because the old events module (1.0) didn't have this behavior IIRC.
Comment #9
gthing commentedComment #10
gthing commentedHow can we get some attention to this issue?
Comment #11
vhle commentedI've retested this with the latest snapshot of 5.x-2.x-dev (dated 2008-Dec-01), and can confirm that this issue is still present.
Please let me know if there is any additional info that I can provide...
Comment #12
graper commentedstill having this problem. seems that if I want to start an event at 9pm and end at 1am the next day it wants to mark it on the calendar on both days and as being "all day"
While I understand that this is a math thing, I would think it would be safe to assume that the event needs to show on the day it is started. Unfortunately that means if someone wanted to start something at 11pm and go til 10am, it'll show on the day that it started. Not sure what how to resolve something like that other then a work around of putting in 2 events, 1st to last from 11pm to midnight and then another from midnight to whenever.
granville
Comment #13
graper commentedI figured it out
event module
line 1014 and 1024 are using single equal signs and need to be doubled to compare rather then assign. This change will show the event with the start time on the starting day, and again with the end time on the end day
sorry, I'm not good enough to provide a patch file.
granville
Comment #14
hutch commentedHere is a patch to fix this, please test folks!
Comment #15
frank ralf commentedComment #16
gthing commentedI can confirm that this change did the trick! Thanks so much graper and hutch!
This one has been bothering me for quite a while now. Nice to have it wrapped up.
I recommend implementing the change in core immediately.
Comment #17
graper commentedComment #18
japerryEvent for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.