Adrian Holovaty wrote:
> On 9/28/05, Robert Wittams <[EMAIL PROTECTED]> wrote:
>
>>However, the patch I have been making to clean up the admin and
>>metasystem, on ticket #535, includes a feature that may help.
>>
>>Rather than doing edit_inline=meta.TABULAR or meta.STACKED, it is also
>>possible
On 9/28/05, Robert Wittams <[EMAIL PROTECTED]> wrote:
> However, the patch I have been making to clean up the admin and
> metasystem, on ticket #535, includes a feature that may help.
>
> Rather than doing edit_inline=meta.TABULAR or meta.STACKED, it is also
> possible to do edit_inline="path/to/t
Adrian,
My thought was that anything not marked core=True that could be left
blank and/or had a default value, could potentially be excluded from
display.
So, to answer your question, I was imaging that fields with blank=True
would be left blank, and fields with a default value set would get tha
mortenbagai wrote:
> Hello,
>
> I have two model objects, Section and Page. Each Page is mapped to a
> Section through a regular ForeignKey field. On the Section edit detail
> display in the Django admin app, I'd like to list the Page objects
> belonging to that Section and having a few fields be
On 9/28/05, mortenbagai <[EMAIL PROTECTED]> wrote:
> However, it seems to me that there is no way to control which fields
> are displayed when editing an object inline through its ForeignKey
> relation. At first, I thought only fields marked core=True would be
> displayed, but that does not seem t
5 matches
Mail list logo