> Yes, I think that is the problem. It's not just Boolean fields -- any field
> that has a default set to something non-blank will make the inline-edited
> item seem non-empty on a save attempt. Not sure what the right way to fix
> this is...it's probably worth opening an issue in trac if you ca
On Feb 3, 2008 10:38 AM, NickJ <[EMAIL PROTECTED]> wrote:
>
> I was definately getting this issue. Cant find any related issue in
> track. I have gone back to standard trunk due to this error so I cant
> retest right now, but I think the inline model that gives this error
> is:
>
> class Link(mode
I was definately getting this issue. Cant find any related issue in
track. I have gone back to standard trunk due to this error so I cant
retest right now, but I think the inline model that gives this error
is:
class Link(models.Model):
""" Outbound link for directory item. """
directory_
On Feb 1, 2008 7:52 PM, NickJ <[EMAIL PROTECTED]> wrote:
>
> Thanks for the response. So what code do I need to add so that, when
> creating a new object, the admin doesnt try to create related fields
> that are left entirely blank? I still see core=True as an option, but
> it no longer does anyth
Thanks for the response. So what code do I need to add so that, when
creating a new object, the admin doesnt try to create related fields
that are left entirely blank? I still see core=True as an option, but
it no longer does anything, and I still dont understand what the
solution is or will be.
On Feb 2, 2008 4:32 AM, NickJ <[EMAIL PROTECTED]> wrote:
>
> I wanted to bump this up, because if there is no solution I think this
> is an issue which needs to be rectified before it is merged to trunk.
There is a solution - it just hasn't been documented yet.
The oldforms 'core=True' approach
I wanted to bump this up, because if there is no solution I think this
is an issue which needs to be rectified before it is merged to trunk.
As Felix noted, without core=True support, anything listed as in-line
*has to be created when you create the parent object. e.g. if a Pizza
can have 1+ toppi
Felix,
> Inline objects now have a 'delete' checkbox which is used for removing
> objects.
Oh yeah! Well that answers the delete question, thanks.
> I believe that the usual admin rules apply for creating models i.e.
> all fields without blank=True will be required, otherwise you'll get
> valid
Hi James,
> I have hit a wall with newforms-admin, which seems obvious but I can't
> find mention of a solution anywhere.
>
> As I understand it, part of core=True was defining when the related
> object was created or deleted.
>
> eg: "The related model being edited inline must specify one or mor
Hi All,
I have hit a wall with newforms-admin, which seems obvious but I can't
find mention of a solution anywhere.
As I understand it, part of core=True was defining when the related
object was created or deleted.
eg: "The related model being edited inline must specify one or more
"core" field
10 matches
Mail list logo