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.
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.
Provides an additional CCK widget type for the base field node reference. The auto-create widget type provides a text-field for input of the node title like standard node reference fields, but instead of linking to existing nodes it creates a node with the specified title on save. When the title is changed during subsequent node saves the referenced node title is changed as well.
A CCK content field which lets you add a country to your content types; displaying country name, ISO 3166-1 alpha-2 code, ISO 3166-1 alpha-3 code or a countryicon with module Country Icons (6.x-1.0-beta2 and newer releases now supports Country Icons 1.x and 2.x).
Allows fields on the node referenced by a node reference auto-create field to be viewed and edited. In other words a node reference is created to a particular node which has additional cck fields. The additional fields can also be edited along side the node title provided by node reference.
The 'FileField Sources Scald' module allows drag and drop from Scald into a file or image field. If building a site from scratch, we highly recommend using the Scald Atom Reference sub-module, included with Scald. However, in some cases, you may need to continue using an existing File, Video or Image field and would like to add Scald drag and drop functionality without adding a new field.
Used for rename a CCK field-name. This help user retain any widget settings. Now users not only able to rename a content-type but also CCK field. If you use CCK very intensive then this module for you.
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.
This module allows site administrators to override the Field Label on any field in the Manage Display settings page. This allows each field to have a different title in different view modes.
The field formatter label settings are found in the Manage display tab for content types, users, and other entities. A text box is available for each field's label, revealed by using the formatter settings edit button (Gear wheel icon) for that field. If no 'Label override' is specified then the default will be used.
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.
Allows textfield to be rendered like a node reference, with some autocompletion magic on edits.
A university department wants to list the authors on their publications' page. Any given publication may have several authors, both from the department and outsiders, with their order being important (ie. it is quite likely to have an 'employee-outsider-employee-outsider' like order.) If an author is an employee of the department, his/her name should be displayed as a link to his/her own profile page, while outsiders' name should be displayed as clear text. There are several use cases with high probability here:
It is quite likely to have an author order like 'employee-outsider-employee-outsider'.
It is quite likely that a now-outsider author becomes an employee later on, in which case his/her name should automatically converted to a link to his/her profile without any changes to the publication.
It is quite likely that the site editor wants to enter existing authors' names without typos, regardless of that they are employees or not.
So what does this module do then, anyway?
Let's switch to Drupal tongue. :) Want to have a nodereference-like link to a node that does not exist yet? Want to have autocompletion both on existing field values and on existing node titles of other content types? Install and enable this text_noderef.module, and all your problems fly away!
This module allows users to mark administrator selected CCK fields as Public (visible to everyone), Hidden (visible to node author, hidden from everyone else) or Private (visible to node author and "friends"; see requirements section below).
The field settings screen provides a new option to enable privacy options for fields. This option is global and affects all content types where the given field is shared. The default privacy status can be specified.
This module supports all kind of fields, and even fields in multigroups.
In the node edit form, a new option to configure field privacy settings will be available as a small icon next to the fields where this feature has been enabled. This is only available to users with "edit privacy options for field %field_name" permission.
Users with "view private data for field %field_name" permission are excluded from privacy restrictions. This feature combined with node revisions allows community managers and/or site moderators to monitor changes to privacy settings.
Builtin support for node revisions and Diff module.
To enable the "Private" status for fields, you need one of the following modules: Flag Friend, Friendlist API, User Relationships. CCK Private Fields module includes ready to install mini-modules that provide builtin support for any of these friendship related modules.
The privacy options dialog requires jQuery UI (either version 1.6.x or 1.7.x).
A simple module that tracks downloads of files added through CCK/Fields by asking anonymous users to enter their email address. Returning anonymous users are tracked using a cookie. A tracking interface shows email address and user account information for tracked files downloaded on the site.
Why only have users enter their email address? Email addresses are a unique and easy way to identify users, and the barrier for entry is lower than actually registering for the site.
This module connects Drupal with the FusionCharts Free and FusionCharts v3 (commercial) package. FusionCharts is a flash charting and graphing component that can be used to render data-driven & animated charts for your web applications and presentations.
This module provides both a user interface for creating charts as well as as an API for developers to integrate with other modules.
What's included in this module:
A content type with an graphical user interface for creating charts
A CCK field
An API that to create charts using SQL queries
An API that to create charts using an array of data
An API that allows for drill-down viewing of data (you can click on the bars to fetch new data)
Examples of how this module can be integrated with other parts of Drupal
The goal of the Eventbrite Drupal module is to enable deep integration with the Eventbrite API as a base module, allowing for seamless connections between Eventbrite and Drupal data around users, events, and more.
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 API exposes the so called driven properties, which are aimed to map any type of node properties (i.e. title, body, taxonomy, CCK fields, workflow, etc).
What such driven properties are used for depends on the modules taking advantage of them.
Taxonomy Orderable Tags adds an autocomplete widget for taxonomy term reference fields that creates a textfield for each entered tag and allows to re-order them by using tabledrag multifield functionality
This module is useful if the order of terms attached to a node is essential and autocomplete / free tagging is required