search

google-code-export / sandy-disaster-recovery

Automatically exported from code.google.com/p/sandy-disaster-recovery
2 stars 2 forks source link

Add confirmation message after deleting a site #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
As of r24, when you delete a site, you're just redirected back to /sites 
without any confirmation that the deletion was successful. We should probably 
display a "success!" message to the user.

Original issue reported on code.google.com by bruc...@gmail.com on 5 Nov 2012 at 3:39

GoogleCodeExporter commented 9 years ago

Original comment by p...@peppyheppy.com on 5 Nov 2012 at 4:53

GoogleCodeExporter commented 9 years ago

Original comment by p...@peppyheppy.com on 5 Nov 2012 at 7:05

GoogleCodeExporter commented 9 years ago 
Low priority. This is not a common use case. Usually, the status will just be 
changed to closed.

Original comment by rostovp...@gmail.com on 7 Nov 2012 at 3:33

GoogleCodeExporter commented 9 years ago 
Agreed. Not a common use case.

Original comment by v...@aarontitus.net on 7 Nov 2012 at 4:35

GoogleCodeExporter commented 9 years ago 
Should this be merged with Issue 21? Should we permit deletion, or just 
deactivation?

Original comment by v...@aarontitus.net on 22 Jan 2013 at 2:46

GoogleCodeExporter commented 9 years ago 
Should be finished. Delete an incident to test.

Original comment by andy.n.g...@gmail.com on 17 Feb 2013 at 4:28

GoogleCodeExporter commented 9 years ago 
I made the following notes on testing: 1. Delete feature is ONLY from the 
"Browse Cases" link. This is fine for now. 2. A confirmation message appeared, 
as expected. 3. After deletion, I was returned to "Browses Cases," where the 
deleted case still appeared on the list (error), until I refreshed the page. 4. 
The total work order sites incremented down after deletion, as expected.

So, if there is a way to make the "Browse Cases" page refresh after deletion, I 
think this one is done.

Original comment by v...@aarontitus.net on 17 Feb 2013 at 1:46

GoogleCodeExporter commented 9 years ago 
We do refresh it, but with cache and the tasks of a distributed data base, we 
can't fix this unless we do something like add a line that makes the program 
sleep for perhaps a whole second.

Original comment by andy.n.g...@gmail.com on 23 Feb 2013 at 7:18

GoogleCodeExporter commented 9 years ago 
Yeah, it's not worth the overhead at this point.  marking fixed.

Original comment by v...@aarontitus.net on 25 Feb 2013 at 3:05