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 adds 3 autocomplete widgets for CCK fields of type Text and Number.
Autocomplete for allowed values list: This widget can be used for Text and Number fields and it takes candidate values from the defined list of Allowed values of the fields. You can even generate your allowed values list using PHP, so the limit to provide a widget with autocomplete features is your imagination!
Autocomplete for existing field data: This widget can be used for Text only and it takes candidate values from existing values in the database for that field.
(7.x only) Autocomplete for predefined suggestions: This widget can be used for Text only and allows an admin to provide a list of suggestions but still allows users to enter anything they want in a text field. Use this widget to help avoid (but not prevent) variations of the same value. Ex: burger, hamburger, Burger ...
(7.x only) Autocomplete for existing field data and some node titles: This widget works just like the "existing field data" widget above except it will also suggest node titles for nodes of a specific content type(s).
All widgets allow you to choose the size of the text element and the method used to match values between 'Starts with' and 'Contains'. You can also enable case sensitive or insensitive matches option. Note however that MySQL may ignore case sensitivity depending on the collation used in your database definition.
When the Internationalization module is enabled, the 'Autocomplete for existing field data' widget also provides an option to filter values by the language assigned to their corresponding nodes. This option allows you to provide a different set of allowed values per language.
the Grid Field Formatter module provides a simple way to overridde the display of multi-value fields to show as a grid/table with a certain number of columns.
This module has no pretention of implementing any field: it is not a Table field, such as TableField, or CCK Table Field.
It's just a formatter (display) to render multi-value fields with a grid/table layout instead of a list of items.
The idea behind this is to provide a simple solution, easy to use, setup, with few dependencies and trying to leverage the formatter hooks provided by #945524: Field formatter settings hooks in core to extend existing field formatters.
#D8CX: I pledge that Advanced Text Formatter will have a full Drupal 8 release on the day that Drupal 8 is released.
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.
Of course, this module is fully compatible with any modules that use entity formatters, such as Views or Panels
New development is done in the http://drupal.org/project/cer module. This expands the corresponding node reference functionality to enitities. Please focus all attention on getting a stable release of cer as soon as possible.
Cnr is looking for a comaintainer to resolve the remaining bugs. No new features will be handled.
It syncs the node reference between two node types which have a nodereference to each other, so double editing nodes is no more needed. If one node has a reference the other node receives also a reference to the saved node if it is referenced in that node.
Release 6.x-4.0 doesnt require setting the options to unlimited, all is handled by cck now. The old setting to allow setting to single is no longer present since it is obsolete. To upgrade, run update.php and manualy set the allowed references on each nodereference instance. The older branches are not supported anymore so you should upgrade.
6.x : CCK
Node reference (comes with cck)
7.x: Node reference (included in References)
Feeds Image Grabber (FIG) is successor of FeedAPI ImageGrabber, an addon for Feeds module, which grabs image for each feed-item from their respective webpages and maps it to an image field in the node created by Feeds (Node Processor).
[Google Reader (with thumbnails) can be imitated on a Drupal site by using Feeds, Feeds Image Grabber, FileField, ImageField, ImageCache, ImageAPI, Views and Voting API module (http://goo.gl/J5MJg)]
Automatically downloads and attaches image to the node created by Feeds module.
Configurable XPath of the desired image location on the webpage of the feed item on per feed basis (using element's id or CSS class).
Select2 - The jQuery replacement for select boxes now available for Drupal fields.
This module provides a new Field widget for Entityreference and Term reference fields. It is based on the Select2 jQuery library: http://ivaynberg.github.io/select2/
This module integrated this library with the Drupal Field API, and provides a new type of widget.
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.
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.
When the batch is running it does not save the entire entity/node, but it only saves the computed field. This make it a fast way of updating the content.
Fast processing of all computed fields.
Select specific computed_field to process.
Select content types to process for selected computed field.
It processes ALL entities/nodes. Also the ones with no value computed yet.
Since we don't do an entity_save() we don't clear the cache on every(!) node processing and no search index updates are triggered, so there is a huge performance advantage here on high traffic sites over the VBO way.
NodeReferrer provides a counter part to CCK's nodereference field. The options for a NodeReferrer field allow you to select content types and field instances to match when creating back reference lists.
Adds a button field type for use with any fieldable entity type and Rules. Provides two different widgets: HTML Button and Image Button. Adds a new button click event, clicked button comparison, and reload page action for use with rules. When the button is clicked, an AJAX call is used to run the event. Using rules you could display a message to the user, alter some data on the entity (or another entity) and reload the current (or any other) page.
This module aims to provide the ability to edit File entities inline, as part of another form (such as nodes). This should enable the ability for reusable and site-wide editing of file properties, such as description, alt text, captions, bylines, etc.
Multi edit/delete/clone/export (checkboxes will be displayed in the rows - select as many rows as you want to perform action against)*
* Drupal 7 version only.
At the front end, users can show/hide, resize, reorder columns & resize the height of the grid. These settings will be stored per user and used next time the grid is shown. Saving the view (via the usual views UI) will reset these settings.
This is a CCK (Drupal 6) / Field API (Drupal 7) field type that will count the number of nodereferences to a particular node. The count is updated both when the node that is being counted is saved, as well as when a node that is referencing the node being counted is saved, updated or deleted. It will count references from individual nodereference fields as well as aggregate counts from multiple nodereference fields to the same node.
The Node Relationships module provides methods to complete two way relationships between content types enhancing the features of node reference fields.
It provides the following features:
Enhancements for node reference fields: "View reference in new window", "Edit reference" (in modal frame, updates widget if node title changes), "Search and reference view" (single and multiple selection based on dynamically configured views), "Create and reference" and "Translate and reference" (when the Drupal core translation module is enabled, with additional support for Internationalization module). These features use the Modal Frame API to provide popup dialogs from buttons attached to node reference fields configured to use the autocomplete widget.
Automatic back references using dynamically configured views that are able to extract the relations from existing database information. This views can be rendered using a myriad of methods in the node view.
The Node Relationships module provides default views for each feature that can be modified and/or cloned (recommended) should you need to add more fields, filters or change any other option to suit your needs.
Basic entity relations diagram (ERD) that can be used to view the relations of each individual content type. The provided diagram can be used to walk the relationships of all types in the system.
It's often useful to provide two versions of a given string: one that's intended for human viewing and another that's intended for use in database queries, URLs, and so on.
In Drupal, this is generally known as a 'Name' and 'Machine name' pair. Drupal 7 even provides a prefab FormAPI element to simplify the process of entering these matched pairs.
Safeword exposes a custom FieldAPI field type that stores two strings using the name/machine name approach. It can be useful when generating PathAuto aliases, exposing Views arguments, and so on.
One common use is to not give users permission to 'Create and edit URL aliases' and instead give them access to a Safeword field which uses the node title as it's source. So that users can only edit a limited part of the path, keeping safe the other parts that your site features may rely on.
This module provides a "colorpicker" form element for CCK forms, and also for module developers to utilize. A colorpicker field is a textfield with a colorpicker button that brings up the Farbastic color widget that comes included with Drupal. (Support for additional third-party color pickers is planned.)
To use this module, simply enable it. Colorpicker-aware modules will then display a colorpicker field instead of a plain textfield where appropriate. And as a site creator making new content types, you now have a CCK colorpicker field at your disposal.
Multistep adds multiple-step functionality to content type editing forms. It does so by assigning a step number to each fieldgroup within the content type and hiding all the groups that do not belong to the current step. The user can then use different submitting buttons that will redirect to the previous, next, or current step.
The form element for amount is reused from the Formatted Number CCK module. Decimal points and thousands separators are formatted using the Format Number API module, where these options are configured from site and/or user settings.