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 Course groupings and datesets/sessions | Event Espresso - Staging Server
First of all i cannot reply to your mail (sales@eventespresso.com).
Next heres my answer:
Hi Garth
Well. Perhaps it helps. Is there anywhere i can see it in action?
You know. The backend?
In my world a package could consist of 3×3 days/ 3 courses. The days are not always sequential. So the 9 dates could be like: 1,2,6/may + 12,13,17/may + 21,22,26/may.
Each course can be bought individually or in the package. In the backend i need to i ONE view to see who registered for fex course2…
Yes. As Garth explained through email, you can both list the events/courses individually as well as use a shortcode to allow the users to register for more than one at a time.
The shortcode to add a series of events to the cart in one step looks like this:
[ESPRESSO_CART_LINK event_id=”6-7-8-9-10-11-12-13-14-15-16-17-18-19″ direct_to_cart=1 moving_to_cart=”Redirecting to cart…”]
This is the only option we have currently.
Did you look into EE4?
Viewing 3 reply threads
The support post ‘Course groupings and datesets/sessions’ 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.
Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.