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 Event Setup Strategy | Event Espresso - Staging Server
We’re trying to wrap our heads around the best way to setup class schedules using EE. So far, we’ve not had great luck with this.
There are a couple of variables that impact how a user can register for a class:
– The type of class that they are registering for (there are 3 types: A class series, single classes from the series, and a single class not associated with a class series)
– Single vs. Group (in our case, this is generally a couple, or two people)
So I guess my question is this – Is there a way to have just one fee for an event, regardless of the number of attendees per registration?
Yeah, we’ve decided that the best (and perhaps only option, without hacking things to death) is to allow group registration and have a general question set for the primary attendee, and nothing for the additional attendees, since additional attendees vary with regards to their information needing to be collected (these are for birthing classes, so custom fields could be for fathers, children, etc.).
We’re going to write a function that forces the base ticket fee for the course, no matter how many attendees register. The reason for this is, while we don’t want to increase the cost based on registration (whether that be 1 person registering, or a group of 5), we still need to reduce class capacity based on attendee.
So, we should be good for now (assuming our plan works out the way we think it will).
The support post ‘Event Setup Strategy’ 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.