Hi all,
I'm busy creating a website which has an assortment of games (self created content type). Now I'm struggling with relations between the different games (nodes).
Problem 1
Several games can be part of a game family. I want every member of the family to have a set of links to the other members of the family in the node. So for instance:
I have:
- Game 1, member of no family
- Game 2, member family A
- Game 3, member family A
- Game 4, member family A
On the Game 1 node there will be no links since it's not member of a family. On Game 2, 3 & 4 there will be links to eachother since they're all member of the same family.
I've tried messing with Views, but didn't manage to get this working. My problem is mainly that there are a lot of games (over 300), so I would like to have a process that is mostly automated for the people who will be adding games.
Problem 2
The same games can be extensions to other games. On the nodes that are an extension of another I would like a link to the original game, while on the original game I would like to see links to all the extensions. So again an example:
I have:
- Game 1, no extension
- Game 2, original game
- Game 3, extension of game 2
- Game 4, extension of game 2
On the game 1 node there will be no links since it is no extension and has no extensions. On game 2 there will be a link to game 3 and 4, while on those nodes there will be a link to game 2.
I hope someone can help me, I seem to be circling around the solution. I want to point out that the website is a completely new website so I can change everything without effect. All games are yet to be added once the website is finished.
Thanks in advance!
Comments
Taxonomy & Node reference
Hi,
Problem 1:
Have you tried using taxonomy to categorize game nodes? -> http://drupal.org/handbook/modules/taxonomy
Problem 2:
You can use a node reference for this purpose by using CCK -> http://drupal.org/project/cck
Hope this gets you started.
Best regards,
Karel
Hi Karel, Thanks for your
Hi Karel,
Thanks for your answer.
I have tried both but didn't succeed in making it work the way I want.
Taxonomy seems the way to go, but how would I automate the process of displaying more from the same family without having to pass an argument to views by typing something in a text box. I tried content taxonomy, but it seems like this is not supported by Views.
Node reference actually works perfectly, but again, the automation is something I'm looking for. If a game has a large family (maybe 15 related nodes) all would have to be added one by one to the node reference.
Thanks in advance!
Libeco, You might want to
Libeco,
You might want to have a look a the following tutorial, this should do what you want:
http://drupaleasy.com/blogs/ryanprice/2008/06/using-views-2-drupal-6-create-a-related-pages-block
Here is the code that's been used on the view in the tutorial so you can copy/paste:
Concerning the node reference, wouldn't you just assign a node reference upon creation of a new node?
Regards,
Karel
That tutorial is (almost)
That tutorial is (almost) exactly what I needed! Do you know how I would use this code, but make sure the currently displayed node will not be showing in the list?
As for the node reference: the way I see it now if a game is an extension of another I would have to manually add the node reference to both. One for the extension which says: this game is an extension of: game x. And another one for the original game which says something like: these are the extensions for this game: game b, game c, game d.
It is possible though that the original game will be published now and the extension only in two years time.
So doing this manually just seems like somthing that could be done easier.
In my mind I picture something like this: on creation of a new extension the user picks what game this is an extension to. A view in the original game will somehow see which games are extensions to it and display those. I hope you understand what I mean.
Thanks again!
I just tried the NodeReferrer
I just tried the NodeReferrer module and it seems to do exactly what I want. I will need to look further into it, but it looks promising although it's still in dev...