You are here

README.txt in Node Relationships 6

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Node Relationships
;;
;; Original author: markus_petrux (http://drupal.org/user/39593)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

CONTENTS OF THIS FILE
=====================
- OVERVIEW
- REQUIREMENTS
- INSTALLATION
- DESCRIPTION
- DEVELOPERS
- CREDITS


OVERVIEW
========

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: "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.


REQUIREMENTS
============

- CCK and Node Reference.
  http://drupal.org/project/cck

- Views.
  http://drupal.org/project/views

- Modal Frame API.
  http://drupal.org/project/modalframe

- jQuery UI module (with jQuery UI library 1.7.x).
  http://drupal.org/project/jquery_ui


INSTALLATION
============

- Be sure to install all dependent modules.

- Copy all contents of this package to your modules directory preserving
  subdirectory structure.

- Go to Administer -> Site building -> Modules to install module.

- Review the settings of your nodereference fields to make sure related
  content types are explicitly specified in the option "Content types that
  can be referenced". Note that this is optional when you are using a view
  for your nodereference fields, but this information is required by the
  node relationships module.

- Now you can start browsing the "Relationships" tab available in the
  administration section of all content types, next to the "Manage fields"
  and "Display fields" tabs provided by CCK.


DESCRIPTION
===========

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:

- Node reference extras:

  This module provides several enhancements for node reference fields configured
  to use the autocomplete widget:

  - Search and reference view
  - Create and reference
  - Translate and reference
  - View referenced node on new window

  When these options are enabled, a new button for each one will be rendered
  in the node edit form, next to the corresponding autocomplete widget of the
  node reference field. These buttons will open a popup dialog where each
  feature is available.

  For nodereference fields defined with multiple values, a new button will be
  available next to the "Add more items" button that can be used to search and
  reference several nodes at a time.

  The "Search and reference" feature uses a view that is dynamically configured
  so that a single view can be reused by several node reference fields. A
  default view is provided with basic fields and pages for table or grid styles.
  You can modify and/or clone (recommended) this default view to add more field,
  filters, etc. A filter per node type is dynamically created to match the
  "Content types that can be referenced" option in the global settings section
  of the node reference field. Note that you should configure this option
  explicitly even if you use a view for the node reference field.

  The "Translate and reference" feature is available when the Drupal core
  translation module is enabled, and additional support is provided when
  the Internationalization module is enabled. When the "Translate and reference"
  option is enabled for a particular node reference field, references that
  already have translations will be automatically assigned to the values of
  node reference fields when a node translation is started. For those that do
  not have translations, a message will be displayed on the create translation
  form to warn the user a translation is missing and an option to translate and
  reference will be provided.

- Automatic back references:

  This module provides a method to display back reference views on referred
  nodes. Back reference definitions are taken from the "Content types that can
  be referenced" option in the global settings section of node reference fields.
  Note that you should configure this option explicitly even if you use a view
  for the node reference field.

  These back references do not need additional data stored in the database.
  Instead, views with the proper relationships are used to join the node
  reference field data with the corresponding nodes in the database. These
  views can then be used from the referred content types to provide a list of
  referrer nodes. The Node Relationships module provides a default view that
  you can modify and/or clone (recommended) should you need to add more fields,
  filters or change any other option to suit your needs.

  Each back reference can be displayed using one of several methods to render
  the corresponding view in the referred node itself (Field, Page and Tab).

  - Field: When a back reference is configured as a "Field", the Node
    Relationships module creates a CCK field automatically that provides the
    view output, and you can drag'n'drop this view to any position from the
    "Manage fields" panel of the content type. Note that no input widget is
    provided for this kind of fields, only the view output is provided.

    Available field formatters:
    - Back references view: renders the customized view as usual.
    - Back references count: displays the count of back references.

  - Page: This method provides a fieldset where all back reference fields
    assigned to this region will be rendered. This fieldset can be dragged
    to any position in the node using the "Manage fields" panel of the
    content type.

  - Tab: This method provides an alternative to the "Page" region, but the
    back references are displayed on a new tab "Relationships" added to the
    nodes where this option is enabled.

- Entity relations diagram:

  This is a basic diagram of the relations of current content type with others
  (referred from and refers to). It can be used to walk the relationships of
  all types in the system. This diagram is available per content type from
  Administer -> Content management -> Content types -> [type] -> Relationships.


DEVELOPERS
==========

Aside from the options that can be configured for node reference fields,
back references, views, etc. The Node Relationships module exposes a series
of hooks that provide enhanced methods of programmatic configuration of the
views and output generated.

@todo: Document the hooks provided by the Node Relationships module.


CREDITS
=======

- This module has been sponsored by Gamefilia:

  http://www.gamefilia.com

- Original versions of the icons can be found free from here:

  http://www.famfamfam.com/

File

README.txt
View source
  1. ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
  2. ;; Node Relationships
  3. ;;
  4. ;; Original author: markus_petrux (http://drupal.org/user/39593)
  5. ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
  6. CONTENTS OF THIS FILE
  7. =====================
  8. - OVERVIEW
  9. - REQUIREMENTS
  10. - INSTALLATION
  11. - DESCRIPTION
  12. - DEVELOPERS
  13. - CREDITS
  14. OVERVIEW
  15. ========
  16. The Node Relationships module provides methods to complete two way relationships
  17. between content types enhancing the features of node reference fields.
  18. It provides the following features:
  19. - Enhancements for node reference fields: "Search and reference view" (single
  20. and multiple selection based on dynamically configured views), "Create and
  21. reference" and "Translate and reference" (when the Drupal core translation
  22. module is enabled, with additional support for Internationalization module).
  23. These features use the Modal Frame API to provide popup dialogs from buttons
  24. attached to node reference fields configured to use the autocomplete widget.
  25. - Automatic back references using dynamically configured views that are able
  26. to extract the relations from existing database information. This views can
  27. be rendered using a myriad of methods in the node view.
  28. - The Node Relationships module provides default views for each feature that
  29. can be modified and/or cloned (recommended) should you need to add more
  30. fields, filters or change any other option to suit your needs.
  31. - Basic entity relations diagram (ERD) that can be used to view the relations
  32. of each individual content type. The provided diagram can be used to walk the
  33. relationships of all types in the system.
  34. REQUIREMENTS
  35. ============
  36. - CCK and Node Reference.
  37. http://drupal.org/project/cck
  38. - Views.
  39. http://drupal.org/project/views
  40. - Modal Frame API.
  41. http://drupal.org/project/modalframe
  42. - jQuery UI module (with jQuery UI library 1.7.x).
  43. http://drupal.org/project/jquery_ui
  44. INSTALLATION
  45. ============
  46. - Be sure to install all dependent modules.
  47. - Copy all contents of this package to your modules directory preserving
  48. subdirectory structure.
  49. - Go to Administer -> Site building -> Modules to install module.
  50. - Review the settings of your nodereference fields to make sure related
  51. content types are explicitly specified in the option "Content types that
  52. can be referenced". Note that this is optional when you are using a view
  53. for your nodereference fields, but this information is required by the
  54. node relationships module.
  55. - Now you can start browsing the "Relationships" tab available in the
  56. administration section of all content types, next to the "Manage fields"
  57. and "Display fields" tabs provided by CCK.
  58. DESCRIPTION
  59. ===========
  60. The Node Relationships module provides methods to complete two way relationships
  61. between content types enhancing the features of node reference fields.
  62. It provides the following features:
  63. - Node reference extras:
  64. This module provides several enhancements for node reference fields configured
  65. to use the autocomplete widget:
  66. - Search and reference view
  67. - Create and reference
  68. - Translate and reference
  69. - View referenced node on new window
  70. When these options are enabled, a new button for each one will be rendered
  71. in the node edit form, next to the corresponding autocomplete widget of the
  72. node reference field. These buttons will open a popup dialog where each
  73. feature is available.
  74. For nodereference fields defined with multiple values, a new button will be
  75. available next to the "Add more items" button that can be used to search and
  76. reference several nodes at a time.
  77. The "Search and reference" feature uses a view that is dynamically configured
  78. so that a single view can be reused by several node reference fields. A
  79. default view is provided with basic fields and pages for table or grid styles.
  80. You can modify and/or clone (recommended) this default view to add more field,
  81. filters, etc. A filter per node type is dynamically created to match the
  82. "Content types that can be referenced" option in the global settings section
  83. of the node reference field. Note that you should configure this option
  84. explicitly even if you use a view for the node reference field.
  85. The "Translate and reference" feature is available when the Drupal core
  86. translation module is enabled, and additional support is provided when
  87. the Internationalization module is enabled. When the "Translate and reference"
  88. option is enabled for a particular node reference field, references that
  89. already have translations will be automatically assigned to the values of
  90. node reference fields when a node translation is started. For those that do
  91. not have translations, a message will be displayed on the create translation
  92. form to warn the user a translation is missing and an option to translate and
  93. reference will be provided.
  94. - Automatic back references:
  95. This module provides a method to display back reference views on referred
  96. nodes. Back reference definitions are taken from the "Content types that can
  97. be referenced" option in the global settings section of node reference fields.
  98. Note that you should configure this option explicitly even if you use a view
  99. for the node reference field.
  100. These back references do not need additional data stored in the database.
  101. Instead, views with the proper relationships are used to join the node
  102. reference field data with the corresponding nodes in the database. These
  103. views can then be used from the referred content types to provide a list of
  104. referrer nodes. The Node Relationships module provides a default view that
  105. you can modify and/or clone (recommended) should you need to add more fields,
  106. filters or change any other option to suit your needs.
  107. Each back reference can be displayed using one of several methods to render
  108. the corresponding view in the referred node itself (Field, Page and Tab).
  109. - Field: When a back reference is configured as a "Field", the Node
  110. Relationships module creates a CCK field automatically that provides the
  111. view output, and you can drag'n'drop this view to any position from the
  112. "Manage fields" panel of the content type. Note that no input widget is
  113. provided for this kind of fields, only the view output is provided.
  114. Available field formatters:
  115. - Back references view: renders the customized view as usual.
  116. - Back references count: displays the count of back references.
  117. - Page: This method provides a fieldset where all back reference fields
  118. assigned to this region will be rendered. This fieldset can be dragged
  119. to any position in the node using the "Manage fields" panel of the
  120. content type.
  121. - Tab: This method provides an alternative to the "Page" region, but the
  122. back references are displayed on a new tab "Relationships" added to the
  123. nodes where this option is enabled.
  124. - Entity relations diagram:
  125. This is a basic diagram of the relations of current content type with others
  126. (referred from and refers to). It can be used to walk the relationships of
  127. all types in the system. This diagram is available per content type from
  128. Administer -> Content management -> Content types -> [type] -> Relationships.
  129. DEVELOPERS
  130. ==========
  131. Aside from the options that can be configured for node reference fields,
  132. back references, views, etc. The Node Relationships module exposes a series
  133. of hooks that provide enhanced methods of programmatic configuration of the
  134. views and output generated.
  135. @todo: Document the hooks provided by the Node Relationships module.
  136. CREDITS
  137. =======
  138. - This module has been sponsored by Gamefilia:
  139. http://www.gamefilia.com
  140. - Original versions of the icons can be found free from here:
  141. http://www.famfamfam.com/