|
robert sirkis
|
January 18, 2017 at 7:49 am
I am running a weightlifting event and I want to have different tiers of registration based on exceeding a certain amount of weight lifted. For example, person A has a total high enough to register but person B does not. I want to allow person A to register but not person B.
My first thought is to create a password but that can easily be shared. What I was hoping I could do was somehow setup some type of database where I can reference a user ID to determine if they have met the standard.
Is there a way to handle this in EE? or do I need to try to find a way to handle in wordpress?
Open to ideas/suggestions/add ons
|
|
Tony
|
January 18, 2017 at 8:29 am
Hi there,
Some of this can be handled within EE, but the differentiation between Person A and B needs to be done through a membership type plugin (or manually by assigning specific roles you create to your users)
With EE and the EE4 User Integration add-on is set a ‘minimum require capability’ for a ticket – https://eventespresso.com/wiki/wp-user-integration/#ee4usage
So in order to purchase that ticket the user must have the capability on their account that you set within that field. Note that also means the user must be logged into the site to purchase the ticket.
So where a membership plugin plugin comes in, is Person A may have a role assigned to him by the plugin that has a ‘full_member’ capability assigned to it. If you set the min cap mentioned above as ‘full_member’ they they can purchase it, any users without the cap can not.
Will that work?
|
|
robert sirkis
|
January 18, 2017 at 8:33 am
Tony – It is definitely a start. I will start here. It sounds like it would work.
Thanks
|
|
Tony
|
January 18, 2017 at 9:48 am
You’re most welcome.
One thing to note is that EE doesn’t really care how that capability is added to your use, as long your users have the cap you set as the minimum cap they will have access to the ticket.
If using a membership type plugin you need to use one that creates either roles for your member, or adds capabilities to your members (roles probably being easier to manage in the long run).
Also, some member plugins ‘stack’ capabilities, for example S2 Member has level_1, level_2, level_3 roles, each higher role has the capabilities of the lower (level_3 has also has the level_2 cap) meaning you can do some interesting things with caps if needed.
|
