Support

March 27, 2017 at 4:46 am

Hi Robert,

You can’t assign multiple roles to a ticket but you shouldn’t really be assigning any role to a ticket as you should use capabilities.

If I understand the above correctly, you can do what you are requesting using the sell from and until dates on multiple tickets, for example:

Ticket 1 sell from now until March 31st 5:00pm
Ticket 2 sell from March 31st 5:00pm until April 30th 5:00pm
Ticket 3 sell from April 30th 5:00pm onwards.

Ticket 1 would need a capability that only ‘Group 1’ has on their role.

Ticket 2 would need a capability that both ‘Group 1’ and ‘Group 2’ have on their roles.

Ticket 3 would not need a capability as you want anyone to access it.

I’m assuming each group has their own role?

What are you using for user/membership management currently?

March 27, 2017 at 8:07 am

How can I get group 1 and group 2 assigned to a ticket?

I’m sorry but I’m not sure what you mean.

You have 2 different types of membership levels and want both to be able to purchase the tickets?

In S2 I’m assuming your using using level_1 and level_2?

For example, I only have 100 total tickets. If I sell 80 tickets in ticket 1, I only want 20 tickets to be available in ticket 2. Then if I sell 15 tickets in ticket 2, I only want 5 left for ticket 3. Using the ‘Limit’ may not work as I will have multiple sets of tickets.

You can set the total limit on the datetime(s) for the event and then the tickets will follow that limit.

Example, I have 300 tickets for the entire event. I have 2 groups that will have 150 available tickets. So the example would look like this.

So is this similar to early bird, normal and late admission?

If you can provide details of the ticket setup I’ll create a demo event to show you what I think you need.

March 28, 2017 at 4:08 am

Ahh ok.

So you need to 2 datetimes, one to take registrations for males the other for females. The limit set on the datetimes is the event limit for each, ie, if you want 150 males you set a limit on the datetime of 150 (the ticket sales for that datetime can be made of any ticket type, but the total sales of all tickets assigned to that datetime can only total 150).

Then for each group option, you want a new ticket type, so it looks like this – http://take.ms/uDilQ

I’ve used ‘early bird’, ‘normal ticket’ and ‘late ticket’ as its basically the same setup.

So with the above the early bird tickets are available no through to the 8th of April when they close sales, then the ‘normal’ tickets open for 2 weeks and close sales and finally the ‘late’ tickets open up and are availabel fro another 2 weeks until the event date.

Make sense?

Each of those tickets is assigned to it’s relevant datetime in its settings, so a Group 1 ticket only applies to the Group 1 datetime, like this – http://take.ms/pKpPl

Group 2 tickets only apply to the group 2 datetime – http://take.ms/RrHxe

Note I’ve tested a sale of a group 1 ticket and it only applies to the group 1 datetime.

Now there is only 149 tickets available for any of the Group 1 tickets (although right now only 1 is active) it doesn’t matter that the tickets all have a ‘limit’ of 150, the datetime limit and availability overrides that.

I haven’t mentioned capabilities yet and we can do that next, but so far does all of the above make sense?

This is how it looks on the front end – http://take.ms/6ZFnW

Actually, here’s the demo event – http://demoee.org/tony-demo/events/weights-tournament/

(It also makes no difference that there is no price on the example and you can also hide the ‘tickets that aren’t available for sale currently is needed)

March 28, 2017 at 7:00 am

You’re most welcome.

If you have any further questions please do let me know.

April 10, 2017 at 4:24 am

The only problem is my group 1 users don’t have access to group 2 (level below group 1).

Your group 2 ticket needs to be set to a capability that both group 1 and group2 users have.

Are you using membership levels within S2? If so you can use the access_s2member_level{X} capability.

For example level_1 members have access_s2member_level0 and access_s2member_level1 capabilities.

level_2 members have access_s2member_level0, access_s2member_level1 and access_s2member_level2

The capabilities are ‘stacked’.

It depends on how you have your memebership roles setup but if using your own you need to ‘stack’ your user levels so the level above has access to the lower levels and then set a capabilities for the highest level (which gives access to the lower levels).