Design decision on ticket #13223 Igor Sobreira Tue Feb 21 15:01:14 2012
Hi, I'm working on a patch for #13223 , but I need some help on how to proceed. The solution I would like to work on is to replace the "save as new" button for a "clone object" link. This is how I understood the suggest on the ticket, and the way makes more sense to me. I've started to create a clone_view() in admin, and submitted a prototype-not-yet-done patch, with the idea. When the user enables the "save_as" admin option (maybe change the name) a "save as new" *link* appears, which opens a <obj id>/clone/ view pre-filled data based on the object id from the url. Any feedback would be welcome. There is a drawback: file uploads would not work. The user would need to upload a new file (or the same). Maybe a new ticket would be better to find the best solution to this (#14760 !?). What I was planning to do is provide a template method called by clone_view() function where the user could copy the file on disk or do anything she wants regarding form filling on GET. Thanks in advance, Igor.  https://code.djangoproject.com/ticket/13223 -- Igor Sobreira www.igorsobreira.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [EMAIL PROTECTED] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
- Design decision on ticket #13223 Igor Sobreira 2012/02/21 <=
- Re: Design decision on ticket #13223 Thomas Woolford 2012/02/21