It'd be nice to have a reverse node reference argument, so you can pass in a node id, and the view will get filtered down to any referenced node of that node id. Does that make sense?

Comments

markus_petrux’s picture

markus_petrux CreditAttribution: markus_petrux commented
Status: Active » Closed (works as designed)

Re: "Does that make sense?"

Not as part of this module, I'm afraid.

This module provides a Views Relationship that you can use to add a nested join to the query. Once you're there, you can add additional filters and/or arguments to the view using fields provided by either side of the relationship.

mansspams’s picture

mansspams CreditAttribution: mansspams commented
Priority: Normal » Major
Status: Closed (works as designed) » Active

too bad, its a must. how else can I make a list of nodes of DIFFERENT TYPES that references current node. With this module I am limited to only one type since reference fields in different content types have different field names.

markus_petrux’s picture

markus_petrux CreditAttribution: markus_petrux commented
Priority: Major » Normal
Status: Active » Closed (works as designed)

This module provides a method to join tables in a view. That's all this module does.

Once you get the joins, you can keep adding stuff to the view to suit your needs, but that's out of the scope of this module.

If you need further assistance, please use the development forums. Thanks