It is very difficult to make events all day in the events modal (and 00:00 is confusing)

When using Discourse Calendar (and Event), I find it unnecessarily difficult to schedule all day events using the modal:

image

Basically, there is no obvious all-day option - a time must be selected. Making matters worse, when it is set to a day or more after the start time, the end time defaults to 00:00, which is quite annoying (it defaults to 1hr after the beginning time if the same day).

I do note that when 00:00 is selected, the following occurs:

  1. in the UI, it is represented as an all day event (i.e. not as midnight)
    [event start="2026-01-21 00:00" status="public" timezone="Pacific/Auckland" end="2026-01-22 00:00"] [/event] gives:

  2. in the timezone times it is displayed as midnight on that day - which is actually 24hrs after when it should be if taken literally

  3. if the time is deleted in the markdown, it behaves the same way

It would be great to have this all a bit clearer for the non-expert users, but I accept that there might be limitations baked into how the dates are stored.

As an alternative, would it be possible to add an “All day event” option to the modal, which when ticked hides the times?

Then we could use 00:00 to actually mean the literal time that it should (i.e. 1 minute before 00:01 on the specified day, not 1 minute after 23:59 on the specified day) - as it does with the Insert Date/Time functionality.

2 Likes

hmmm, speaking for myself only - I don’t really find the workflow that difficult for multiple day events, i just select the first date, the click the dropdown for time and hit the 0 key and 00:00 pops up and i select it. then i just select the second date in the calendar and it defaults to 00:00 and i move on to the next required fields


which gives this:

I agree that it could be clearer when one clicks on the dates and shouldn’t show the times tho. :thinking:

i would expect the date fields in the event modal to behave similar as the insert date function in the composer, but it doesn’t really.

also the inconsistency of events calendar week starting with Sunday and the insert date function calendar week starting on Monday is annoying.

1 Like

Yeah, that flow works quite nicely now that I know it - and understand what 00:00 means / does.

The problem is that this is overlaying a whole heap of meaning on 00:00 which is not obvious or clear to new users. Basically, it needs refinement - or at least ‘just in time’ information.

Yes, agree - these really need to work exactly the same.

1 Like