Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Class Sessions, Class Printout | Event Espresso - Staging Server
How do you handle a class that is multiple sessions? All our classes involve two or three sessions, a week apart. For example, when a customer signs up for a knitting class, they need to know that they need to come on two Saturdays, June 1 & 8 from 1:30-3:30. We have a few classes that are exceptions, where you need to come two Saturdays in a row, skip a Saturday, and then come one last Saturday. They don’t get to choose from among these sessions: when they sign up for the class, they need to automatically be enrolled on these different dates. Will this be clear for everyone involved?
We also need to be able to give our customers a print out in the shop that has a list of current classes, descriptions, session dates, and prices. Does Event Espresso have the ability to create reports like this?
Events which run over separate days but are one event, are best advised in the event description. It is possible get them created as separate events and link them to the main (first day) event as well. Sometimes this helps as you can add the different days to the calendar to show the users what days the event is on.
We do not currently have a report like what you mention.
We currently support over 15 different gateways, unfortunately BluePay is not one of them.
If you have any more questions, please let us know.
Viewing 1 reply thread
The support post ‘Class Sessions, Class Printout’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.