A trio of related fixes worth surfacing because the bug was nearly invisible to the dev team (developing near UTC) but consistently wrong for the hosts who use PixVenu the most — North America, plus anywhere in the western hemisphere.
The shared root: event_date and publishedAt are calendar dates — they live as yyyy-mm-dd in the database and the CMS front matter. But the rendering code was treating them as UTC-midnight timestamps, then formatting them in the viewer's local timezone. In US Central (UTC-6), a 2026-05-24 calendar date rendered as "May 23, 2026 6:00 PM" — and format(d, 'MMMM d, yyyy') rounded that to May 23, one day earlier than the host had typed.
Where it bit:
- /changelog and /blog — entries published "today" appeared a day in the past.
- /g/recent — guest-visible event dates on recently visited galleries shifted backward.
- Home dashboard "Next event in N days" tile — silently filtered out today's event because the past-events guard compared UTC-midnight (the event) to local-midnight (today). A host opening the dashboard the morning of their event saw no countdown.
All three now extract the UTC year/month/day parts and recompose them as a local-midnight Date before rendering, or compare yyyy-mm-dd strings directly. The rendered date matches the host's input character-for-character regardless of viewer timezone.
If you ever opened the dashboard the day of your event and wondered where the countdown went — that was this. It's back now.
