You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
File entity provides interfaces for managing files. It also extends the core file entity, allowing files to be fieldable, grouped into types, viewed (using display modes) and formatted using field formatted.
vs
Media entity provides a 'base' entity for media. This is a very basic entity
which can reference to all kinds of media-objects (local files, YouTube
videos, Tweets, Instagram photos, ...). Media entity provides a relation between
Drupal and the media resource.
From those 2 descriptions from file_entity module and media_entity module, I may be hard for a site builder to decide whether to use a Fieldable entities or Media entities to achieve different use cases.
I'm just about modelling a complex site and torn between the 2 approaches, so let's share some notes:
While file-entity makes local files fieldable, media-entity has a reference to either a local file or a remote resource. So if you need or will need remote resources, media-entitiy is your only choice.
Both file and media allow for different bundles (thus fields) for different file types
Currently there seem more (media) file field formatters than file-url formatters (x)
Media has a plugin system to extract (thus denormalize) metadata to fields that has no correspondence for file-entities (x)
(x): Note: It might make sense to build bridges here.
My gut feeling is that most traction is going to the more generic media entities, so it might make sense to focus on this and cover the missing spots (like (BU) above).
vs
From those 2 descriptions from file_entity module and media_entity module, I may be hard for a site builder to decide whether to use a Fieldable entities or Media entities to achieve different use cases.
Take a look to the first 5 minutes of this video https://www.youtube.com/watch?v=vyav4VBuLng for more context.
The text was updated successfully, but these errors were encountered: