After upgrading to 5.13.0 we notice that the time and date format has changed from "2025-04-26 13:00:00" to "May 7, 2025, 1:36 p.m." Is this a deliberate change in NAV or a result of a change in a library?
Most important: How can we get the old format back?
--Ingeborg
On Wed 07 May 2025 at 14:27, Ingeborg Hellemo via Nav-users nav-users@lister.sikt.no wrote:
After upgrading to 5.13.0 we notice that the time and date format has changed from "2025-04-26 13:00:00" to "May 7, 2025, 1:36 p.m." Is this a deliberate change in NAV or a result of a change in a library?
Time format where?
On Wed 07 May 2025 at 14:27, Ingeborg Hellemo via Nav-users nav-users@lister.sikt.no wrote:
After upgrading to 5.13.0 we notice that the time and date format has changed from "2025-04-26 13:00:00" to "May 7, 2025, 1:36 p.m." Is this a deliberate change in NAV or a result of a change in a library?
Time format where?
-- Sincerely, Morten Brekkevold
Everywhere a time stamp i shown. Examples:
/ipdevinfo "First discovered", "End time" of Jobs
Timestamp in SMS/email: ...is down since May 7, 2025, 11:19 p.m..
--Ingeborg
On Thu 08 May 2025 at 11:07, Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
Everywhere a time stamp i shown. Examples:
/ipdevinfo "First discovered", "End time" of Jobs
Timestamp in SMS/email: ...is down since May 7, 2025, 11:19 p.m..
We're thinking this may be something we missed in the upgrade to Django 4.2 in NAV 5.13 (nothing really changed in NAV here, but we may have missed something that changed in a newer version of Django).
We did solve a bug that may be related to this, where the NAV front-end code expected timestamps in a specific format from the back-end, and the timestamps apparently changed format without NAV code changing at all: https://github.com/Uninett/nav/issues/3329
My suggestion is to make a new bug report and reference 3329.
-
Ingeborg Hellemo -
Morten Brekkevold