I have the organic group (og) subscribe module working
http://drupal.org/project/uc_og_subscribe
I have also figured out how to use migrate (migrate_og) and tablewizard to import my 100+ groups.
What is a practical way to manage this? I'm interested because it is interesting to figure out the "right" drupal way of doing things, and also because, even after I get my site set up with my (less than 200) groups, I'm going to be sharing the site with other local organization I partner with, and they are going to be setting up their sites, with there own different set of groups! So this site set up will need to be done quite a few times.
I think ideally, on import of a cvs file describing the groups it would [it. what is it here. maybe my own module, I just did http://drupal.org/node/735714#comment-2694462, or is it a rule]:
a* set up the attribute option values for the one product we have: "join". in the join product, there is an attribute (pull down) to select the groupname. each option value is a groupname.
b* for og groups who have a certain category (taxonomy) of active [vs closed] those groupnames would be enabled in the product options (eg. node/19/edit/options)
c* set the sku in the adjustments to something like 1001-groupname
d* add a group subscription feature (node/19/edit/features) for each sku linking 1001-whatevergroupname to the og group groupname
I've used rules a bit lately, so I'm wondering if rules can be used to do any of this.
Even something like:
tigger: create new node type group (that is what my migrate import does)
action: a-d, etc. might be some built in actions that would work, or use the execute php action
I suppose also I would need something for when a group changes from active to closed:
e* disable the product option
And maybe some like when a group is deleted:
f* remove the attribute option
I'm guessing I wont have to disable the option for the product [coresponding to b*, because the option will be removed, so it wont be listed anyway. And same for c*: there wont be an adjustment, hmmm what about d* the feature? I guess if the attribute option value is removed, I wont have to worry about the feature either... Hmm. I just tried it. I manually deleted an option value for groupname: MyCity, which did take care of c* the were no adjustments then for setting the sku of the product with that option, because the option was gone. BUT, the feature was still there which said to look for the sku 1001-MyCity. Also interesting, I did delete the actual og group, and the feature is still there to saying: MyCity is the group to subscribe to. If I edit the feature, then sku pull down menu does not list the old adjustment (because it is deleted) and it does not list the old group (because it is deleted)... but the old feature is still there, "trying" to do stuff based on a sku that does not exist, to a group that does not exist.
Well. There are some thoughts recorded so I dont forget them, and also to see what others have to say. Thanks.
