Date/Time formatting not working

[julianstolp]

Deployment Type

Self-hosted

NetBox Version

v4.0-beta1

Python Version

3.10

Steps to Reproduce

1. Upgrade to v4.0-beta1
2. Date and Time formatting defaults to Created 03/10/2022 1 a.m. or 04/04/2024 12:50 p.m. CEST
3. Check config configuration.py

# Date/time formatting. See the following link for supported formats:
# https://docs.djangoproject.com/en/stable/ref/templates/builtins/#date
DATE_FORMAT = 'N j, Y'
SHORT_DATE_FORMAT = 'Y-m-d'
TIME_FORMAT = 'g:i a'
SHORT_TIME_FORMAT = 'H:i:s'
DATETIME_FORMAT = 'N j, Y g:i a'
SHORT_DATETIME_FORMAT = 'Y-m-d H:i'

Expected Behavior

Date and Time is formatted as defined in Config Created 2022-03-10 01:00 or 2024-04-04 13:34 CEST

Observed Behavior

Created 03/10/2022 1 a.m. or 04/04/2024 12:50 p.m. CEST are displayed also standard values defined in settings.py are not used.

[jeremystretch]

Reminder: Please don't prefix your issue title with any sort of faux tag. Just indicate the affected NetBox version and the appropriate tag(s) will be assigned during triage.

[opericgithub]

I believe you should additionally enable localization in configuration.py

ENABLE_LOCALIZATION = True

[julianstolp]

I believe you should additionally enable localization in configuration.py

ENABLE_LOCALIZATION = True

I already added this option. Does it work for you?

[jeremystretch]

From the Django 4.0 release notes:

In order to follow good practice, the default value of the USE_L10N setting is changed from False to True.

Moreover USE_L10N is deprecated as of this release. Starting with Django 5.0, by default, any date or number displayed by Django will be localized.

This was on our radar back when we moved to Django 4.0, but fell off more recently. As Django now effectively mandates the localization of dates and times, the configurable formats will be used only when the user's locale cannot be determined (AFAICT).

We should at least remove the USE_L10N ("use localization") variable from settings.py, but beyond that I'm not sure there's any other action to take.

[opericgithub]

I already added this option. Does it work for you?

It works in 3.7.
Currently I'm unable to upgrade to 4.0 and check that.

Here is what we use in v3.7 with enabled localization, might help you:

DATE_FORMAT = 'd. F, Y.'
SHORT_DATE_FORMAT = 'd.m.Y.'
TIME_FORMAT = 'H:i'
SHORT_TIME_FORMAT = 'H:i:s'
DATETIME_FORMAT = 'd. F, Y. H:i'
SHORT_DATETIME_FORMAT = 'd.m.Y. H:i'

And here is what we use in v3.6:

DATE_FORMAT = 'N j, Y'
SHORT_DATE_FORMAT = 'Y-m-d'
TIME_FORMAT = 'g:i a'
SHORT_TIME_FORMAT = 'H:i:s'
DATETIME_FORMAT = 'N j, Y g:i a'
SHORT_DATETIME_FORMAT = 'Y-m-d H:i'

[opericgithub]

I already added this option. Does it work for you?

It works in 3.7. Currently I'm unable to upgrade to 4.0 and check that.

Here is what we use in v3.7 with enabled localization, might help you:

I was wrong, this time/date format actually doesn't work in our environment.
We were doing some tests with enabling/disabling localization, but we never made it work.