Jump to:
| Project: | RelatedContent |
| Version: | 5.x-1.6 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
This is a very nice module and has a good approach of using views module. Still this module could have even better integration with views, but also support for cck.
a) Currently options what to display in nodes are: teasers or full nodes. It would be great, if user could select a custom view (that is made first in views administration) and what ever view type (list view, calendar view, table view, etc), that determines exactly what and how to display in nodes.
b) Currently options where to display in nodes are: beginning, end and not at all. This makes troubles with some customized content types. What if this module would produce a cck field type, that displays related links view. Perhaps this module could use some functions of view field module, too.
c) Currently it's possible to select a view, which makes lists for selecting nodes of related content. That's fine, but in tab where nodes are selected, it's freezed to display only columns title, node type, author and created information. In some use cases this is not relevant information. It is useful have a table view with check boxes here, but other columns could be optional and additional column options could come from selected views - or showing only those columns that selected view displays. Also, if a selected view supports exposed filters, related content module could display them here.
d) I'm not sure, but seems that API currently doesn't support displaying referring nodes. For example, if this module would make a new views field "referred by" (showing list of node titles) and a new views filter "is referred" or "is related", then it could be possible to have referring information (as counter-part of related information) for any views that needs them.
e) In node edit views, users see a tab "Related Content" in every content type where this module is in use. Since there can be many reasons for creating content relations, this text is not always relevant. It might be useful to have a customized tab name for each content type.
Comments
#1
+1 for adding support of exposed filters. This would be a huge help for sorting through lots of content to match by keyword.