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_item = models.ForeignKey(DirectoryItem)
url = models.URLField(verify_exists=False, core=True)
title = models.CharField(max_length=40, blank=True)
alt = models.CharField(max_length=100, blank=True)
is_active = models.BooleanField(default=True)
is_primary = models.BooleanField(default=True)
Perhaps the issue is with the boolean fields having default set to
True - perhaps the widgets getting "checked" by default tricks the
admin in to thinking the fields havent been left blank?
If you cant replicate the issue, I will switch back to newforms-admin
and get a replication of the error.
(whilst I´m at it, I found another issue with admin (both newforms and
normal) with this model: it was throwing very strange errors with any
URL field set as unique=True)
On Feb 2, 4:03 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> 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 anything, and I still dont understand what the
> > solution is or will be.
>
> You shouldn't have to do anything. Inline-edited items that are empty
> should be ignored during add processing. There was a problem at one point
> where entirely blank items were being flagged as validation errors, but that
> has been fixed. I'm don't recall ever seeing problems with entirely empty
> items being constructed. Could you give details of your models and what
> behavior you are seeing (I'm not sure if you are getting validation errors
> for blank items or spurious all-blank items added to the database?). Maybe
> check trac for reports of problems like what you are seeing. I haven't been
> able to keep up to date for a few weeks, but had been running on
> newforms-admin without running into what it sounds like you are reporting,
> so it's either something specific to your models or perhaps something that
> has changed recently.
>
> Karen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
