Would you consider this as unexpected behavior and if so, would it be
interesting to preserve that state?
--
Ticket URL: <https://code.djangoproject.com/ticket/22736>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
How do you get a save and continue button on the pop-up? Are you using a
custom template? I don't think the pop-up is really designed to be used
like that.
--
Ticket URL: <https://code.djangoproject.com/ticket/22736#comment:1>
Comment (by sthzg):
Yes, I customized it to achieve this behavior. It makes more sense in my
use case than returning to the change list (or closing the popup right
away after saving). I thought it would be nice if the popup context
remained in that scenario as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/22736#comment:2>
Comment (by sthzg):
Replying to [comment:1 timo]:
> How do you get a save and continue button on the pop-up? Are you using a
custom template? I don't think the pop-up is really designed to be used
like that.
Sorry, I wrote an answer (comment [comment:2]) but added a new comment
instead of hitting the reply button.
--
Ticket URL: <https://code.djangoproject.com/ticket/22736#comment:3>
Comment (by timo):
What do you mean by "popup context"? Did you have a look if overriding
`templates/admin/popup_response.html` might help? There's JavaScript logic
there which closes the popup if that's what you're trying to avoid.
--
Ticket URL: <https://code.djangoproject.com/ticket/22736#comment:4>
* status: new => closed
* resolution: => needsinfo
--
Ticket URL: <https://code.djangoproject.com/ticket/22736#comment:5>