Another bug (I think) I've found: (I find this tool very useful, and I was going to develop a very similar one, that's why I'm getting interested on debugging it).

The module should check that the end date of the reservation is posterior to the start one, and if you enter a wrong end time, ask you to change it.

Now, the module saves the reservation with the same end date that the start one, but without warning the user. Another aproach could be asking the user if he wants to accept the correction, setting the end date to be the same that the start one, but I find more intuitive the first case.

Greetings.

Comments

deviantintegral’s picture

deviantintegral commented

I'd been under the impression that event.module would handle this, but apparently not. If you enter an end date which occurs before the start date, it silently sets the end date to the same time as the start date. You should probably search/file a bug with the event issue queue.

--Andrew

deviantintegral’s picture

deviantintegral commented
Status: Active » Closed (won't fix)
zetxek’s picture

zetxek commented

Yeah, I made some testing with the module and resource conflict is not the one that silently changes the end date, it just takes the date that is passed from event. Thanks for taking a look anyway.