content_resource_delete points to non-existence path
GENERAL
TESTING
GENERAL
TESTING
Description
in both 2.3.1 and 2.5 beta, when you delete a file from resources, it creates an entry in content_resource_delete. However the file path entry points to a non-existent file. As far as I can tell the old file is simply removed, and not preserved anywhere. If that's what you're goign to do I'd like you to preserve the old file path. Then we could get it from a backup. By changing to a new file path that doesn't exist, you've removed the data we need to do restorations.
I consider this a serious bug. Users expect us to back up their files.
We applied this patch to 2.6.2 and it is mostly working. However, there is still one problem. If a file is deleted and then the same named file is uploaded again and deleted again, the second deletion is not recorded in CONTENT_RESOURCE_DELETE, i.e., no row is written in the table. Thus, you cannot find the path to retrieve that second version of the file.
Aaron Zeckoski September 7, 2010 at 2:57 PM
Attaching a patch which will cause the resource delete table to be correctly updated with the file path when resources are deleted.
Jean-François Lévêque August 2, 2010 at 3:08 AM
Trying automatic assignment of issue because it still happens with a supported version
Jean-François Lévêque August 2, 2010 at 3:07 AM
Updating affects based on U Va input.
Stephen Marquard July 29, 2010 at 7:47 AM
It would be great to get this fixed. As a workaround if you're using Oracle, you can follow UM's approach and use a trigger.
in both 2.3.1 and 2.5 beta, when you delete a file from resources, it creates an entry in content_resource_delete. However the file path entry points to a non-existent file. As far as I can tell the old file is simply removed, and not preserved anywhere. If that's what you're goign to do I'd like you to preserve the old file path. Then we could get it from a backup. By changing to a new file path that doesn't exist, you've removed the data we need to do restorations.
I consider this a serious bug. Users expect us to back up their files.