Req: Tweak the code so that when someone is a member of CIR they are marked as a Member and not just a User in UBB. I still have to do that manually.
Since the code now only sets the UBB cookie if the correct Drupal permissions exist, OK to orphan the UBB group membership as dropping out of the Drupal "member" group will not set the UBB cookie in the first place.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | ubb.module.1296064.diff | 941 bytes | mdlueck |
Comments
Comment #1
mdlueck commentedThis patch successfully addresses our needs.
Comment #2
muriqui commentedWell, that's a quick-and-dirty approach, but not something I'd want to commit to the module, since you're just hardcoding a configuration value specific to your UBB implementation. It would be better to make the group value selectable in the admin UI.
Comment #3
mdlueck commentedAgreed, just sharing the work-around that works in our case.
I understand that the original UBB Group "Users" was used for another permission group in the past. Since we did not want to do away with that permission group, and since the Drupal group is also called "Member" I decided to do the hack I did.
So perhaps "long term" there will be a request to get more elaborate with the module and have it support multiple syncs, that if Drupal-A group then UBB-A group, etc...
For now I think all is well with this quick patch. Thanks! :-)
Comment #4
muriqui commentedFixed in commit 13d4fb1.
Comment #5.0
(not verified) commentedAddl info