This extensible module will create fields for content types that can be used to display video, image, and audio files from various third party providers. When entering the content, the user will simply paste the URL or embed code from the third party, and the module will automatically determine which content provider is being used. When displaying the content, the proper embedding format will be used.
The module is only an engine, and requires a supported module to function. These include 'Embedded Image Field', 'Embedded Video Field' and 'Embedded Audio Field'. These modules are included in the contrib folder of the module, so they can be easily activated from the module administration page.
Please note: As of emfield 2.x, provider files for these modules are no longer included with the main emfield module, and must be downloaded separately- please see the list of projects providing provider files below.
Modules extending Embedded Media Field
The following modules work in conjunction with this project, largely to expose media providers (you'll need at least one of these to make the module useful):
Media: Bits On The Run
Media: Fox News
Media: National Public Radio
The Media: Video Flotsam, Media: Audio Flotsam, and Media: Image Flotsam modules contains various provider files that were included as part of emfield 1.x but not 2.x, and which do not have their own "Media:" module yet.
These extend the project in other ways:
The following modules are packaged with the module (and you need at least one of them to get this working):
The Embedded Video Field module already supports, through the "Media:" modules listed above, YouTube, Google, Blip.TV, Revver, MySpace, MetaCafe, Last.fm, JumpCut, SevenLoad, Spike TV, Daily Motion, Veoh, Vimeo, Tudou, imeem, Guba, Yahoo Music Video, and Live Video video formats. An api allows other third party video providers to be supported using simple include files and provided hooks. (Developers: examine the documentation of /providers/example.inc for help in adding support for new providers).
The Embedded Image Field module supports third party image content.
The Embedded Audio Field module supports third party audio content.
The administer of a site may decide whether to allow all content providers, or only a certain number of them. They may further be limited when configuring the field.
The Embedded Media Thumbnail module allows editors to override the thumbnails of videos with their own, with a simple upload field. Activate the module, then check the new box in any defined video fields to allow custom thumbnails.
Embedded Inline Media creates a new filter/input format that will allow users to post a link to a video in the body of a node or comment, and have it automatically display the video instead. Currently only works with providers for the Embedded Video Field (Image and Audio soon enough, hopefully).
Read the README.txt files in the individual contrib folders for more information.
Drupal 5 to 6 Upgrade notice
IMPORTANT: If you are upgrading from Drupal 5, please make certain to run all the available updates before doing so.
And a reminder about CCK: Before upgrading your site to Drupal 6, you must upgrade CCK to version 5.x-1.9 and run all updates. Updating to 5.x-1.9 is especially important before an upgrade because that version includes a fix to ensure you don't lose data when you disable modules in preparation for the upgrade.
Author: Aaron Winborn
Development Began 2007-06-13
Requires: Drupal 4.7, 5, or 6, Content (CCK)
Other modules that work with Emfield: FeedAPI/FeedAPI Element Mapper (click here for instructions for importing Embedded Video Feeds), Media Actions, Asset, Lightbox2 & Thickbox.
- Maintenance status: Seeking new maintainer
- Development status: No further development
- Module categories: Content, Content Construction Kit (CCK), Content Display, File Management, Filters/Editors, Media, Third-party Integration, Views
- Reported installs: 32,523 sites currently report using this module. View usage statistics.
- Downloads: 412,355
- Last modified: February 16, 2016
- Stable releases are covered by the security advisory policy.
Look for the shield icon below.