#13506: admin does not allow saving of blank inline objects ----------------------------------+----------------------------------------- Reporter: PaulM | Owner: nobody Status: new | Milestone: Component: django.contrib.admin | Version: SVN Keywords: | Stage: Unreviewed Has_patch: 0 | ----------------------------------+----------------------------------------- If I have an inline that allows all fields to be blank, it is impossible to create a new object with all blank fields. I have to add some text to one of the fields, save it, then remove it, and re-save to create a new, blank object.
I only noticed this after setting extra = 0 on the TabularInline and then clicking the "Add another" button. This dynamically adds another row with the object as expected, but when I save, the row is not saved because it's blank. The admin seems to be treating this row the same way it treats the default empty rows. I don't know if this is a deliberate design decision (there are some use cases for "empty" objects, but you can create them outside of the inline if you absolutely have to), or if it's simply a UI issue. One solution might be to add some kind of widget in the delete column that provides the opposite function - a "create" toggle that turns green when any fields are modified or it is clicked. In any case, as the UI currently stands, clicking "add another" and then not getting another object saved is confusing and counter-intuitive. -- Ticket URL: <http://code.djangoproject.com/ticket/13506> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-upda...@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
