Posted by tony584 on November 4, 2009 at 7:03pm
Hi,
I'm trying to create a columnist view for a client, wherein each user's name and photo will appear along with their most recent columns (blog postings). It should look somewhat like this: http://www.denverpost.com/newscolumnists
I cannot figure how to leverage views to display more than one node title for each user. Any ideas? thanks.
Tony
Comments
group by user name
Seems more of a support issue than a development one, but you should be able to accomplish what you want to do simply by creating a node view that includes both title and user name fields, and grouping the view by user name (click the little gear next to "style").
tried that
thanks, i tried that. it didn't work, and if it did work, it would give me every single column, not just n columns.
Not if
you filter by date, or something. You said most recent columns, not most recent n columns. "It didn't work" isn't very specific, either. (It worked fine in a test view I created when I answered your post.) Anyway, you might also look at the Views Attach module if you can't quite get the functionality you want, or you could create your own plugin to limit the number of items displayed per grouping.
Edit: I found an issue that's relevant to what you're trying to do; you might consider tracking it to see if anyone else posts a solution.
http://drupal.org/node/193187
thanks
thanks for your help. will do. appreciate it!
grouping field not grouping, see image
xjm - i have uploaded this image:
http://afreshsqueeze.com/grouping_field.jpg
the grouping field is not grouping them correctly. each time a node is found by the user - a new "group" is displayed rather than the usernames once followed by all nodes by that user.
tony
found the answer, here it is for all..
if your "group by" field is not working, and you are running theme developer - disable the theme developer... i found this little tidbit here: http://drupal.org/node/388140
"Caution:
If you wonder why your output is not grouping things together, disable Theme developer, and see if that helps.
In case it saves others from scratching their heads, here's something to note about this example:
The reason you write a template is that the grouping field does its comparison based on the output of the template rather than the raw data. This was apparently done to implement things like granular date grouping relatively easily.
One BIG side effect of this is that any tools that monkey with the output, say... THEME DEVELOPER ... will cause what seem like equivalent date strings to be different. More specifically, the output will be wrapped in a tag, that includes a thmr attribute that increments."
Thanks!
Very interesting
Thanks for the followup; that's a pretty sneaky bug!