Min #content option
Flying Drupalist - October 19, 2008 - 05:25
| Project: | Relevant Content |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Jump to:
Description
I have a space for relevant content on the site, and if there's nothing there, then it looks bad. My request is for a min # content option, so that there are at least, for example, 5 titles listed in the block. If there aren't enough legitimately related nodes, I would like for the module to list random nodes to display, and for me that would be super. :) Thanks.
#1
But if those nodes are random then they wouldn't be "relevant", would they?
It think a better alternative for a "no resultset" situation would be either:
1) dont display the block
2) fall-back to a node-queue with a customizable message for the user...
#2
Yes, that's right, the nodes would be random instead of relevant. The issue is that of the nodes on my site, all of them are relevant to each other in some way. But they may not all share taxonomy terms. The list of results that relevant content returns isn't necessarily sufficient for me. So it would be very nice if the module can return other nodes on the site.
Of the alternatives, #1 isn't possible for me, and #2 just looks bad, as there are other relevant nodes... For instance, on a site about cats, all nodes about cats are relevant, but I'm not going to tag every node as 'cat', I would tag them as grey cat, white cat, lolcat, and so on. So viewing a node about grey cat would cause me to miss out on a relevant white cat.
Thanks, I hope you understand what I'm going for here.
#3
I understand the problem here - however, in terms of taxonomy this isn't possible unless you use heirarchical taxonomy.
Although you might have grey cat, white cat, black cat and so on... As far as Drupal is concerned its Term 1, 2 and 3 which are unique. You cant simply assume that these unique terms are associated in anyway. Term 4 could be "dog" - what if I dont like dogs and only wanna read about cats?
There is also the issue of picking random nodes in that they could be completely irrelevant. In this case you might have a node type "cats"... So the feature would then become "Minimum content by filling with random nodes of a specific type"...
I think what I'd rather have here is a module hook so that if someone wants to modify the relevant nodes, they can write a small module which hooks in and pads out as necessary. A random feature - to me - seems pointless and misleading.