Open epixian opened 4 years ago
@epixian, I've noticed the same thing with all day start_datetime
being off. Personally, the workaround I use is calculate the 00:00:00 of the event date with EST timezone and they will count it as an all day event. For the end_datetime
, 11:55pm is the time used to calculate an all-day event according to the events I've created inside of the platform. I hope this works for you as it has for me!
What is the current behavior? https://app.breezechms.com/api#add_event Adding an event with
all_day=1
sets"start_datetime":"1969-12-31 19:00:00"
regardless of Unix timestamp entered and setsend_datetime
to the current day at 23:55:00.If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via Using Postman, submit a POST request:
Without
all_day=1
: https://yoursubdomain.breezechms.com/api/events/add?name=Bonfire&starts_on=1467161100With
all_day=1
: https://yoursubdomain.breezechms.com/api/events/add?name=Bonfire&starts_on=1467161100&all_day=1What is the expected behavior? From the documentation:
What is the motivation / use case for changing the behavior? Returns incorrect values for
start_datetime
andend_datetime
Please tell us about your environment: Postman API