I have a slightly different requirement which I am unsure whether the module currently supports.
I would like to make the a user have to pay to be able to create an organic group, similar to pseudo-role upgrade. Additionally, the user should have to pay a subscription fee to keep the organic group "live." I do not what to have to list this as product, I would like to be internal.
In my use case, the user would earn the right to buy an organic group (rules based/userpoints perhaps). The user can purchase the right to create an organic group directly from the site, then the user will have to pay a subscription fee henceforth. The organic group can have members who also have to pay a separate subscription fee, the subscription fee may or may be a different rate to that of the group maintainer/creator/admin's "keep live" fee. Additionally, the organic group members can subscribe to multiple organic groups.
Possible?
Thanks
Comments
Comment #1
adam_b commentedsubscribe... this sounds like what I want
Comment #2
Stomper commented@adam_b, I wouldn't mind hearing what functionality you would need.
Comment #3
adam_b commentedThe site that I manage has online content to which we sell subscriptions - basically using Purchase Role in Ubercart. At the moment the subscriptions are for one year, though this might change later.
The problem comes when users want to purchase multiple subscriptions to the same package, so their users can have concurrent access. Sometimes separate logins are OK; sometimes they're redundant (eg for a library). At the moment we're using concurrent sessions, but this obviously raises other problems.
What I'm thinking of is making users able to purchase the ability to create a group, within which they'd have X number of users (depending on how many they've paid for).
...I'm still working this out, so this is as far as I've got so far. I was rummaging through OG alternatives and thought that this might be useful.
Comment #4
Stomper commentedThat's an interesting concept. So the organic group owner/admin would pay for the members, and the group members get in for free?
Comment #5
adam_b commentedYes, because the group would be a company or organisation in this case (eg an advice bureau or a law firm) - so the group buys a subscription for X number of concurrent users.
Comment #6
Stomper commentedI see, that's a cool application. I was also looking along the lines of providing subdomains for each group, it could be an optional or paid feature. So that groups could access their pages directly via groupname.website.com.
I think OG groups allows subdomains, not sure though. See http://drupal.org/project/subdomain
Comment #7
adam_b commentedWe're already using subdomains for different areas of our site, so that would be overkill from our point of view.
Comment #8
Stomper commentedI see, so you're using the subdomain module already?
Well I initially thought there was no preexisting support for subdomains, especially for OGs, but since the module does support it. Having the feature in this issue/module request is redundant.
Though, having a subdomain as a paid/optional feature might be useful for other use cases.
Comment #9
tinker commentedUsing one of these you should be able to have a product that sells the creation of a new organic group node:
http://drupal.org/project/uc_node_checkout
http://drupal.org/project/paypernode
If you want subscriptions the uc_recurring would be a good starting point
http://drupal.org/project/uc_recurring
Comment #10
Stomper commentedDo the modules you suggested work with Rules? Ideally, once a user has completed a specified number of transactions or made a specified number of contributions the role permissions should unlock. Should they accept it they should be able to start accessing the content types for that role and pay for it. Users should be alerted to this new role by email or private message.
Comment #11
tinker commented@Stomper, the modules I suggested address the issue of "Pay to create an organic group". I think the added functionality you want, user contributes and unlocks permission to purchase, is a whole other topic. You might want to check out:
UserPoints http://drupal.org/project/userpoints to store points for contributions
UserPoints_role http://drupal.org/project/userpoints_contrib to assign a role once points level is reached
Then use some sort of Access Control to grant access to a product based on role that allows for the purchase and creation of a group.
Comment #12
Stomper commentedThanks so much for the further assistance. I guess I could allocate points for a certain number of transactions/contributions. I will look further into those modules you suggested.