> Well, not universally true. There are a lot of cases where this would,
> in fact, be useful information (e.g. last HTTP return code and message
> when editing an RSS feed entry for a planet syndication application, or
> the mail refusal code for a person's entry in newsletter software so you
> c
On Thu, 2007-12-20 at 09:20 -0600, James Bennett wrote:
> On Dec 20, 2007 9:03 AM, GodOfGeeks <[EMAIL PROTECTED]> wrote:
> > The problem is that when I set the fields to editable=False then they
> > won't be visible in the adminModel
>
> The admin interface is deliberately designed not to have
>
On Dec 21, 2:59 am, brian corrigan <[EMAIL PROTECTED]> wrote:
> try using
>
>
Seems like a good idea, but remember that a DISABLED field's value
does _not_ get sent back with the HttpRequest submission, and will
therefore be flagged as missing input if the form's field definition
doesn't have "r
On Dec 21, 2:20 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On Dec 20, 2007 9:03 AM, GodOfGeeks <[EMAIL PROTECTED]> wrote:
>
> > The problem is that when I set the fields to editable=False then they
> > won't be visible in the adminModel
>
> The admin interface is deliberately designed not
On Dec 20, 2007 9:03 AM, GodOfGeeks <[EMAIL PROTECTED]> wrote:
> The problem is that when I set the fields to editable=False then they
> won't be visible in the adminModel
The admin interface is deliberately designed not to have
"display-only" data -- the thinking has been that things which can't
Hello all,
I have a problem and I have been googling around for many days for the
solution without any hope. It will be great if someone can help me out
with it.
I have a model Called 'Country' with the following fields
male_count = models.SmallIntegerField( null=True, blank=True,
edita
6 matches
Mail list logo
