|
AMTA Admin
|
August 26, 2016 at 3:14 pm
I have a complex event I need to set up, the various options for which exist here: Sample Convention. The single sessions are at the top of the datetime list with the combined datetimes at the bottom. This works well from a logistical standpoint because then each session can have different limits on tickets sold. It doesn’t work from the standpoint of actually registering for the event, because a full convention registrant can’t actually say which datetime they’re going to ahead of time. This is about half of the full list of sessions, which would need to be collapsed in some way (ideally combining each matching datetime under one expandable heading).
The other option is to have the sessions listed as questions (also present, you can run through a registration to see the questions set up), which works well from a UX standpoint. However, it becomes a mess because attendee limits can’t be set on questions, and checking people in is a nightmare of matching people against their registration answers.
Each person should be able to register for only one session per time slot (making questions appealing), but the sessions require limits to be set on attendees to avoid overbooking popular sessions (making individual sessions appealing). People will also legally need to receive certificates of completion from the sessions based on being checked in to the sessions, not just registered for them.
How do you recommend setting this up? I have half of a custom addon plugin written, but I’m not sure which side of the registration process I should be looking at.
Second thing: 
This area doesn’t consistently listen to the ordering setting from the payment methods settings. I ordered Authorize.net AIM as 1 and Check as 99 and the screenshot shows them the other way around. I can replicate it around 60-70% of the time and it can flip back without me changing settings or clearing a cache. When this happens, selecting credit card will open the CC fields, but will then select the Check radio button on its own. The fields remain open, but it won’t submit the payment info because the payment method is no longer selected. It WILL go to the next page, but it won’t even capture the payment attempt to show as failed/declined/cancelled or give an error.
Here’s my info from the Maintenance area: http://pastebin.com/r81dkNXf
|
|
Josh
|
August 29, 2016 at 4:03 pm
How do you recommend setting this up? I have half of a custom addon plugin written, but I’m not sure which side of the registration process I should be looking at.
You could follow the example of what the Espresso Breakout add-on did for Event Espresso 3 where the sessions were selected after their main conference registration was completed.
This area doesn’t consistently listen to the ordering setting from the payment methods settings.
Can you check to make sure that both payment methods are not set to open by default? Then after that, you can check for any JavaScript errors in the console. What may be happening is there’s a JavaScript error happening on the page, and the AIM fields aren’t being removed from the page as they should.
|
|
AMTA Admin
|
September 6, 2016 at 12:36 pm
There weren’t any JS errors happening, so I “turned it off and on again” with regard to the open by default option and that’s now functional. I’m not sure why that affected the display order (hence not putting the two together in the first place), but it’s fixed so no matter.
I’m having some trouble recreating the Breakout add-on for EE4, since the code changed so much. Should this be following the Add-on API method or the site-specific plugin/gist method? Because I’ll be extending it to not only include the breakout session functionality, but also the EE3 Certificates add-on, a site-specific plugin might not be the best choice?
Thanks for your help with this!
|
|
Josh
|
September 14, 2016 at 12:47 pm
You don’t need to use the Add-on API, but it can make things easier if you’re going to do model and/or class extensions.
|
|
AMTA Admin
|
September 20, 2016 at 3:39 pm
So the event will be set up with a datetime per time slot (morning session, afternoon session) and each ticket is a specific session that relates only to the correct datetime(s). This accounts for sessions that span more than one datetime (full day class). I’ll be customising the single event template to group together some things and clean up the page. I started doing this here with a demo event setup: https://amtanewyork.org/events/test-state-convention/ by modifying the datetime template to start: https://gist.github.com/KinnaT/3cb77138aacbd4e3f932ab41fa34fe0d.
This means I can focus on the other side of it for now: the datetimes need to have “continuing education credit hours” (CE credits) attached to them, because datetimes can award different amounts of hours. The logic doesn’t work for tickets because of check-ins and external requirements for this project.
Following the Pricing Hooks documentation and the WP User Integration add-on, I was able to add CE credits as an option in the ticket advanced details area, but not to the area for datetime.
Is there a hook to add a new metabox/option to a datetime instead?
|
|
Josh
|
September 23, 2016 at 7:19 am
I checked and I didn’t see one. If you need hook there, you can fork Event Espresso from github, add your hook(s), and do a pull request and development will review.
https://github.com/eventespresso/event-espresso-core/
|
