Closed (won't fix)
Project:
FileField Sources
Version:
6.x-1.2
Component:
General
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
24 Dec 2010 at 17:22 UTC
Updated:
28 Apr 2011 at 16:56 UTC
Jump to comment: Most recent file
Comments
Comment #1
quicksketchThanks, this seems like a good idea. I was worried about more LIKE statements increasing SQL query time, but it doesn't look like it has any significant effect on the query time adding additional LIKEs. Code needs a bit more cleaning up though to match coding standard, but I can probably clean this up next time I'm working on FileField Sources.
Comment #2
tatewaky commentedMissing validation to enable use of files on Drupal that not belongs to the node of the specific content type.
Comment #3
tatewaky commentedMissing validation to enable use of files on Drupal that not belongs to the node of the specific content type.
Comment #4
quicksketchThe new change is not related and something that absolutely cannot be included (in this patch or otherwise). It would effectively turn off deletion of all files in all of Drupal.
Comment #5
tatewaky commentedHi quicksketch,
would you please explain to me your point, i would like to know what i'm doing wrong.
Thanks in advance
Comment #6
quicksketchhook_file_references() is used to check if a file may be deleted. This additional hook makes it so that FileField Sources claims that it is using every file in Drupal no matter what, effectively making it so FileField will never let any file be deleted. Modules should only claim usage on a file if they were the module responsible for uploading it. For FileField Sources, it's merely a tool to provide alternative mechanisms for FileField (which implements hook_file_references() already).
Comment #7
quicksketchIf you're still interested in rerolling the original patch I'll take a look, but the idea of making all files in the entire files table available is not feasible for security reasons.
Comment #8
tatewaky commentedi am, what should i do from now?