I've created a ticket for this issue:
https://code.djangoproject.com/ticket/23857
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
re: "There shouldn't be a delete box for unsaved items, right?"
This is a special case - you are taking an existing record and "Save as
new"-ing (or however you say that), so there are existing associated
records that you are copying as well. But, in this case, I think the user
would change a
Hello,
Thanks for replying! Sorry for delayed response.
I am not using custom forms or custom templates.
It looks like, with "Save as new", django first makes a full copy of the
base record and all the child records, including those that are marked for
deletion, and then it subsequently
Hello,
That does seem odd. Are you using a custom form or custom template at all?
There shouldn't be a delete box for unsaved items, right?
Collin
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop
Hello,
I have an Event model (for an event like a concert or a play) that can have
many Event_Dates (different showing dates and times of the concert of
play). The model relation is implemented with a ForeignKey from the
Event_Date model to the Event.
In the django admins, I have the
5 matches
Mail list logo
