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 Registration Question | Event Espresso - Staging Server
Do you have any screenshots as to what the checkout process for recurring events looks like? My client has a very specific look they want where all of the recurrences of an event are shown on 1 page, and the user can simply check the classes they want, and then checkout. Is this how your plugin works? Thanks.
Thanks. This looks like it may work. Am I correct in assuming that all the recurrences of a class can be listed on one page, and then the user can just click the “add to cart” button? Once the finished their cart, they can just go to a checkout page?
Depends on how you set up your event. There are some alternate Recurring Event Manager templates you can use that will alter the event list so that a recurring event will have a list of all the occurrences of that event underneath and you pick the one you want to register for.
Alternately, you could set up your events separately, use Multi Event Registration, and have add to cart links for each event that would take them into the checkout process.
The Multi Event Registration add-on is what adds the cart functionality, otherwise the registration process is what you see if you click on the event and enter your information that way. So if that’s what you’re looking for, you’ll want to make sure the license you go for includes Multi Event Registration or buy it as an a la carte add-on.
Viewing 5 reply threads
The support post ‘Recurring Event Registration Question’ 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.