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.
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.
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.
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).
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.
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.
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.
This module allows you to fill title, body, and CCK fields from the URL. It auto-populates a field with a value from the URL. There are options to allow / disallow overriding pre-existing values, hiding a field if it is filled from the URL, and a few other goodies.
It supports both single and multi-value fields. It has support for the following field types:
Field inspector provides an administrative user interface for the Field Info API. This allows users to select what information, formatting, and fields they would like to see, and provides output in a manner that can be copied into a module, or install profile into a hook_install, or hook_update_N function. This functionality is similar to the Content Copy module provided in 6.x and earlier versions of the CCK package.
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.
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 module turns the nodereference widget into a modal popup allowing new linked nodes to be created on the fly. Because it uses an iframe, it should support even Javscript and file uploads within the sub-node.
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'.
Sometimes you want to be able to give simple URL access to content that would not normally be available to a particular user (or perhaps someone not even registered with the site).
Deep link module allows the direct access to a specific item of content under certain circumstances and limitations. Such as one-off or time-limited deeplinks.
The deeplink module provides a framework for generating special URLs which can be inserted into emails that allow access to a content item or page, and tracks the uses of that link.
The controls that go with deeplink provide the means by which users are selected, one allows selection by user - so only users will receive the deeplink and only those users will be able to use it; and by email: this allows you to enter a set of email addresses that will be sent the deeplink URL. Obviously this one is more limited in that unregistered users can look at the content.
Other controls, for example to select by role, could be built.