Yes, You are right it was this patch.
On un 25, 3:36 pm, "Danny W. Adair" wrote:
> Hi Alexander,
>
> On Jun 15, 9:54 am, Alexander Jeliuc wrote:
>
> > Thank You, I found a patch for that. My version is already 1.2.1
> > After pathching fields.py and widgets.py it start working fine
>
> It helps
Hi Alexander,
On Jun 15, 9:54 am, Alexander Jeliuc wrote:
> Thank You, I found a patch for that. My version is already 1.2.1
> After pathching fields.py and widgets.py it start working fine
It helps others if you mention where they can find such a patch.
I assume it was this:
http://code.djangop
Thank You, I found a patch for that. My version is already 1.2.1
After pathching fields.py and widgets.py it start working fine
On Tue, Jun 15, 2010 at 12:49 AM, D3f0 wrote:
> Hi
> There's been a slighty change in 1.2, take a look at:
> http://docs.djangoproject.com/en/dev/ref/settings/#date-in
Hi
There's been a slighty change in 1.2, take a look at:
http://docs.djangoproject.com/en/dev/ref/settings/#date-input-formats
Nahuel
On 13 jun, 09:00, Jeliuc Alexandr wrote:
> Hello.
> I'm using django1.2.1 with i18n and l10n enabled...
>
> standart django admin date format is mm-dd-
> when
Hello.
I'm using django1.2.1 with i18n and l10n enabled...
standart django admin date format is mm-dd-
when it changes to Spain it becomes dd/mm/
Not problem it is possible to choice date and save it...
But if I want to edit row it becomes like standart mm-dd-...
No problem... but if I
5 matches
Mail list logo