Content Construction Kit (CCK)

The idea behind this module is to create a clean version of the node form.
This is useful in the cases where we would like to use the node form
as a simple and clean form for user input showing only necessary fields
and no extraneous fields that only complicate the end user experience.

This module is compatible the CCK module. Thus, it provides
the same breadth of field types available to the CCK module.

All forms submitted via this module create a node of the same type as the
node form used to create the form.

Adds support for Embedded Media Field to use Animoto.com as a content provider.

The module provides a select list with optgroups for taxonomy terms selection.

The way how the module implements optgroups depends on Drupal version.

This module will allow you to exclude users from a node using the user reference CCK field.

This module allows Views to set build modes for row objects depending on an active context. When should you use this module?

This module defines a twitter field widget for CCK and handles posting the contents of the field that uses the widget to a Twitter account.

This module satisfies the need of those looking to post statuses to a single shared Twitter account as describe in #412118: Proposal for a New "Twitter Shared Accounts" Module by @Shai.

This module will use the user reference CCK field to exclude users from viewing a specific node.

The Nodereference Widget Thumbnail module provides a configurable way to associate an
image from a cck imagefield to be used as a thumbnail for a nodereference autocomplete
widget on the referencing node's edit form. The addition of the thumbnail for the nodereference field is an excellent content author usability enhancement when using the nodereference field to reference nodes with imagefields.

Node CSS uses node fields to populate a CSS template file. CSS for all nodes can either be aggregated into a single file or generated per node. In both modes, the CSS files are added using drupal_add_css() so it complies with full Drupal aggregation and compression. If aggregation is turned on in Node CSS it is recommended to make the CSS node specific via a body node class because the same CSS file is loaded for multiple nodes. Many themes output a node specific class by default.

The problem

The Computed Field module only updates its computed values on saves or on load (if no computed value is computed yet). This is not optimal when using computed values in lists etc., or if you should wish to change the logic in the computed field.

The solution

If you wish to avoid re-saving all the entities/nodes using the computing field, you can use this tool to re-compute all the values again.

The computed field tools module offers a way to re-compute the computed fields of existing entities/nodes. It does so through the Batch API.