custom field due_date with datefield plugin after upgrade to Trac 1.6

23 views
Skip to first unread message

Ales Horak

unread,
Oct 1, 2025, 9:57:02 AMOct 1
to Trac Users
I was running Trac 1.2 with a custom field "due_date" and the DateField plugin.
The definitions in trac.ini are:

[ticket-custom]
due_date = time
due_date.date = true
due_date.date_empty = true
due_date.format = date
due_date.label = Termín dokončení
due_date.order = 0
due_date.value = DD-MM-YYYY

[datefield]
first_day = 1
format = dmy
separator = .

This worked ok in ticket editing with correct setting in our date format as 29.10.1999.

After upgrade to Trac 1.6, the custom field works ok, but the calendar widget trac-datepicker does not follow the datefield settings and works with dates in the format of 10/29/1999, week start on Sunday.

How can I change the trac calendar widget format to the original datefield settings?




Jun Omae

unread,
Oct 2, 2025, 4:22:34 AMOct 2
to trac-...@googlegroups.com
It is unable to. The date picker always determines the format based on user's locale.

--
Jun Omae <jun...@gmail.com> (大前 潤)

Holger Bruenjes

unread,
Oct 2, 2025, 5:03:49 AMOct 2
to trac-...@googlegroups.com
Hallo

Am 01.10.25 um 15:57 schrieb Ales Horak:

> After upgrade to Trac 1.6, the custom field works ok, but the calendar
> widget trac-datepicker does not follow the datefield settings and works
> with dates in the format of 10/29/1999, week start on Sunday.
>
> How can I change the trac calendar widget format to the original datefield
> settings?

I dont now is that correct for you

I set as locale in the .wsgi Script too

environ['trac.locale'] = 'de_DE.utf8'

that worked for me

Holger

Ales Horak

unread,
Oct 4, 2025, 9:00:49 AMOct 4
to Trac Users
thank you, I have tried setting the `environ` value, but it did not help.

finally, the problem was in the Ubuntu 24.04 Trac package, which is missing the file 
`/usr/lib/python3/dist-packages/trac/htdocs/js/jquery-ui-i18n.js`. without it, the
datepicker ignores the current locale.

I have also found out that the problem has already been reported, including
its workaround, as described in this bug report, but not fixed in this LTS version.


Dne čtvrtek 2. října 2025 v 11:03:49 UTC+2 uživatel Holger Bruenjes napsal:
Reply all
Reply to author
Forward
0 new messages