Opened 13 years ago
Last modified 12 years ago
#255 closed defect
Cannot delete media page if the file itself had been deleted — at Version 9
Reported by: | Aleksej | Owned by: | Sacha |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | programming | Keywords: | |
Cc: | Parent Tickets: |
Description (last modified by )
1. Have some media uploaded. 2. Delete the files manually from the user\_dev directory. 3. Try deleting a media through MediaGoblin (I used an "admin" user). Fails with "No such file or directory", shows an error page.
Change History (9)
comment:2 by , 13 years ago
Aleksej Serdjukov wrote: .. raw:: html <del> Fails with "No such file or directory", shows an error page. 4. Try deleting any media (that or other). .. raw:: html </del> Nothing happens at all, redisplays the media page. Sorry, those steps were not meant to be strike-though (there was a "-" before each ">").
comment:3 by , 13 years ago
(I suspect the issue for which I originally filed this ticket was actually from me forgetting to set the "I am sure" checkbox: `http://bugs.foocorp.net/issues/597. <http://bugs.foocorp.net/issues/597.>`_)
comment:4 by , 13 years ago
One simple solution to this is to simply return without doing anything if there's nothing to delete. However that could cause problems of its own... Suggestions on how to handle this pleasantly?
comment:6 by , 13 years ago
The original url for this bug was http://bugs.foocorp.net/issues/590 .
Relations:
#262: related
comment:7 by , 13 years ago
Owner: | set to |
---|---|
Status: | accepted → assigned |
comment:8 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
here is the fix https://gitorious.org/mediagoblin/mediagoblin/merge_requests/37 :D
comment:9 by , 12 years ago
Description: | modified (diff) |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
I'm pretty sure that fix hasn't been applied, so this shouldn't be closed.
Also, there are some issues with that merge request. First, it probably shouldn't have the comments that are there. Second, I think that's not the only reason that an OSError can get kicked up. Is silently doing nothing the right thing to do here? Should a message get logged?