Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Tue, 2008-03-04 at 12:59 -0600, James Bennett wrote:
> > Ticket #6705 [1] proposes that 'form.errors' be changed to somehow
> > provide a "prettier" display not based on the underlying field name
> > (which is cur
On Tue, 2008-03-04 at 12:59 -0600, James Bennett wrote:
> Ticket #6705 [1] proposes that 'form.errors' be changed to somehow
> provide a "prettier" display not based on the underlying field name
> (which is currently used as the key in the errors dictionary).
&g
On Tue, Mar 4, 2008 at 9:22 PM, Dj Gilcrease <[EMAIL PROTECTED]> wrote:
> he cant do something like http://dpaste.com/38006/ ?
The desired case is for {{ form.errors }} to somehow do something
similar, but automatically.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of c
Dj Gilcrease said the following:
> On Tue, Mar 4, 2008 at 10:59 AM, James Bennett <[EMAIL PROTECTED]> wrote:
>> Thoughts?
>
> he cant do something like http://dpaste.com/38006/ ?
Should probably be field.label instead of field.label_tag, no? :)
--
Collin Grady
"I don't think so," said Descar
On Tue, Mar 4, 2008 at 10:59 AM, James Bennett <[EMAIL PROTECTED]> wrote:
> Thoughts?
he cant do something like http://dpaste.com/38006/ ?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
Ticket #6705 [1] proposes that 'form.errors' be changed to somehow
provide a "prettier" display not based on the underlying field name
(which is currently used as the key in the errors dictionary).
The person who opened this ticket contends that it is a common issue,
