Experimental Project

This is a sandbox project, which contains experimental code for developer use only.

Monitor References is a simple module that makes the values for nodereference and userreference fields on a form as they are filled out on the form. What this means is that nodereference and userreference fields which use views to define which nodes can be selected can use another nodereference or userreference field's values as arguments for their views, provided that the value is given programmatically.

Usage case

For instance, say you have these for the source field's values:

  • Burgers [nid:1]
  • Fried Chicken [nid:2]

And these are the values for the field that is dependent on the source field:

  • Burger Chicken Combo [nid:3] (this node references "Burgers" and "Fried Chicken")
  • Fried Combo [nid:4] (this node references "Burgers")

If the dependent field's argument is the values nodereference field of other nodes, you can give the view an argument of "1,2" since these are the values on your form so the dependent form allows you to pick "Burger Chicken Combo" and "Fried Combo".

Inspired by this issue: Filtering One Nodereference Field Based On Another Nodereference Field.

Note: Since this is a sandbox module, I suggest you exercise some caution before trying it out.

Maintainers for Monitor References

  • ShadowKyogre - 2 commits
    last: 47 weeks ago, first: 48 weeks ago

Issues for Monitor References

To avoid duplicates, please search before submitting a new issue.
All issues
Bug reports