Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Allow there to be multiple codes per group where each code could give the newly registered user a different role.
What would be a good way to present this to the administrator and group admins?
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 620496-multiple_keys-5-D6.patch | 6.67 KB | sreynen |
Comments
Comment #1
marcp commentedIf anyone's interested in this, please re-open.
Comment #2
bribiz commentedI have a use case for this too. Would this be a significant re-write or a minor change in your view?
I would like to keep one organic group but be able to assign multiple codes to it. I would then like to turn off codes in the future so as to block access to old subscribers who haven't been given the new code.
Comment #3
marcp commentedIt's a pretty big departure from the current [simple] design. First off, the database schema will need to change. The system configuration screen will be more complicated and the fields that are added to each group node will be more complicated.
It would be worthwhile to spec out how exactly you think this should look configuration-wise at admin/og/reg-keys-settings and also on the group node pages. Getting that specified will be a good part of the battle.
Comment #4
sreynen commentedI have a use case this functionality, and I'm volunteering to write a patch. Here's how I see the interface changing:
- On admin/og/reg-keys-settings, we add a new field for number of keys per group, defaulting to 1. (This goes in a system variable.)
- On each group page, we include however many key fields we've specified. (This will require changing the DB schema.)
- On admin/og/reg-keys-edit, we change the REGISTRATION KEY column to REGISTRATION KEYS and list the keys. (This will require changing og_reg_keys_views_data and I think adding a custom handler based on views_handler_field_prerender_list.)
Sound okay?
Comment #5
sreynen commentedAttached patch does most of what I described in #4. I didn't actually change the admin/og/reg-keys-edit view. The database schema also didn't change much, so that's just showing the first now if there are multiple keys.