Event: upload feature image not working

[lgontard]

Updated description (June 11, 2026):
The Feature image block is not working. If you select Add media button, nothing happens

Initial report: Seeing intermittent behaviour when you select Add media button: sometimes nothing happens; other times, you can access the Media library but only see one page of image options, all directories are selected (see screengrab). When select the next arrow, get the "command" message (see screengrab). When select an image, sometimes able to upload, but sometimes not and then get the "command" message (see screenshot). Using Edge.

[lgontard]

Nothing happens when you select Add media button

[theteknocat]

@lgontard @leeomara

Root cause identified. The 500 error on the media library AJAX request on the Event form is caused by a bug in the date_recur contrib module (drupal/date_recur), not the media library itself. Here's what we found:

What happens:

The Event content type's "Event Start Time" field (field_event_start_time) had a default value configured in field config (default_date_type: now, default_time_zone: America/Whitehorse). When a default value is set, the date_recur basic widget renders a second spurious empty occurrence slot on the form. When the media library AJAX request fires to rebuild the form after selecting an image, Drupal processes that second occurrence — which has an empty timezone string — and crashes with a PHP DateInvalidTimeZoneException.

What we looked into:

This is a known limitation of the date_recur module. The basic widget has never properly supported field-level default values:

• #3040729 — Show form validation warning if default values will not end up in widget — the maintainer is aware defaults don't get applied; the proposed resolution is a validation warning, not actual support
• #3030603 — Allow partially-invalid field value defaults — the field requires all three of start date, end date, and timezone to be a valid default; partial defaults produce broken behaviour

There is no upstream fix currently in progress.

Fix:

We're removing the default value from the field config (it wasn't working as intended anyway — no dates were being pre-filled on the form). We also updated the date_recur module to the latest stable release (3.8.2) — this was attempted first based on a related issue (#3417915) that appeared to address the same crash but was subsequently closed as "Works as designed." Since the module was due for an update regardless, that work is retained in the PR even though it didn't resolve the issue on its own. A PR will be linked to this issue shortly.

[lgontard]

@theteknocat This is working in test and ready for deployment to prod.