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.
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 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:
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'.
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 module allows for certain user roles to be exempt from required fields. This is mainly useful to those on the back-end of a website do not necessarily need to fill all of the fields to submit a node.
When you are setting up the field you have the option to set certain role to be exempt from the required. When that user role comes to add or edit that node, the field will not be required for 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.
Link Intelligence (LI) provides multiple methods to facilitate automated and manual linking of related web page content. It is designed with easy plug-and-play defaults for simple install and forget auto-linking, yet is highly configurable to enable advanced linking strategies.
It supports both standard styles of related content linking; transforming keywords in node content into links (content linking) and/or adding links to sidebar lists (displayed via CCK and/or Views). It can generate either style of link automatically or provide suggestions for content authors to quickly find and embed links to relevant content themselves.
Wiki / glossary - LI can auto link in-content keywords to definitions, wiki pages or other keyword related content.
Related content – LI builds sidebar style links to related content. You can either auto populate the list of links or use the suggestions search and add link feature to quickly and easily build your own list.
Search engine optimization (SEO) - LI can interlink content with a blend of in content and sidebar links to re-enforce important keywords on your website.
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 provides support for international banking standards and identifiers such as BIC (ISO 9362) and IBAN (ISO 13616).
Current features include CCK field types for BIC and IBAN identifiers, as well as an API to parse and validate those identifiers (with specific IBAN support for 52 countries, up to date as of Release 13 of the ISO 13616 IBAN Registry).
This module provides a function to check new content which may be similar or equal to other nodes. This does integrate with cck and uses phonem to make sound check on strings to detect "drupal" and "trupal" as equal field content. You can set the fields that are used too check if the node is unique or if it already exists in admin setting area. The module lets you choose which compare method you would like
to use, equality or phonemic sound check (with phonem 'drupal' is equal to 'trupal' because it sounds similar).
Just place the module into your sites module folder, in most cases /sites/all/modules, and enable it on the admin module page /admin/build/modules.
Configuration and usage
Go to your content-type in drupals adminsettings and go to the settings of the field you want to use to check if a node is unique. You can select as many fields as you want. For example if you have a content type 'person' with fields 'firstname', 'lastname', 'birthday', firstname and lastname could be checked for equality to decide if a node that represents the person already exists. To get this done, go to the edit page of the field 'firstname' and select an option in the fieldset 'unique content' at the bottom of the page.
You have 3 options and one checkbox:
This module has not been ported to Drupal 8. Refer to this issue to find out its progress.