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 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).
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'.
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.
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.
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.
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 extends File and Image fields by adding ability to upload files from third-party services such as Dropbox, Box, OneDrive, Google Drive and Instagram. The module's built-in plugin API allows developers extend functionality of the module by integrating other service providers.
The module respects Drupal field settings such as file size limit, extensions, cardinality.
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.
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.
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.
If you have a product that has multiple attributes, but dont wish to create a separate field for each of these, you can use Attributes. In the field, it has an Attribute (Size, Colour, Distance, anything) and a Value (8, Red, 21km, etc).
As it uses CCK Text Fields, its Views Integrated and has two filters: Attributes & Values.
This is not an official module, and we have no affiliation with Vimeo.com.
Don't confuse your end users by asking them to paste embed codes or URLs into your website. Instead let them browse the videos visually and insert which ones they want by clicking on them. Now that's easy!
This module enables to associate nodes according to different criteria such as Taxonomy and CCK fields.
You can give a different weight for each criterion. All criteria will be aggregated by the main module which compute a matching score for each couple of nodes. Then, for a given node, you can get the other nodes that are associated to it. The associated nodes are ordered by the matching score they have with the given node.
Different associations can be defined with their own criteria and weight.
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.