Manual delete with FID not working if file already missing (fileusageinterface error) [#2730599]

Some files were deleted on the server but still in the db (temporary)
I listed their FID in the manual delete Tab and click "Engage"
Everything runs fine (I mean no mistake) but the files are still there!!
I made another try by adding only one FID but I got this error:

Une erreur HTTP AJAX s'est produite.
Code de statut HTTP : 500
Informations de débogage ci-dessous.
Chemin : /batch?id=34&op=do_nojs&op=do
StatusText: Internal Server Error
ResponseText :

Comment	File	Size	Author
#5	fancy_file_delete-change_method_to_delete-2730599-5.patch	432 bytes	myLies
#5

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

21 May 2016 at 12:57

DuneBL created an issue. See original summary.

Comment #2

DuneBL

French

CreditAttribution: DuneBL commented 21 May 2016 at 13:11

As a side note, I just ran file_delete($myFID); and the file was correctly deleted!

Comment #3

HongPong CreditAttribution: HongPong as a volunteer and at kor group commented 28 July 2016 at 04:41

I had similar errors. Thanks for the tip. This is a messy thing to sort out!
It would be good if this can specifically scrub fid in the database after the files are gone.

error was
FileUsageInterface not found in fancy_file_delete_batch

It has to do with if force delete is checked probably. If you're not forcing, the interface has nothing. I think interface has to be implemented?

else {
FileUsageInterface::delete($file);
}

Comment #4

HongPong CreditAttribution: HongPong as a volunteer and at kor group commented 28 July 2016 at 04:41

Title:

Manuel delete with FID not working

» Manual delete with FID not working if file already missing (fileusageinterface error)

Comment #5

myLies CreditAttribution: myLies as a volunteer commented 28 July 2016 at 14:57

File	Size
fancy_file_delete-change_method_to_delete-2730599-5.patch	432 bytes

Yes, this way needs implementation.
I сreated a simple patch. It may fix this error in case when you wouldn't use the "force remove"
It work for me

Comment #6

myLies CreditAttribution: myLies as a volunteer commented 28 July 2016 at 15:13

Status:

Active

» Needs review

Comment #7

labboy0276 CreditAttribution: labboy0276 commented 28 July 2016 at 22:16

Thanks for this, I havent touched the d8 version in quite some time. I will roll this when I work on the D8 version one day.

Comment #8

labboy0276 CreditAttribution: labboy0276 commented 21 October 2016 at 16:09

Status:

Needs review

» Closed (won't fix)

One day when will will retool the d8 version, but since VBO is still in a state of flux, I am not going to port this patch in. I will leave it here for the universe to use as need be though.

Comment #9

HongPong CreditAttribution: HongPong as a volunteer and at kor group commented 21 October 2016 at 16:20

labboy0276 I would still suggest rolling in the #5 patch from myLies because the patched line addresses an un-implemented interface. It does improve the codebase.