my most recent comment is the most up to date ======= I figured this out – if the client chooses: start date: 2/9/24 end date: 2/10/24 without a time, the back end assumes that the event has ended at 12:am on 2/10/24, rather than at the end of the day on 2/10/24. Is there a work around for this so that I don’t have to ask for an end time? These are events that last until the day’s events finish up – there’s not specific time and so it doesn’t make sense to ask for an end time. Maybe in the back-end, the default should be that if we don’t ask for times, assume it’s an all day event. When users pick times, then the start and end should assume the activities are within that time frame. == We have series events that take place on multiple weekends, and would like to tag the event preview card and single post page with an “in progress” message. It is working with events that occur only once. I built out a text page to pull all of the date values – see attached. Cache Cattle is an event with more than one weekend, Ashcraft Ranch takes place only once. BOTH events are taking place this weekend. If you look at the fields, the one time event retains the values in the upcoming fields on the dates of the event. When the event has more than one date, the upcoming dates are being moved to previous when the event starts. This loses the happening now tag, so the happening now trigger is lost for the front end visibility rules.