Re: [Trac] custom field due_date with datefield plugin after upgrade to Trac 1.6

Jun Omae <[email protected]> Thu, 2 Oct 2025 17:22:22 +0900
Newsgroups gmane.comp.version-control.subversion.trac.general
Message-ID <[email protected]>
On 2025/10/01 22:57, Ales Horak wrote:
> I was running Trac 1.2 with a custom field "due_date" and the DateField p=
lugin.
> The definitions in trac.ini are:
>
> [ticket-custom]
> due_date =3D time
> due_date.date =3D true
> due_date.date_empty =3D true
> due_date.format =3D date
> due_date.label =3D Term=C3=ADn dokon=C4=8Den=C3=AD
> due_date.order =3D 0
> due_date.value =3D DD-MM-YYYY
>
> [datefield]
> first_day =3D 1
> format =3D dmy
> separator =3D .
>
> 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 wi=
dget 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 datefiel=
d settings?

It is unable to. The date picker always determines the format based on user=
's locale.

--=20
Jun Omae <[email protected]> (=E5=A4=A7=E5=89=8D =E6=BD=A4)

--=20
You received this message because you are subscribed to the Google Groups "=
Trac Users" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to trac-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
To view this discussion visit https://groups.google.com/d/msgid/trac-users/=
0c5e2336-3265-41cb-a16f-c35e4f02e51f%40gmail.com.