Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
Provides integration with the Spotify Metadata API and a field to display artist, album and track information with a link that opens the Spotify client. Since 7.0-rc2 you can also output the data as a Spotify play button.
First beta is out. All XML-functions removed.
Rewrite of basics functions. Using json instead of XML when getting information from Spotify. Uses images from Spotify instead of Amazon. You could now use Image styles, and images are stored locally.
This module contains Embedded Audio Field providers (i.e. emfield's emaudio module) that don't currently have their own "Media: " module yet (see the emfield project page for more information on the move towards the new and vastly improved Media Module).
This module provides support for international banking standards and identifiers such as BIC (ISO 9362) and IBAN (ISO 13616).
Current features include CCK field types for BIC and IBAN identifiers, as well as an API to parse and validate those identifiers (with specific IBAN support for 52 countries, up to date as of Release 13 of the ISO 13616 IBAN Registry).
When editing CCK fields, the selector is built with the types where the field really exists. This behavior has the nice effect that you can quickly check if the field being edited is shared by simple inspection of the selector options, and it offers a quick method to switch from one type to another to compare the instance related settings of the field on different content types.
The EMBridge module extends the image management functionality of Drupal by connecting it to EnterMedia, an open-source digital asset management system distributed under the GNU General Public License, used to search, manage, reuse, and track all digital files.
Generally, this project enables content authors to see from any current content (entity) its dependent entities content.
Project overcome a major content control difficulty for content authors.
Provide content authors ability to track external content which refers to current content, without the need to check mass of external content to find out whether each external content refers to current content or not.
Content dependency main advantages:
Easily manage content dependencies - you can view/update for each content entity it's dependent entities from one places.
Backward Compatibility - You can install this module & start use it without need to perform any change in your content structure.
UPDATE: Module development has resumed since a new maintainer has been appointed.
Provides a widget for Node Reference which displays the node teasers instead of a select box, and allows choosing the referenced nodes
from a Modal panel. The list is optionally sortable, depending on JQuery UI Sortables. The modal supports pagination, exposed filters
and exposed sorting, all using AJAX.
Bricks — is a revolutionary new way of creating rich content in Drupal. Thanks to the powerful contributions like ECK and Entity Reference, Bricks itself is just ~13 KB of code (gzipped).
In terms of concept Bricks is a new generation of Paragraphs, drop-in replacement for Panelizer and a good friend to Display Suite and CKEditor or any other WYSIWYG. Shortly, it allows you to nest field items using Drupal drag & drop UI (exactly like for menu or taxonomy items).
This is a set of modules, which provide input elements for endusers with the power of cck.
This module hosts a set of fields to be used by the Content Construction Kit. Fields are used to create various content types. They appear as input fields when creating or editing a node. They are rendered to text, when shown to page visitors.
The difference for CCK Inputs is, that they are rendered as input elements to the visitor. This way you can build a webform using CCK.
CCK Input Elements do not provide any means to evaluate or store the data which users send back to your site, when hitting "submit".
This module serves one purpose, it provides a Bundle Name Reference field type.
As a developer you would like to promote flexibility in your website and empower content editors. You would like editors to be able to custom create content listings on the fly.E.g a page showing all articles and ebulletins.
If you were to use views page or similar quite often the user has no power over meta information, nor the ability to choose the URL etc.
This module features:
1. Drupal 6 only, as drupal 6 has updated jquery, there's no need to
depend on the jquery_update module.
2. Providing a jcarousel block which can be managed throught the
3. No need to write any HTML or including any JS. If the block shows on
a node page, it reads the images from the node (CCK required).
4. Images are loaded through configurable cck image field. Currently
only supports imceimage and imagefield.
5. lightbox support by default
Alfresco module provides integration between Drupal and Alfresco Enterprise Content Management System. Alfresco is a Open Source content management platform for documents, web, records, images, and collaborative content development.
This module helps you build Drupal websites using the Alfresco's Document Management repository to store and share the documents.
A compound field with a text field and paired integer field.
There is now also a submodule called textintegerfieldx2url -- that's two text fields, two integer fields, and a URL field. This is unlikely to fit your exact needs but it is another example you can copy for making compound fields.
The Video Upload module provides a CCK field type that allows for the end user to upload video directly to YouTube, using a single account for the site.
Video Upload and Drupal 7
You are encouraged to use the Media and Media:YouTube modules to replicate the functionality that this module has historically provided.
If you are interested in maintaining this module as an alternative to the Media module in Drupal 7, please contact me.
The video never hits the Drupal host (for the 5.x and 6.x-2.x versions only—see the 6.x version below for details on the difference between browser and direct upload methods), saving on storage and bandwidth bottlenecks. Furthermore, the end-user doesn't need a YouTube account, since all video is stored under the site's account. Video can be organized on YouTube with customized developer tags, currently with limited token support.