Changes between Initial Version and Version 1 of Ticket #13223, comment 18


Ignore:
Timestamp:
Feb 13, 2012, 4:29:49 AM (13 years ago)
Author:
Ramiro Morales

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #13223, comment 18

    initial v1  
    1 I've attached an updates version of the patch that simply allows it to apply cleanly in trunk.
     1I've attached an updated version of the patch that simply allows it to apply cleanly in trunk.
    22
    3 But th OP in ticket #17417 (slightly related to this one) makes a good point regarding the current buggy behavior and that isn't fixed by this patch:
     3But the OP in ticket #17417 (slightly related to this one) makes a good point regarding the current buggy behavior that isn't fixed by this patch:
    44
    5 ''If you press "Save as New" without changing the slug field a ValidationError? is raised, and the for is displayed to the user with a warning (as it should). However, '''the url is that of the old entity''' ...''
     5''If you press "Save as New" without changing the slug field a ValidationError? is raised, and the form is displayed to the user with a warning (as it should). However, '''the url is that of the old entity''' ...''
    66
    77That means that at that point the user is presented with the admin add view/form for a new instance of the model, pre-filled with values of the original instance (the one whose edit view/form she was looking at when she decided to press the ''Save as new'' button) but the URL in the browser address bar hasn't changed.
Back to Top