Open GoogleCodeExporter opened 9 years ago
"This is known. Packages aren't actually removed, they
are flagged as deleted, hence the 409 indicating a
conflict. The idea was precaution when deleting something
unintentionally." - Tobias Pape
How about a "Deleted files" page in the admin section, where you can restore or
"really delete" things?
Original comment by sean.p.d...@gmail.com
on 11 Jul 2012 at 11:29
On Jul 11, 2012, at 7:40 PM, Dale Henrichs wrote:
I guess there was no intention to prevent the re-uploading of deleted files ...
I recall that the files weren't actually deleted, but I thought that they would
have been renamed in such a way so as to not prevent a re-upload, although in
truth it has been about 5 years since I looked at that code, so I may be
misremembering ...
I would think that a rename of the package (allowing for multiple deletes of
the package) would be just fine ... if the mcz file ever needs to be
resurrected it can be done by an admin with direct access to the db... I'm not
sure that it's necessary to complicate things will a new UI feature ...
Original comment by sean.p.d...@gmail.com
on 11 Jul 2012 at 11:43
On Jul 11, 2012, at 7:40 PM, Dale Henrichs wrote:
> if the mcz file ever needs to be resurrected it can be done by an admin with
direct access to the db... I'm not sure that it's necessary to complicate
things will a new UI feature ...
I'm okay with that. How about some text on the delete confirmation page
mentioning that files are never really deleted and the process for resurrection?
Original comment by sean.p.d...@gmail.com
on 11 Jul 2012 at 11:46
I should fix that.
My current Idea is to move deleted versions to a trash repo, where deleting
actually happens.
Original comment by tobiasp...@gmail.com
on 5 Sep 2013 at 2:16
Original issue reported on code.google.com by
sean.p.d...@gmail.com
on 11 Jul 2012 at 6:43