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 Recurring event following school term | Event Espresso - Staging Server
I’m switching from my current booking system to event espresso and am struggling to get my head around recurring events.
I run a drama studio and we run four x eight week programs each year. Each eight week program coincides with a school term.
Our students are automatically placed into the new term at the conclusion of the previous term, but at the beginning of each term we also open registrations to new students.
I’m unsure if I should be using the recurring event settings to create each of my classes 8 per term x 4 (so 32 in total) or if it should just reflect the start date of each term?
If for example, you need every single class to be shown on the calendar, then you would need to create the 32 events, and probably link them using the Alternate Registration URL option in each event so that only one event is actually used for booking.
More likely I would say to create the 4 events and have the dates run from start to finish so it shows correctly on a calendar, with the registration times set as needed (ie end registration before the first day of “term” if registration stops then).
Let me know if you need anything else clarifying regarding this matter, as I know that the Recurring Events Manager can be overwhelming to use at first.
Viewing 1 reply thread
The support post ‘Recurring event following school term’ 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.