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

------=_Part_155938_2107459713.1759327022439
Content-Type: multipart/alternative; 
	boundary="----=_Part_155939_1191819084.1759327022439"

------=_Part_155939_1191819084.1759327022439
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I was running Trac 1.2 with a custom field "due_date" and the DateField=20
plugin.
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=
=20
29.10.1999.

After upgrade to Trac 1.6, the custom field works ok, but the calendar=20
widget trac-datepicker does not follow the datefield settings and works=20
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=
=20
settings?




--=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/=
2d477b35-d671-4276-8507-ad85be991908n%40googlegroups.com.

------=_Part_155939_1191819084.1759327022439
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div>I was running Trac 1.2 with a custom field "due_date" and the DateFiel=
d plugin.</div><div>The definitions in trac.ini are:</div><div><br /></div>=
<div>[ticket-custom]<br />due_date =3D time<br />due_date.date =3D true<br =
/>due_date.date_empty =3D true<br />due_date.format =3D date<br />due_date.=
label =3D Term=C3=ADn dokon=C4=8Den=C3=AD<br />due_date.order =3D 0<br />du=
e_date.value =3D DD-MM-YYYY<br /><br /></div><div>[datefield]<br />first_da=
y =3D 1<br />format =3D dmy<br />separator =3D .</div><div><br /></div><div=
>This worked ok in ticket editing with correct setting in our date format a=
s 29.10.1999.</div><div><br /></div><div>After upgrade to Trac 1.6, the cus=
tom 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, w=
eek start on Sunday.</div><div><br /></div><div>How can I change the trac c=
alendar widget format to the original datefield settings?</div><div><br /><=
br /></div><div><br /></div><div><br /></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Trac Users&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:trac-users+unsubscribe-/[email protected]">trac-use=
rs+unsubscribe-/[email protected]</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
trac-users/2d477b35-d671-4276-8507-ad85be991908n%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/trac-use=
rs/2d477b35-d671-4276-8507-ad85be991908n%40googlegroups.com</a>.<br />

------=_Part_155939_1191819084.1759327022439--

------=_Part_155938_2107459713.1759327022439--