Closed (fixed)
Project:
Organic Groups
Version:
7.x-2.x-dev
Component:
og.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
31 May 2011 at 10:22 UTC
Updated:
8 Sep 2017 at 10:12 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedDo we really need to create separate content types, e.f.
event_for_cars
event_for_planes
etc.
How can we filter just "events" from all "cars" groups?
Comment #2
firecentaur commentedI want to know this as well.
I have several groups
1) Paid Members Group
2) members interested in books
3) members interested in giraffes
I want to create a view to display all users who are:
in the PAID Members group AND also in the Books group
How can I do this?
Please help!
Comment #3
bryancasler commentedsubscribe
Comment #4
mradcliffeI think the only way to do this is to divorce og and og_membership from og_handler_relationship (i.e. create a relationship handler for each one).
The og relationship handler should provide an options form so you can select what entity you want to relate to (Users, Nodes, etc...), and then pull in the base table and field for that entity (that's the challenge there). This, I think, is theoretically possible and I have been playing at it now and then for a while now.
Og_membership handler should work the same as og_handler_relationship works now.
Amitaibu, does this approach sound sane, and if so, may I change the title of the feature request to "Create separate views relationship handlers for og and og_membership"?
Comment #5
amitaibu> On the frontpage of my site I want to show a list of events from the cars group.
Isn't it enough to pass in the contextual filters the group ID?
Comment #6
penguininja commented> Isn't it enough to pass in the contextual filters the group ID?
Unfortunately no, because cars is not a group with a unique group ID. It is a group *type* which may contain several cars groups (like "BMW," "Toyota," etc.) each with their own group ID. A potential workaround could be to pass all the individual GIDs to the contextual filter, but that will not work in our case. (We are using OG heavily in an installation profile, so we will not know the GIDs of any of the groups being created by the end users).
Comment #7
jgraham commentedI think this should probably close out as this works in 2.x branch with the following steps.
I've been reviewing the 2.x branch of og this last week and it is looking fantastic. Huge thanks to Amitai. :)
Comment #8
amitaibu> I think this should probably close out as this works in 2.x branch with the following steps.
Fine, changing target version.
> I've been reviewing the 2.x branch of og this last week and it is looking fantastic. Huge thanks to Amitai. :)
Happy to read that, thanks for the reviews, issues and patches Jeff :)