Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I found your module very nice but have encountered an issue that limits its usability. Basically the problem arises when the view with the related nodes is very large. For example, if you want to allow the user to select *any* node created on the site then the list is too long and its not viable to use it as is. I think this will happen quite often. The suggestion / request is to separate the related content into a new tab. The node_images does this for its images (i've attached a screenshot of how it works).
The idea for the related content is to add a new tab and on it show 2 lists: on top it would list the date, node type and title of the related content. On the bottom you would have a paginated list of content (using the related content view to filter the nodes). The user can then select content and with a button relate the content to the current node. To remove content the user selects the content which is already related (the top list) and clicks on a button to 'unrelate' the selected nodes.
I believe this addition will make your module much more useful and usable. I'll leave my email in case you want to contact me. I may be able to help with the coding. cesar at easytech dot com dot ar
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | relatedcontent_with_tab.png | 81.46 KB | cesarmiquel |
| node_images_0.png | 94.21 KB | cesarmiquel |
Comments
Comment #1
TBarregren commentedA very good idea. I will implement it as soon as I get some time off. Feel free to contribute a code snippet or a patch if you have time and feel for it. I would appreciated it very much, and of course give you due credit.
Comment #2
cesarmiquel commentedI finally had a little time to code a bit and finished a patch which adds a Related content tab to the edit node screen. The new tab shows the related content list, a filter to limit the view and a paginated list of nodes. The idea is to be able to work with views with many nodes. The filter allows you to further filter the nodes by part of the title and node type. I think that with this functionality the related content module will be able to work in sites with lots of content. In our case, we are using the module in a site which will have a lot of news items and they can have related content such as images, videos, audio files and other news items. The amount of nodes will increase rapidly and there should be a way to limit the nodes. Ideally the user should, when creating the view, add exposed filters and these filters should be used instead of the current two fixed filters. Unfortunately I didn't know how to do this with the views API nor did I have time to investigate it. Maybe in the future I get the time to try and code this.
I'm attaching a screenshot here and submitting the patch in the patch section. Hope this gets into CVS!
Comment #3
TBarregren commentedThis issue has been superseded by #155818.