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 module allows site administrators to add additional HTML attributes to the wrapping markup on any field in the Manage Display settings page.
The field formatter attributes settings are found in the Manage display tab for content types, users, and other entities. A options element is available for each field formatter, revealed by using the formatter settings edit button (Gear wheel icon) for that field.
Why use this module?
This module is good if - for example - you need a quick & dirty way of adding schema.org microdata attributes to fields. A better solution to this problem is found in the Microdata module, but most field formatters are not yet supported. *edit: An even better solution to this problem is the Schema.org module which, while not technically supporting the recommended microdata format on schema.org, uses RDFa 1.0 which all the search engines support nicely.
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.
Field Defaults allows batch updating of default field values to existing content. When adding a new field to an entity you can update all existing content with the default value or when editing an existing field you can choose to also update all existing content with the new value.
This module features:
1. Drupal 6 only, as drupal 6 has updated jquery, there's no need to
depend on the jquery_update module.
2. Providing a jcarousel block which can be managed throught the
3. No need to write any HTML or including any JS. If the block shows on
a node page, it reads the images from the node (CCK required).
4. Images are loaded through configurable cck image field. Currently
only supports imceimage and imagefield.
5. lightbox support by default
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).
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.
This is a set of modules, which provide input elements for endusers with the power of cck.
This module hosts a set of fields to be used by the Content Construction Kit. Fields are used to create various content types. They appear as input fields when creating or editing a node. They are rendered to text, when shown to page visitors.
The difference for CCK Inputs is, that they are rendered as input elements to the visitor. This way you can build a webform using CCK.
CCK Input Elements do not provide any means to evaluate or store the data which users send back to your site, when hitting "submit".
When editing CCK fields, the selector is built with the types where the field really exists. This behavior has the nice effect that you can quickly check if the field being edited is shared by simple inspection of the selector options, and it offers a quick method to switch from one type to another to compare the instance related settings of the field on different content types.
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).
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 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 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 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