Wrong date format

[fixed77]

NetBox version

v3.4.0

Python version

3.8

Steps to Reproduce

1. Set date format in configuration.py

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

2. Restart netbox
3. In main page after login date in bottom: 12/15/2022 11:11 a.m.
4. Other -> Change Log. Open any record. Time: 12/15/2022 10:22 a.m.
5. Open any Virtual machine. Created 01/26/2022 3 a.m. · Updated 1 month, 1 week ago (Without minutes)

Expected Behavior

Expected date format as specified in configuration.py

Observed Behavior

Observed wrong date format

[jeremystretch]

Observed wrong date format

The date and time are being formatted according to the locale specified by your browser. Automatic localization was enabled in NetBox v3.4 (see #10821), and the configured formats are now used only as fallbacks. This ensures that dates and times are presented to each user in their "native" format according to locale. (The option to disable localization is being removed in Django 5.0 entirely.)

[jeremystretch]

Seems that we have the option of "unlocalizing" specific date/time strings in templates. This might be appropriate in some places, but in general we probably want to stick to localized formats.

[fixed77]

Observed wrong date format

The date and time are being formatted according to the locale specified by your browser. Automatic localization was enabled in NetBox v3.4 (see #10821), and the configured formats are now used only as fallbacks. This ensures that dates and times are presented to each user in their "native" format according to locale. (The option to disable localization is being removed in Django 5.0 entirely.)

Then it doesn't seem to work properly.

[fixed77]

I trying open netbox with Firefox and Chrome, change locale in DevTools, but unfortunately no success.

[fixed77]

fixed by returning to settings.py:

USE_I18N = True
USE_L10N = False

[kkthxbye-code]

@jeremystretch - Found the issue I think, haven't tested though. According to the documentation, we need to activate the django.middleware.locale.LocaleMiddleware to support automatic localization. Otherwise the fallback is LANGUAGE_CODE for all users.

It might also be nice to expose LANGUAGE_CODE as a configuration value for fallback, and maybe even allow disabling the LocaleMiddleware to provide static localization.

[jeremystretch]

According to the documentation, we need to activate the django.middleware.locale.LocaleMiddleware to support automatic localization.

Ah, good catch! I forgot we had removed that from the middleware list.

It might also be nice to expose LANGUAGE_CODE as a configuration value for fallback

We can do this, though I worry it might be a bit confusing given that NetBox doesn't actually support different languages (although we've started tracking that work under #10833). We'll just have to be clear about its effect. I've opened #11214 for this.