Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By dageshi on
Hello I'm wondering if someone can advise me on the drupalish way to accomplish the following.
I've got two nodes, Show and Show_Review
Show has dates, venues, band names e.t.c. Show Review is a review of a show and currently uses a node reference to reference which show is being reviewed. My dilemma is that alot of the fields from show should be in show_review aka band, dates, venue e.t.c.
I've not been able to figure out whether I can use views to reference and sort fields in the show node when being referenced by show_review.
Aka I want to display show_reviews nodes based on the date that a specific band played at a specific venue with all this information being held in the Show node node and referenced by the show_reviews node.
At the moment I have identical venue, band, date fields in both nodes, I wrote some ajax code that automatically fills in the relevant fields in the show_review create content form when the nodereference select field is changed. But I'm wondering whether this is a good way or if there is a better way, it works and allows views to sort all the data correctly, in theory the information in show should never change after the gig has happened but I have this uneasy feeling about it.
Any advice appreciated.
Comments
Your uneasy feeling is
Your uneasy feeling is warranted. You shouldn't need to duplicate fields.
You can certainly use Views to pull information about the Show from the Show Review nodereference CCK field.
Seeing is better than words, so look at this video from Lullabot. Yes, it's dealing with photo galleries, but the data and relationships are the same, so the setup would be very similar.
-Corey