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.
Field Defaults allows batch updating of default field values to existing content. When adding a new field to an entity you can update all existing content with the default value or when editing an existing field you can choose to also update all existing content with the new value.
All existing content is overwritten with the new value.
This is a light weight module that provides an Internet Sources field (i.e. emfield in its 6.x branch) formatter. It helps you turn any link or text field to a media field with rich features (thumbnail or full player in any size) and without a heavy module.
Currently supported: YouTube, Vimeo, Dailymotion...
Semantic CCK was created to give users the means of customizing the HTML output of CCK fields. It was inspired in part by the highly recommended module Semantic Views which provides the same functionality for Views.
A Drupal 7 version of Semantic CCK is currently under development: Semantic Fields.
This module contains Embedded Video Field providers (i.e. emfield's emvideo 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). The hope for this project is that it will eventually be phased out as new maintainers step up and take ownership of individual provider integrations, but I wanted to make sure that current users of these providers can still use them with Emfield 6.x-2.x (assuming they're even working). This module's issue queue should also be used for any issues regarding the currently included providers.
Current providers include:
Custom URL (for embedding video files directly)
Get involved! Maintaining a Media Provider file is a great way to get started with Drupal module development/maintenance, so if you're looking for a way to get a foot in the door, take a look at the currently included provider files and start your own "Media: " project to house it (you could also help out with a current provider or create a new one)! If you're interested in taking over a provider file, please open an issue in this issue's queue.
This module creates a CCK field that accepts RSS urls.
- Aggregates RSS/Atom feeds
- Controls item display count and frequency of updates
- Feed Fields may be positioned just like any CCK fields
- Feed Fields may accept multiple values (deltas)
- Feed Field-enabled nodes may be used in Blocks and Nodeblocks
- Works with FlexiField
- Feeds are automatically updated by cron
- Test Page simulates cron without changing any data
D7 Note Currently, what with how Drupal 7's fields are written in a way so you can't really tell how to get at the data, and with Corresponding Node Reference already having a successful D7 port, there are no plans to update Backreference to Drupal 7. If you plan to upgrade, I suggest changing your Drupal 6 site to use Corresponding Node Reference, and then update.
Backreference Module provides a nodeapi interface to maintain 1-1 relationships between all shared instances of a nodereference field. This means that given a field instance of field_reference1, if you add a reference to NodeBeta to NodeAlpha's field_reference1 and NodeBeta has an instance of field_reference1, then NodeAlpha will be added to NodeBeta's instance of field_reference1.
There are other similar modules out there that do similar work, such as NodeReferrer and Node Relationships. In their cases they use views or similar queries to query for the nodes that are pointing to module B, where BR writes to a CCK Nodereference field. This has some advantages:
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.
This module contains Embedded Image Field providers (i.e. emfield's emimage 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 a method to enforce referential integrity rules for CCK user and node reference fields. In other words, it allows you to decide what to do with reference values when a referenced entity (node or user) is deleted.
CCK node and user reference fields may contain values that point to nodes or users that have been removed. CCK does nothing when a node or user is removed with the values of fields that reference them. So after some time, your node and user reference fields may contain records that point to nowhere. Orphans.
Extension for reference fields:
Once the module has been installed, the user and node reference field settings form will provide a new option "Referential integrity behavior".
Available options are:
Set NULL (Set the value of this field to NULL when referenced users/nodes are deleted).
Monitoring orphan records:
You can also review all your reference fields to monitor if they have orphan records from Administer -> Content management -> Content -> Orphan references.
This report displays the total number of records in the tables used for each reference field, and also the number of orphan records found, if any.
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
This module allows site administrators to add additional HTML attributes to the wrapping markup on any field in the Manage Display settings page.
The field formatter attributes settings are found in the Manage display tab for content types, users, and other entities. A options element is available for each field formatter, revealed by using the formatter settings edit button (Gear wheel icon) for that field.
Why use this module?
This module is good if - for example - you need a quick & dirty way of adding schema.org microdata attributes to fields. A better solution to this problem is found in the Microdata module, but most field formatters are not yet supported. *edit: An even better solution to this problem is the Schema.org module which, while not technically supporting the recommended microdata format on schema.org, uses RDFa 1.0 which all the search engines support nicely.
This module allows you to specify content type(s), users, or any other type of entity as being a block. This allows the content managers of the site to edit the block text and title without having to access the block administration page. Users only need edit access to that entity in order to edit it.
This module simply export nodes into word file (by formatted html) using VBO to bulk export. This module also borrow some function of print module, so which field would like to export can adjust at cck print display page.
This module allows administrators to rearrange the order of (cck) fields for node displays.
Normally the order of CCK fields is similar in both the node edit form as in the node's view. If you'd like to have an other order in, let's say the teaser display of a content type, this module provides you an user interface for this specific task.
Each context (Basic, RSS, Search, etc.) and each build mode (Teaser, Full, etc.) can have it's own field order.