Following #2615006: Give webmasters permission to delete contents of files and access pift settings for projects webmasters now have access to delete contents of the files uploaded in the issue queue. When opening Edit tab for an issue, webmasters will now see 'Delete contents' operation next to each file in the files table. Please note that this should only be done when sensitive private or personally identifiable information was uploaded to the issue by mistake, and such a removal was requested by the person who uploaded the file. Thanks!

(This is just fyi issue so marking fixed).

CommentFileSizeAuthor
#6 step3.png65.5 KBtvn
#6 step2.png29.62 KBtvn
#6 step1.png176.99 KBtvn
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tvn created an issue. See original summary.

apaderno’s picture

Is there any delay? I just tried, and the attachment is still visible and downloadable.

tvn’s picture

There might be slight delay due to caching provided by our infrastructure and a CDN we use.

apaderno’s picture

It seems the reference to the file is removed from the issue summary (the node), but there is still a reference in the comment. See www.drupal.org/node/2501851: The node doesn't have any reference to the uploaded file in comment #21, but the comment #21 still lists the uploaded file.

Should I open a bug report?

dddave’s picture

Yup. In this issue the file was marked as "don't display". Upon deletion I get a success message and the issue summary does no longer contain the file yet the comment itself does and the file is downloadable too.

tvn’s picture

FileSize
176.99 KB
29.62 KB
65.5 KB

There is no bug. We are not /deleting the file/, it is impossible to delete any file attached to issue, because of the way issue pages are built. What we are doing instead is deleting the contents of the file. So the reference to the file will still exist in the comment, and in the issue (it is just hidden from display in the files table on issue summary). And you still can download the file too. But the contents (and thus all sensitive info) will be gone.

Now, at the moment files are cached too heavily on Fastly, so we have to manually purge that cache for you to see changes to the file contents quickly. We've just done it for this specific file, and will work on automated way to purge those cached post Drupal 8 release.

Just to make sure we are talking about the same thing, here are the steps how to delete contents of a file attached to the issue:
step 1
step 2
step 3

dddave’s picture

Yeah, that was what I was doing and seeing.

apaderno’s picture

It was what I did it, and I was still able to download the file and read it. I guess it is just a matter of cached file, then.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.