This module makes is possible to use the Subform Element module with the Relativity module.
Provides an 'Edit Button' CCK field, allowing the content-type designer to add a javascript-enabled button to the CCK field set, active when the node is being edited, but hidden when the node is being viewed.
This is a convenience module for Drupal-based Ajax programming. It returns images attached to a node from CCK Imagefields. An HTTP GET request to a predefined URL format (e.g. node_resource/NODE_ID/CCK_IMAGEFIELD_LABEL/0) returns the image to the HTTP client.
Development sponsored by LANDO-LINKS, INC
A CCK field type to store lists of co-ordinates, or tracks. These tracks are intended to be visualised on maps, plotted as distance/altitude profiles, have statistics derived from them, etc.
The module has been created in what is hoped is a flexible enough manner to allow multiple input formats to be used, and to allow track data to be shown in many different ways. The 'base' trackfield CCK field knows about latitude, longitude, altitude and distance. This system is flexible enough to allow distance/altitude pairs to be entered without latitude/longitude (this entry could be via the trackfield_csv module). This would be useful for someone with a cycle computer with altimeter but no GPS who wishes to graph hill profiles. Although of course the input modules know how to convert latitude/longitude pairs into distance data when it is entered.
User data handling will be catered for later, an example of which is an athlete who might want to record heart rate and time information (from which speed can be derived) at each co-ordinate.
Asset field is used as the back end for the Asset Manager module.
Our end goal is to have it be a generic asset handling CCK-field that can easily format various file types as appropriate.
This module allows you to refer to images that are associated with imagefields using a simple URL structure that locates the images based on the nodes they belong to, rather than their locations on the filesystem. This is especially convenient for situations where you might be changing the actual filepath in an imagefield sometimes, but it's also nice if you just prefer the idea of having a more consistent URL structure for your site, where images can be treated more like "first-class content".
When you install this module, it scans all your content types to find which ones have imagefields. It also "notices" when you alter any content types to add or remove imagefields. Without any configuration from you, it allows you to use URLs like this to refer to images:
/[$node_type]/[$nid]/[$field_name]
...where [$node_type] is the "machine-readable" name of your content type, [$nid] is the node id for a particular node, and [$field_name] is the name of the imagefield without the "field_" prefix.
So, for instance, if you have a content type called "biography", and an imagefield defined for it called "field_portrait", you can refer to the portrait on node 34 like:
/biography/34/portrait
This is a user matching module that uses the Matching API to match users with similar interest / criteria.
It can be used for user personality/interest matching and similar applications.
Developed by Omar Abdel-Wahab (owahab).
Sponsored by 2bits.com
Defines a field type Node revision reference which creates a relationship to a specific node revision.
This module adds the ability to edit a single element. The element needs to be surrounded by a DIV with the right things in it. This can be achieved by using something like contemplates,
You will need something like this:
This module has been abandoned; if you are looking for actively maintained projects with a similar purpose, see
