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.
Taxonomy Orderable Tags adds an autocomplete widget for taxonomy term reference fields that creates a textfield for each entered tag and allows to re-order them by using tabledrag multifield functionality
This module is useful if the order of terms attached to a node is essential and autocomplete / free tagging is required
This module allows views to be used as formatters for CCK node and user reference fields. This means that instead of just a title, teaser, or full node, you can show nodes using any fields that are available to Views, in any sort order, in any view style, with any views theming.
This module is version 2 of Node reference views, reworked to provide multiple formatters, and for user references as well as node references (hence the change in name).
A simple module that tracks downloads of files added through CCK/Fields by asking anonymous users to enter their email address. Returning anonymous users are tracked using a cookie. A tracking interface shows email address and user account information for tracked files downloaded on the site.
Why only have users enter their email address? Email addresses are a unique and easy way to identify users, and the barrier for entry is lower than actually registering for the site.
Allows fields on the node referenced by a node reference auto-create field to be viewed and edited. In other words a node reference is created to a particular node which has additional cck fields. The additional fields can also be edited along side the node title provided by node reference.
The goal of the Eventbrite Drupal module is to enable deep integration with the Eventbrite API as a base module, allowing for seamless connections between Eventbrite and Drupal data around users, events, and more.
This module allows users to mark administrator selected CCK fields as Public (visible to everyone), Hidden (visible to node author, hidden from everyone else) or Private (visible to node author and "friends"; see requirements section below).
The field settings screen provides a new option to enable privacy options for fields. This option is global and affects all content types where the given field is shared. The default privacy status can be specified.
This module supports all kind of fields, and even fields in multigroups.
In the node edit form, a new option to configure field privacy settings will be available as a small icon next to the fields where this feature has been enabled. This is only available to users with "edit privacy options for field %field_name" permission.
Users with "view private data for field %field_name" permission are excluded from privacy restrictions. This feature combined with node revisions allows community managers and/or site moderators to monitor changes to privacy settings.
Builtin support for node revisions and Diff module.
To enable the "Private" status for fields, you need one of the following modules: Flag Friend, Friendlist API, User Relationships. CCK Private Fields module includes ready to install mini-modules that provide builtin support for any of these friendship related modules.
The privacy options dialog requires jQuery UI (either version 1.6.x or 1.7.x).
This module allows you to specify content type(s), users, or any other type of entity as being a block. This allows the content managers of the site to edit the block text and title without having to access the block administration page. Users only need edit access to that entity in order to edit it.
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.
Used for rename a CCK field-name. This help user retain any widget settings. Now users not only able to rename a content-type but also CCK field. If you use CCK very intensive then this module for you.
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
This module connects Drupal with the FusionCharts Free and FusionCharts v3 (commercial) package. FusionCharts is a flash charting and graphing component that can be used to render data-driven & animated charts for your web applications and presentations.
This module provides both a user interface for creating charts as well as as an API for developers to integrate with other modules.
What's included in this module:
A content type with an graphical user interface for creating charts
A CCK field
An API that to create charts using SQL queries
An API that to create charts using an array of data
An API that allows for drill-down viewing of data (you can click on the bars to fetch new data)
Examples of how this module can be integrated with other parts of Drupal
A CCK content field which lets you add a country to your content types; displaying country name, ISO 3166-1 alpha-2 code, ISO 3166-1 alpha-3 code or a countryicon with module Country Icons (6.x-1.0-beta2 and newer releases now supports Country Icons 1.x and 2.x).