Chekin' in

[Daniel Abrams]

Close what window? After registration, thry are automatically redirected to Cart in same window to make payment.

[Hollis Brown]

I'm beginning to think that my wishful thinking (on both matters) is not going to carry the day.

You win.

[Daniel Abrams]

Go here and register: https://development.chapteroffice.com/event-registration/?m=e&fid=15&eid=113
How is it? Note that the email not sent yet. If you like it, I'll make it so.

[Hollis Brown]

Wait a minute! Are you saying I won? That looks like my idea.

Should that button be at the bottom of the page?

[Daniel Abrams]

After last night's election, I think you deserved something in the win column Done, and ready to test.

[Hollis Brown]

Pass
Pass
Pass

[Daniel Abrams]

Good!

Been thinking about Event Tokens (sign-in and sign-out) with respect to multi-day Events. As you have already noted, the way we have it now is insufficient. I'm thinking of a new database table: EVENTS_EVENT_TOKENS to store these tokens: ID, UID (User ID), EID (Event ID), DID (Day ID). These would be set via Admin :: Manage Events :: Day. And, another database table: EVENTS_USER_TOKENS: ID, UID, EID, DID, SIGNIN_TOKEN, SIGNOUT_TOKEN to track users signing in and out. These would visible when viewing attendees via Admin.

How would they be assigned? Per day? For example for a three(3) day Event, sign-in and sign-out each day. Each day has it's own tokens, so they are not created single for Event as it is now, but multiples (one set per day). If you did not sign-in and sign-out each day of the Event, no certificate (if applicable). Thoughts?

[Hollis Brown]

I had given up on trying to fit this into this update. However, you asked...

I imagine options:

1. Single Sign-in/out for entire one-day Event
2. Single Sign-in/out for each Day of multiple Day Event
3. Individual Sign-in/out for each Session

One certificate for entire event regardless of 1, 2 or 3. Cert would list Days or Sessions attended by each Attendee.

[Daniel Abrams]

Okay, I'll get started on this starting tonight. So, they select one of those options, and not a combination thereof?

[Hollis Brown]

I don't think it's a combination. I think it's one or the other or the other.

[Daniel Abrams]

Okay.

[Hollis Brown]

I have an early start tomorrow and I don't think you need me here, so I'm going to call it a night.

[Daniel Abrams]

Go for it, I'm good

[Daniel Abrams]

When you have a chance, in the case of (2), would each Day have the same or unique Token? And, in the case of (3), would each Session have the same or unique Token?

[Hollis Brown]

Tokens should be unique to the Day or Session. Don't want people attending one and signing in/out of two. Token is announced to the current audience and applies to them only.