Closed (fixed)
Project:
Conference Organizing Distribution Support Modules
Version:
6.x-1.x-dev
Component:
cod_community
Priority:
Normal
Category:
Feature request
Assigned:
Issue tags:
Reporter:
Created:
9 Jan 2011 at 01:35 UTC
Updated:
3 Jan 2014 at 02:41 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ezra-g commentedLet's get this into cod-alpha3.
Comment #2
lisarex commentedAttached is an exported feature. It abandons the previous View called 'attendees'. We might want to call this view something like 'community' if more of the social/community features we have planned are added to it it.
Comment #3
ezra-g commentedBig +1 on changing from cod_attendees to cod_community.
We need to update the machine name used for the job title profile field, since the current one results in broken views handlers, and also add a more human-readable name for the feature.
I think we can add the location bits separately later as part of #1026386: Add html5_user_geolocation for user locations.
Comment #4
ezra-g commentedI'm working on this locally. One thing to note: If this is the 'community' view, do we want to retain a second display for "attendees" so that folks can see who is attending? Should it have the same filters? Perhaps it should be a tab on the community display.
Comment #5
lisarex commentedI'd love to test this on folks... my answer depends on how the other social features (friending, fanning) are displayed as well. One the one hand, Community is the landing page and it features the Attendees. But does this Community page do much else other than provide filterable access to attendee lists and highlight Forum activity?
So having an Attendees view with the same filters doesn't worth it, unless the Attendee view has a different purpose ... maybe we just want to display names and faces like many other conference sites do and cut the exposed filters down to what makes sense?
In fact maybe the Community page default view is names + faces, and the extra exposed filters and table view appear on the Attendees page? Are names + faces only that useful to people?
However, right now I'm thinking that we don't need a 2nd display though.
Comment #6
ezra-g commentedAgreed, let's stick with this display for now.
Slight complication:
http://drupalcode.org/viewvc/drupal/contributions/modules/cod_support/co...
This feature depends on views that don't exist after we remove the existing cod_attendees :\. I'll add some placeholder displays to the new cod community view for now. I look forward to removing context in favor of panels as part of #1011844: Better default frontpage .
Comment #7
ezra-g commentedI've added a block display with the right machine name, fixed broken handlers errors and made both displays require the signup:user relationship and updated the human readable feature name & description.
This will replace cod_attendees, which will be removed.
Comment #8
ezra-g commentedThe signup.module default vbo admin view adds the "Signup: User: " relationship the user name field. I didn't notice a change in behavior leaving this relationship out as it's required on the view but we should double check before committing.
Comment #9
ezra-g commentedI tested and verified that the view functions as expected without adding the signup:user relationship to each field. It's probably important on the vbo view since that one uses both the signup:user and signup:node relationship in the same display.
I also updated the view name to just "attendees" so that it matches the cod_front_page context.
Who knew this seemingly basic feature would be such a big commit?
http://drupal.org/cvs?commit=488770
Thanks!
Comment #10
lisarex commentedupdating component