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 sessions vs. recurring events | Event Espresso - Staging Server
Hi,
I posted this in an existing pre-sale thread, but might be better to start a new one here:
How will courses look like in V4? The workaround with recurring events and multiple registration is a deal breaker for me unfortunately. My classes run 6 to 8 weeks with up to 16 sessions per class (Mondays and Fridays e.g.). With 25+ classes at the same time and each class starting 4 to 8 times a year, I normally have roundabout 150 events to manage. With your workaround I would have to work through a list of almost 2,000 events in the backend – only to have a nice calendar view of all sessions instead of just the sign-up date. Not working for me… :(
Will V4 have a solution for this? :) I can imagine that I am not the only one struggling with this.
thanks
I think version 4 will be better for you if I understand your needs correctly. In the version currently being worked on we have an option for a single event to have multiple dates and times.
The calendar will not be released initially, but it is of course on our list of things to do.
This is a real problem for us as well. What is the time frame for v4 and the supporting calander?
Viewing 3 reply threads
The support post ‘course sessions vs. recurring events’ 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.