Note that there are some explanatory texts on larger screens.

plurals
  1. PODrupal 6: sort display of node references
    primarykey
    data
    text
    <p>I have a content type that references multiple nodes, and I need a way to sort the display of those referenced nodes.</p> <p>Any ideas?</p> <p>--- EDIT --- Clarification:</p> <p>I'm not using views, but rather am using my own queries.</p> <p>I have a bunch of teachers (teacher content-type), and some conferences (conference content-type).</p> <p>Within the conference content-type I want a node-reference field set to handle multiple teacher selections. But I need to be able to manually order them independently. What that means is that each individual conference needs to be able to sort the order of the particular teachers selected.</p> <p>That's the ideal situation, but not the way I'm actually doing it.</p> <p>What I'm ACTUALLY doing to jury-rig this thing is to have separate node-reference fields (teacher 1, teacher 2, teacher 3 etc.). Each node-reference field independent of the others.</p> <p>It makes for a mess when it comes to creating views or composing db queries. </p> <p>I know what I'm looking for is all but impossible, but I thought I'd run it by the Drupal gurus here anyway...</p> <p>--- EDIT 2 --- Further clarification:</p> <p>Another way to do what I want, but is really impractical, is to create a separate nodequeue for each conference. Then you could select a handful of teachers associated with each conference and order them via the nodequeue. - That should help with visualizing the problem. But as a solution, it's even more messy (in terms of administration) than the one I'm currently using.</p> <p>Also: I should mention that we're talking about 40 to 80 conferences, and 100-200 teachers. Just to get an idea of why I'm looking for a more elegant solution than the two I mentioned above.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload