Closed (works as designed)
Project:
D7 Media
Version:
7.x-2.x-dev
Component:
Media Bulk Upload
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
23 Jul 2014 at 21:10 UTC
Updated:
21 Apr 2016 at 09:28 UTC
Jump to comment: Most recent
Comments
Comment #1
shadysamir commentedComment #2
shadysamir commentedComment #3
Leagnus commentedYep, i've got same issue.
IMHO, anybody can create new file type only if mime differs from existing.
Comment #4
dave reidI don't believe that the file type selection works with the bulk upload functionality yet, and we don't have a plan in place for supporting it. Assistance for how the UI and workflow for that would work, would be welcome.
Comment #5
nerdoc commentedThis has nothing to do with bulk upload, as I don't have it installed here, but I have the exact same issue, with a file field in a webform content type.
I have two similar file types with application/pdf MIME type.
I chose "pdf" at the webform as only available file type. When uploading a file on this webform, it is saved, and then listed under
admin/content/fileas my custom type ("news"), without any chance to influence it.Then I checked the "normal" file field (without webform). I added a file field to a new content type, and disabled Audio, Video, and my custom PDF type "news" for this file field, only "Document" is allowed. Despite that setting, when uploading a file there, I am asked whether I want to save it as "News" or "Document" from the Media module.
IMHO this is a severe bug. I just don't know of which module ;-) - webform could be the culprit too.
edited (3x) - cleaned up.
Comment #6
nerdoc commentedI found it (at least for webform) - webform asks file_entity, exactly using file_get_type() which type the uploaded file is. This function invokes all hook_file_type, and if it is a pdf (in my case) gets an array of 2 types back:
array("news", "document").And then it calls:
Which picks the (randomly) first element of the array and returns it as single item.
The OP wrote about bulk upload, maybe it is similar there.
So, I suppose this is no Media bug...
Comment #7
nerdoc commentedThis seems to be a file entity bug.
Comment #8
nerdoc commented