I recently noticed that when booking a conflicting event using resource conflict, the times displayed in the error message are incorrect...it seems as if they're not using the correct timezone information or something. (see screenshot attached, please)

My time settings are:
Date Field: Type = datetime, Timezone Handling = no timezone conversion
Global: Timezone = America/Los_Angeles, User configurable timezones = Disabled

These seem consistent to me and are displaying proper times across the site, except for in the error message for resoruce conflict. Is this a bug where Resource Conflict doesn't deal with timezones properly? If not, any advice?

CommentFileSizeAuthor
conflict-date-wrong.jpg68.53 KBRob_Feature

Comments

perlgal’s picture

perlgal commented

I got the same problem. Any clue?

Renee S’s picture

Renee S commented

I get this on recurring events - the error message shows the first recurring event as the conflict, even if it is (say) the 5th event that's conflicting.

shanefjordan’s picture

shanefjordan commented

I am running into this same issue still. The timezone is working, however it is not working with Daylight Savings Time (DST).

Times display every where else without an issue, but the error message will show the time off by 1 hour (both start and end).

This has to be something with the format_date in the resource_conflict_display_conflict_errors. Since this module requires the DateAPI module, it seems as though functions from the Date module should be able to correct this.

Does anyone else have any ideas?

Thank you,
Shane

ohthehugemanatee’s picture

ohthehugemanatee commented

Please clarify what I need to do to duplicate the problem on a clean install. It seems like there are two issues being discussed here: one with event repeats, and one with date/timezones.

It would make sense for the dates in error messages to be off - the module converts everything to GMT for the comparison. Probably not a great idea. The simple solution is just to remove dates/times from the error message so this isn't visible. :)

wusel’s picture

wusel commented

But I think, the title, date and time of both events should be shown in the error-message. Then the editor of the new event knows, witch events are in confict.

shanefjordan’s picture

shanefjordan commented

I installed the Daylight Savings Time module and this fixed the issue for me. Now, the error messages are displaying the proper date/time.

imclean’s picture

imclean commented

Possible steps to reproduce;

- Enable Date, DST and Resource Conflict modules
- Set the site's timezone to anything except UTC (Australia/Hobart in our case)
- Create a Date field with "No time zone conversion"

Taking into account DST, we're currently 11 hours ahead of UTC/GMT.

To test, I created a booking from 7:30am to 9:30am then tried to create an all-day booking for the same day.

The error message indicates the conflict is 11 hours later than it actually is: 6:30pm until 8:30pm.

The comparison appears to be correct, it's just the error message which is confusing.

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Issue summary: View changes
Status: Active » Closed (outdated)

Closing this due to D6 being EOL and to clean-up the queue. Please feel free to let me know if you think it is relevant to D7 and I'll re-open.