Hi there,

The change proposed in Delete media assets from the filesystem after parent media entity is deleted will not work for orphan files already in the system. Plus the site-builder should be a able to delete files from the system in any case.

Options:

File Delete (D8) https://www.drupal.org/project/file_delete uses the temporary flag so we'll still have to wait for the offending file to go away with the garbage collection.

  • Pros: Uses the same process proposed for 3150710
  • Cons: From a sitebuilder perspective, we can assume that something bad has happened and we want the file gone right away at this stage!

Use view bulk operations.

  • Pros: Uses our consistent approach to these tasks
  • Cons: we tested it with the delete entity action and it did not work. The system yielded an access denied.
  • Mitigation: research options and tools available.

Considerations

  • Create a are you sure dialogue
  • Don't allow this for usage >0?

Ta,

Heike

CommentFileSizeAuthor
#5 file-delete-vbo_3150714_5.patch14.96 KBdanielveza

Comments

HeikeT created an issue. See original summary.

heiket’s picture

Issue summary: View changes
heiket’s picture

Issue summary: View changes
heiket’s picture

Title: Review options to allow the sitebuilder delete files from the file tab » Review options to allow the sitebuilder to delete files from the file tab
danielveza’s picture

StatusFileSize
new14.96 KB

Makes sense!

I've tested this further since our first meeting and it works well out of the box with VBOs. I believe that old site we were testing on may have had issues with the file system I believe are a red-herring. Lets catch up about this.

I've attached a patch to add this functionality in. Config level change only.

Note that this patch does not yet address the considerations section

danielveza’s picture

Status: Active » Needs review

  • DanielVeza committed 3899548 on 5.0.x
    Issue #3150714 by DanielVeza, HeikeT: Review options to allow the...
danielveza’s picture

Status: Needs review » Fixed

Passed internal testing from @HeikeT, committed.

Thanks!

Status: Fixed » Closed (fixed)

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