Posted by crea on February 18, 2010 at 6:17pm
With recent development of many nodereference-based modules, I wonder if it's going to be better long-term solution to use custom nodes with nodereferences and build on that.
OG I think suffers in a way that it duplicates some features of the CCK. Example: If audience was CCK Nodereference field, I could just use any nodereference widget, that is supported, has long history of bugfixing and more stable etc. Now because audience is not CCK field I can't do that out of the box.
I am aware of the global "fieldable" focus switch in D7. I'm more interested in D6 solutions cause that's what I'm using and going to use very long.
Comments
There's related blogpost at
There's related blogpost at http://nodeone.se/drupal/goodbye-organic-groups
I'm interested
I have to be honest that it never occurred to me to use anything but OG. But I read that blog post earlier today and it got me thinking. I'll have to give some good thought to what I'm using in OG and what else could do that job.
Thanks for sparking the idea. I look forward to seeing what others think.
Michelle
It's definitely interesting,
It's definitely interesting, although I think labeling the approach described in the blog post as being "more the Drupal way" and all that one could want from OG is pushing it. I think the discussion/post would be more useful as a description of an alternative when one only needs certain aspects of OG - I'm not sure that distilling OG down to access control is quite accurate, and there are some access / display control elements in OG not covered. Still, it certainly has promise - I can see the potential - and it got me thinking as well.
I've used (and customized) OG for projects. I've opted for non-OG approaches on others. I've both appreciated OG and been frustrated by it - I have found that considerable customization is needed in some cases. But I also appreciate OG being around because it can be useful, maybe especially for those who aren't going to feel comfortable with the work of setting up an alternative.
I too was intrigued after
I too was intrigued after reading that blog post. I had never thought of that route. I would be interested in a breakdown of the OG features and how those features could be accomplished with other modules.
OG has been frustrating at times. I think it tried to be everything for everyone and bloated a bit.
-
@foggyperspectiv | foggyperspective.com (blog)
This really sounds very
This really sounds very interesting and is great to manage user access.
Nevertheless, with my limited experience, for real group functionality this does not seem to be the golden route. My main concern is about managing the group members e.g. invitation and join a group after approval. Until now I did not find a proper module which would provide me a join-node functionility. If someone knows one or is in the mood to quickly write one please feel free. ;) Also I'm not sure how to use the forum with this node reference.
thanks
Well, technically OG consists
Well, technically OG consists of several parts:
1) Relationships
2) Access control
3) Signup / Invite
4) UI to manage all that.
Parts 1 and 2 can managed by nodereference-based solutions. Signup / Invite of OG is not that good and I think many people build their own solutions anyway. UI is good for novices with no developer access but in other cases it's almost useless since you are going to build your own anyway.
For relationships, are you
For relationships, are you referring to node-to-group and user-to-group relationships?
I agree that #3 and #4 aren't very polished in OG, but at least it provides a starting point. How would this be accomplished using the nodereferenced-based solutions?
I'd also be curious on the performance of OG vs nodereferenced solutions, specifically around access control and views.
-
@foggyperspectiv | foggyperspective.com (blog)
For relationships, are you
Yes, it could be node-to-group, user-to-group of vice versa
I suspect Flag module + Rules could do most of the job for sign-up. For inviting there's Invite module but I haven't had time to try it yet.
I would too.
Issue with access module combinations
I've been trying to develop a system using the Node Access Node Reference and Node Access User Reference modules, and it's working well with one exception. If I edit any of the node reference or user reference fields, it prompts me to rebuild the permissions. If thats done, then the node reference relationships are broken. Has anybody run into this? Any ideas on why this could be?
organic groups and ubercart
hello, i am new to drupal and very exiting about the cababilities.
I will meet the camp on the the 10th and 11th on athens.
i have a problem and i need your help,
I have set up ubercart and organic groups.
what i want to do is each group creator to have the ability to own its own ubercart account, i mean the ability to get paid for the products that he/she post in the site.
I am thinking another way to do so its the pay module but doesn't seem to work or neither i can not make it work. this module gives the oportunity to have a paypal checkout bottom on each node..
but even than there is no way to use a shopping cart.
so i am stack with the idea to use ubercart and each group or even each user have the ability to administer their ubercart account.. and post and make changes to the payment modules as paypal for example.
please give me your ideas ..
i have seen that a module has been done in the past 2 years ago but it will be for older version of drupal 4.7 .. and they provide only .module file.