bug: Calendar new event creation fails with "Bad request" error #110

New Issue

2026-05-11T15:05:59Z

enjin2310 commented

2026-05-11 15:05:59 +00:00

When attempting to create a new event in the calendar, the event fails to save and displays a "Bad request" error message.

Observed behavior:

User attempts to create a new event in the calendar.
After filling in the event details and clicking Save Changes, the event fails to save.
A red error banner appears at the top of the page with the message "Bad request. Please check your input."
The event is not added to the calendar.
The attached screenshot shows the error message on the calendar page.

Expected behavior:

When creating a new event with valid information, it should save successfully.
The event should appear on the calendar immediately after saving.
No error messages should appear if the input is valid.
If there is an error, a specific error message should indicate which field or input is problematic.

Impact:

Users cannot create new calendar events.
No clear indication of what input is causing the "Bad request" error.
Feature is non-functional for event creation.

Classification:

Type: bug
Area: Calendar / event creation / API
Severity: high (feature blocking)
Impact: Users cannot create calendar events; error message is vague and unhelpful

When attempting to create a new event in the calendar, the event fails to save and displays a "Bad request" error message. Observed behavior: - User attempts to create a new event in the calendar. - After filling in the event details and clicking Save Changes, the event fails to save. - A red error banner appears at the top of the page with the message "Bad request. Please check your input." - The event is not added to the calendar. - The attached screenshot shows the error message on the calendar page. Expected behavior: - When creating a new event with valid information, it should save successfully. - The event should appear on the calendar immediately after saving. - No error messages should appear if the input is valid. - If there is an error, a specific error message should indicate which field or input is problematic. Impact: - Users cannot create new calendar events. - No clear indication of what input is causing the "Bad request" error. - Feature is non-functional for event creation. Classification: - Type: bug - Area: Calendar / event creation / API - Severity: high (feature blocking) - Impact: Users cannot create calendar events; error message is vague and unhelpful

Screenshot 2026-05-11 110452.png

144 KiB

spikerj commented

2026-06-07 18:39:35 +00:00

Root cause: the event modal set end = start for all-day events, but the calendar API requires end to be strictly after start, so all-day event creation always returned 400. The vague banner was a second bug — the frontend only read the ModelState errors dictionary and dropped the controller's plain-string message.

Fix in spikerj/spikersoft-angular#4: all-day events now send a start-only event (or a strictly-later end for multi-day), and the API service surfaces the server's specific 400 reason. Regression specs added.

Closing as fixed by spikerj/spikersoft-angular#4.

Root cause: the event modal set `end = start` for all-day events, but the calendar API requires `end` to be strictly after `start`, so all-day event creation always returned 400. The vague banner was a second bug — the frontend only read the ModelState `errors` dictionary and dropped the controller's plain-string message. Fix in spikerj/spikersoft-angular#4: all-day events now send a start-only event (or a strictly-later end for multi-day), and the API service surfaces the server's specific 400 reason. Regression specs added. Closing as fixed by spikerj/spikersoft-angular#4.

spikerj closed this issue

2026-06-07 18:39:44 +00:00

spikerj referenced this issue

2026-07-03 23:13:28 +00:00

[E2E P1] Anonymous walk — every public route + primary actions #314

spikerj referenced this issue

2026-07-03 23:15:34 +00:00

[E2E P1] Anonymous walk — every public route + primary actions #314

spikerj referenced this issue

2026-07-06 03:03:33 +00:00

[Security] Remove anonymous access to Trails mutating endpoints (DELETE /{id}, DELETE /purge) #416

Sign in to join this conversation.