The aim of this module is to greatly reduce the load to the site's database by using "virtualized" fields instead of "real" FAPI fields.
This module is just a formatter (display) of textfield, text area and text format. The idea behind this is to provide a simple solution, easy to setup, with few dependencies to display text on website.
The trim function in this module is taken from Views module with a few modifications.
- Text (Drupal 7.x Core)
- Filter (Drupal 7.x Core)
Download the module and simply copy it into your contributed modules folder:Read more
This modules provides an api and set of tools for creating flexible content types, taxonomy terms, and their respective fields and field groups. Although the base functionality is similar to what is offered by Features, these tools are entirely maintained in simple to create/edit/update yaml files with only as much information as is needed; there is no need to alter fields or content types in the UI and then recompile; just alter or add a setting in the code, rebuild the content type or taxonomy vocabulary, and you're done. When utilized to it's fullest potential, this module provides a code-based alternative to the Field UI.
This module allows site administrators to override the Field Label on any field in the Manage Display settings page. This allows each field to have a different title in different view modes.
The field formatter label settings are found in the Manage display tab for content types, users, and other entities. A text box is available for each field's label, revealed by using the formatter settings edit button (Gear wheel icon) for that field. If no 'Label override' is specified then the default will be used.
- Field formatter settings: Provides the low-level API needed to alter formatter's settings forms.
This module is almost identical to the Field Display Label module, the sole difference being that the label can be overridden in the Manage Display UI (rather than on the field configuration screen).
This module should work just fine with the Field Display Label module in the way you expect. If it is enabled the following logic dictates what a field's label will be:
1. Use the Field Formatter Label override, if it is not specified then:
2. Use the Field Display Label override, if it is not specified then:
3. Use the Field label (as per Drupal core behaviour).
The content of multigroup fields created with CCK are stored in tables in the database which use the the node version id (vid) and delta (the position within a set of fields that a field occurs) in order to reference them. Unfortunately, as delta can change - i.e. if a node is edited and the order of the fields is changed - you cannot use these tables to reliably reference a particular piece of content stored within a field on a node.
At least one module exists to reference fields which aren't in multigroups (the serial module), however I could not find any which are able to track the content of fields stored in a multigroup.
This module creates unique IDs for non-grouped, standard grouped and multigroup CCK fields. It includes a function which you can use to obtain a reference for a CCK field from its node nid, node vid, the name of the CCK table (content_field...) and its delta.
This has been built for Drupal 6 - I don't know whether the issue that this project is addressing also applies to Drupal 7.
Part of the Commtap project.