The default implementation for ordering fields in Drupal stores weights together with the field instance. This works well as long as you know that there is only one canonical source for these weights, but in reality this might not be true. Consider the following situation:
This module is about the simplest way to get a Google Map, and/or a link to a Google Map, displayed with your content. It provides a field formatter for Drupal plain text fields (it can also be used on Computed Fields module fields). You enter an address that Google Maps can recognize in the field, and the formatter displays it as a dynamic map, a static map (without the ability to zoom/pan etc.), a link to Google Maps, or some combination.
FileField Sources Plupload lets you add Plupload (a multiple files/multifile upload widget) as a source to any file field supporting FileField Sources.
Plupload is a GPL licensed multiple file uploading tool that can present widgets in Flash, HTML5, Silverlight, and HTML4 depending on the capabilities of the client computer.
By using FileField Sources to add Plupload as a source, multiple file uploads can be achieved on regular File and Image fields using the standard widgets as well as a range of contributed field widgets supporting FileField Sources. This includes cropping widgets, like the excellent Manual Crop.
This module adds additional domain based settings to control a number of field settings, including field display and editing access, required flag, label and help overrides.
This module creates additional view modes for all entities. There is one view mode created per domain per existing view mode.
If a corresponding view mode for a domain is enabled on a content type, this will be automatically used to regenerate the content items (nodes) view. This option can be turned off in the domain settings page (see warning below). Other entities are not set up to automatically use these additional view modes.
Almost non-existent module which demonstrates what you can do with hook_node_view_alter().
This example changes the visibility of fields based on whether the node is published.
Inspired by this question on stackexchange: http://drupal.stackexchange.com/questions/20480/
This project is a modification on nodereference_url, aimed at referencing terms in the "new node" form based on the tid in the url. Both modules can be used independently and simultaneously. For good functioning special care should be taken though to create URLs for referencing when mixing node and term references by URL on a single node type.
A field that uses CTools access and context plugins to check access. Only a field and some API functions right now, but more will come.
This module provides a way to change the maxlength of Alt & Title to any value.
Why develop this module ?
Default value of Image Field Alt & Title maxlength are unreasonable.
Read more: http://drupal.org/node/1353030#comment-5506350
FAQ
This module allows one field to track changes over a given time span in another field based on revisions. For example, if field A records the number of kittens you own, and field B is set to find the difference of field A over a 1 month span, field B would show how many new kittens you acquired in the past month. The difference is calculated whenever the entity is saved.
Currently, only nodes seem to have revisions, so it only works with nodes. So far this only does integer differences. If you'd like it to do something else, open a feature request issue.
