The current admin (and the newforms one) doesn't allow enough
customization to make it user-friendly. That may be a feature, but
that is really boring to need to write its own admin because of the
limitations of the existing one.
In my case, I just have a ForeignKey to an User. At the first save,
On Mon, 2007-04-16 at 08:58 +, [EMAIL PROTECTED] wrote:
>
> I don't think one it's possible to add to the "fields" admin option,
> so you'll end up having all editable fields in it:
>
> class MyModel()
> field1 = models.CharField(editable=False)
> field2 = models.CharField()
> ..
I don't think one it's possible to add to the "fields" admin option,
so you'll end up having all editable fields in it:
class MyModel()
field1 = models.CharField(editable=False)
field2 = models.CharField()
...
fieldn = models.SomeField()
Class MyModelAdmin()
fields = {"field1"
On Tue, 2007-04-10 at 16:30 +, James Stembridge wrote:
> Hi Philippe
>
> On Apr 10, 1:41 pm, "[EMAIL PROTECTED]"
> <[EMAIL PROTECTED]> wrote:
> > http://code.djangoproject.com/ticket/3990
>
> Perhaps a simpler way of handling things:
> 1. Leave the current behaviour of "editable=False" as is
I like your idea because it doesn't add a new option to the admin
class. I went for the simplest possible implementation while this
would require modifying a bit newforms to allow editable=False fields
to be forced in. On the other hand, one might want to have some
editable=True fields as readonl
Like I said, I wanted to do that this aftertoon and then I saw your
patch... which fits exactly to what I needed. It is imo an useful
change - and not only because I would need it - that should be
integrated in the core.
On 10 avr, 14:41, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> Done:
>
>
Hi Philippe
On Apr 10, 1:41 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> http://code.djangoproject.com/ticket/3990
Perhaps a simpler way of handling things:
1. Leave the current behaviour of "editable=False" as is, i.e. if set
the field will not by default appear in the admin interface.
Sorry, it seems, that I misunderstood something, because I was reading
only this discussion, but not the ticket information.
Regards,
Aidas Bendoraitis aka Archatas
On 4/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Done:
>
> http://code.djangoproject.com/ticket/3990
>
> Please note
Done:
http://code.djangoproject.com/ticket/3990
Please note that the submitted is different from what we discussed. I
have created a new option for the AdminModel class and left the non-
editable fields out of the picture.
Aidas: what you're looking for is editable=False :)
--~--~-~--
Shouldn't there be a possibility to have fields that were not visible
in the admin at all, like sorting paths for multilevel objects (i.e.
categories), pickled objects, or other system data that makes no sense
to "normal human beings". I would propose to have some attribute like
visible=False or h
On Mon, 2007-04-09 at 18:28 +, [EMAIL PROTECTED] wrote:
>
> There is a problem with:
> http://code.djangoproject.com/ticket/3247
> http://groups.google.com/group/django-developers/browse_thread/thread/50150b61aca46a7e
>
> I've made a first working version but my implementation reverses the
>
There is a problem with:
http://code.djangoproject.com/ticket/3247
http://groups.google.com/group/django-developers/browse_thread/thread/50150b61aca46a7e
I've made a first working version but my implementation reverses the
changes described in the above ticket/discussion. Here's a summary of
wha
On Sun, 2007-04-08 at 15:40 +, [EMAIL PROTECTED] wrote:
> You must mean those:
>
> http://code.djangoproject.com/ticket/1714
> http://code.djangoproject.com/ticket/342
>
> I'm currently trying to create a patch but I'm not really confortable
> with changing options so I'd rather have input f
You must mean those:
http://code.djangoproject.com/ticket/1714
http://code.djangoproject.com/ticket/342
I'm currently trying to create a patch but I'm not really confortable
with changing options so I'd rather have input from the devs.
Currently, "editable=False" for a field really means privat
On Sat, 2007-04-07 at 14:17 +, [EMAIL PROTECTED] wrote:
> There are a lot of fields I'd like to mark as editable=False in my
> models but this make them disappear from the admin interface, both
> when creating and modifying an object. I think it would be useful to
> be able to specify readonly
There are a lot of fields I'd like to mark as editable=False in my
models but this make them disappear from the admin interface, both
when creating and modifying an object. I think it would be useful to
be able to specify readonly fields that would be defined and validated
when the object is creat
16 matches
Mail list logo
