On the event creation form it says "Select what type of registrations should be enabled for this sng_online_conference. Depending on the display settings, it will appear as either string, registration link, or form."
I want to be able to restrict which options the event creator has.
Can I currently do this via roles? (If not this is a feature request)
use case 1: Features integration
The way features works is that I have to create registration bundles for each feature. So if I have event and a meetings features, I have to create two different event registration bundles. If I create an event, I don't want someone selecting the meeting registration bundle.
Use case 2: To further complicate maters
So for the meeting I might have a basic and adv registration or a vegan vs carnivore registration. And there is a seperate event feature which has been enabled but the meeting creator does not have access to.
I would like to be able to either give the meeting creator the option of selecting either or as an admin I select one that cannot be changed. In either case, the meeting creator should never see the registration entities for the event feature.
Issue fork registration-1683116
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #1
fishfree CreditAttribution: fishfree commentedI have the same need. This should be configured in the "Registration" field editing UI, Administrator can select registration types.
Comment #2
Mike.Conley CreditAttribution: Mike.Conley commentedI'd like to throw my name into the hat as well, it would be great if administrators could limit registration types per attached entity type, just like you can choose which bundles you'd like to allow on an entity reference field.
Comment #3
john.oltman CreditAttribution: john.oltman at SiteBasin, Inc. commentedComment #5
john.oltman CreditAttribution: john.oltman at SiteBasin, Inc. commentedComment #7
john.oltman CreditAttribution: john.oltman at SiteBasin, Inc. commented