Timezone-Aware Date Attributes Show Local Time

A gate time entered as 7:30pm in the admin could appear as 1:30am on the public site: datetime custom attributes with a timezone were rendering the raw universal instant instead of the configured local time. Timezone-aware datetime attributes now render in their local time everywhere themes display them, so patrons see the time the editor actually set.

What editors set is what patrons see

Choosing a timezone on a datetime attribute previously looked like it worked but the selection was dropped on save. The timezone now persists with the value, public pages convert the stored instant into the configured local time, and existing records have been migrated so previously entered times display correctly too. Attributes without a timezone are untouched and behave exactly as before.

Consistent times across the admin and site

The admin's datetime attributes also expose their timezones properly when exporting, and post dates shown on collection cards now respect the site's timezone rather than the server's. Together these close the gap between the time an editor enters and the time a patron reads.