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).
Extends Field group with an option for a Popup field group. This will render a link which, when clicked, shows all of its children in a simple position: fixed popup.
This module does not mess around with the structure of the form or the DOM particularly. Rather the children of the group are surrounded in a <div>, which is then styled as a very simple position-fixed popup.
A button is then rendered on the form which toggles the popup open/closed. The label of the button is configurable.
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 module allows Views to set build modes for row objects depending on an active context. When should you use this module?
If you need to create a view which depending on the users' properties (permissions, roles,...) does or doesn't show certain 'limited access' fields of a row object. This allows you to do away with the restrictive, clunky CCK field permission system.
If you need to show a view on diverse sections of your site and you don't want to create a gazillion display variants. This promotes reuse of views displays.
1. Install/Enable the module
2. Go to admin > build > context and create a new context
3. Add conditions to your new context
4. Add the VCD Reaction plugin as a single reaction to your context.
5. Go to admin > build > views
6. Create a new view or edit an existing view
7. Choose 'VCD Object' as the active Row Style plugin and edit its' options
8. Expand the Contextual build modes tab
9. You'll see all the contexts which have the VCD Reaction plugin set
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 is the HTML5 Canvas field module, which allows you to capture manual "drawing" input directly in the browser. It's main component is a FieldAPI Widget for the image field, meaning you can display captured images the same way you would any image field. Some suggested uses are marked-up screenshots and signature capture.
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.
This CCK field allows a filtering of the selectable terms for a matching vocabulary displayed in the taxonomy select combo box in a node create/edit form. This allows a single vocabulary to be used across a number of node types. It is used to restrict the terms associated with a node type. Subsets can be overlapping. A single selection will force that term to be associated with the node type and the selection will not be displayed. Typically the term will be the node type's name.
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.
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.
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.
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'.