Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.So, if one event ends at 11am, and another starts at 11am, they are shown as conflicting.
Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.So, if one event ends at 11am, and another starts at 11am, they are shown as conflicting.
Comments
Comment #1
hunmonk commentedi'd say that is technically a conflict
Comment #2
boris mann commentedIf I sign up for one session after another, each starting when the next begins, every single one will show as a conflict. In *actually* scheduling something, these are not conflicts.
Do I have to change all my events to have a 5 minute gap just to work around "technicalities" in signup code?
Comment #3
hunmonk commentedit's not a technicality. i could easily change it to avoid this issue. at this moment i still feel that if you have something ending at the exact same time something else starts, then that's a conflict. it seems appropriate to me to have some kind of a gap between the end and the start--after all, we don't live in a world of teleportation... :)
i'm still undecided if i want to change the current setup.
Comment #4
boris mann commentedThis is typically how things are scheduled in the real world. See http://2006.northernvoice.ca/speakers for more examples.
Make it a check box if you want to enable "strict" conflict scheduling or something. It currently makes conflict checking useless for real world scheduling slots.
Comment #5
hunmonk commented'useless' seems a bit overstated to me... :)
after further thought, i now agree that this approach hinders practical scheduling. fixed in 4.6 and HEAD.
Comment #6
(not verified) commented