Autocomplete widget is broken. Forcing a Node Creation. Nodereference Count. 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. Also see Entity reference count for a version of this module that works with entity references. This should be an improvement over alternate solutions to the same problem, such as: Using a computed field, which would either be updated when viewed, but not available to views, or when saved, but not when a nodereference was added or removed. Or a view, which would be updated when displayed, but with a performance price and not be available within the node itself. Formatters Two display formatters are provided. Installation. Node reference field. Reference views 6. This module allows views to be used as formatters for CCK node and user reference fields.
This means that instead of just a title, teaser, or full node, you can show nodes using any fields that are available to Views, in any sort order, in any view style, with any views theming. This module is version 2 of Node reference views, reworked to provide multiple formatters, and for user references as well as node references (hence the change in name). There are instructions and examples on the documentation page. Node Reference View Formatter 7. Node Reference Create 6/7. Node Widget. Node Widget allows to create and edit referenced nodes (stored in CCK nodereference fields) in the same form used to edit the main content.
An editing form for referenced nodes is embedded in the main editing form; it is possible to select which fields should appear in this subform. The module supports only single value fields of the following modules: Content Taxonomy: select and radio widgetsDate: text, select and popup widgetsEmail Field: text widgetFivestar: stars, select widgetsLink: link widgetNode Reference: select widgetNumber: number widgetSelect (or other): select widgetText: text, select, radios/checkboxes widgets Available in 6.x-1.x-dev Filefield: file upload widgetImagefield: image upload widget Usage.
Node reference auto-create 6dev. Reverse Node Reference 6. Overview The Reverse Node Reference module enhances Views with reverse relationships for node reference fields.
Drupal 7 status: This feature is provided by References and Views 3. See these threads: #1083902: Backreferencing (listing nodes that reference the target node) and #1188500: Provide a reverse taxonomy field relationship. Description Node Reference fields in CCK for Drupal 6 provide relationships to Views that allow you to access fields from the referred nodes of a particular node reference field.
For certain applications, we may also need to do the opposite, travel from the parent node (the referred node) to the child node (the one that has the node reference field). This module implements the reverse relationships using the second option. More information How is this different from nodereferrer? How can you get involved? Write a review for this module on drupalmodules.comHelp translate this module at localize.drupal.orgHelp writing documentation.
Partners 6. Corresponding node references 6/7. New development is done in the 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. Screenshots Description It syncs the node reference between two node types which have a nodereference to each other, so double editing nodes is no more needed. Updates Release 6.x-4.0 doesnt require setting the options to unlimited, all is handled by cck now. Dependencies. NodeReferrer 6. BackReference 6. D7 Note Currently, what with how Drupal 7's fields are written in a way so you can't really tell how to get at the data, and with Corresponding Node Reference already having a successful D7 port, there are no plans to update Backreference to Drupal 7.
If you plan to upgrade, I suggest changing your Drupal 6 site to use Corresponding Node Reference, and then update. Backreference Module provides a nodeapi interface to maintain 1-1 relationships between all shared instances of a nodereference field. This means that given a field instance of field_reference1, if you add a reference to NodeBeta to NodeAlpha's field_reference1 and NodeBeta has an instance of field_reference1, then NodeAlpha will be added to NodeBeta's instance of field_reference1. There are other similar modules out there that do similar work, such as NodeReferrer and Node Relationships.
Along the same lines is Corresponding Node References, which seems to work similarly to BackReference.