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 No Colons module allows you to remove colons from form labels and other types of label text. There are two modes of operation: Remove all colons -or- Remove colons only if label text ends in punctuation (such as a question mark).
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).
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.
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.
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.
The Wysiwyg ImageField module is an inline image management tool for the Wysiwyg module based on the ImageField and Insert modules with an IMCE-esque image library provided by the FileField Sources and Views modules.
Wysiwyg ImageField is currently being re-written as Wysiwyg Fields, which will allow for any CCK field to be used inside the Wysiwyg.
Checkout a quick demonstration of the early module at http://youtu.be/-CYGPCCzWYo
This package is a collection of add-on formatters for various CCK fields. Each provided sub-module in this package should be a self-contained single formatter.
CCK fields support an arbitrary number of "formatters", swappable code that renders a field. In Drupal 6 these are essentially theme functions, although in Drupal 5 they are not always. It is possible for any module to define new formatters for field types it doesn't define itself, which creates a very powerful way to extend and theme a field in any of the myriad ways that a field can appear.
This module is an "incubator" for new field formatters. Because each formatter may have its own development cycle, there will probably not be stable releases of the entire suite. If a specific formatter gets particularly popular or requires a more full-featured release cycle, it should likely be spun off to its own project.
This suite is maintained by Palantir.net. If you want to submit another formatter module to be included, please contact Larry Garfield. If you maintain a CCK field and want to fold one of these formatters into the field module itself, contact the appropriate module author (or Larry if you aren't sure who that is).
Allows administrators to clone CCK fields.
After enabling this module you'll be able to clone a field by accessing it's settings page (at admin/content/node-type/[node-type]/fields/[field-name]) and clicking on the "Clone field" link at the bottom of the page.
The 2.3 version for D6 works with the following field types (all select widgets):
Number (integer, float, decimal)
This module can be used for a few different reasons:
1. You are using a reference field such as node_reference, user_reference, or role_reference and have options that you'd like to trim out of the list, but don't want to write a custom module to form alter out those options or use the views feature for populating the list.
I'm looking for a co-maintainer for this module – in particular in order to port it to Drupal 7.
The Array Tokens module allows you to use all values in multiple-value CCK fields and multiple-value taxonomy terms in a single token. It also allows you to define your own settings for how items should be merged ("merge styles").
The output of each item is either plain text (for taxonomy terms) or the default CCK rendered output (for CCK fields). However, a few special formats are provided for file fields, node references and user references.
Module adds 'view own content' and 'view any content' permissions for all of content types.
So, administrator can build a more flexible system of rights.
For example, admin can add 'view own question content' for role 'clients' and 'view any question content' permissions for support engineer so, clients can see only own questions and technical support engineer can see all questions from all clients.
NEW! If you using CCK, you can check new feature 'view content via field_reference'.