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 Fixed Event Periods (period lengths) | Event Espresso - Staging Server
I need the option to create fixed period events and I need them to be operable for the user who will be choosing a starting date from the active calendar (or ticketing) side.
For example:
A user wants to book an event from January the 1st 2013. Now the options that I require this event-type to be is to give them 2 options. 1 option for a 2-week period and 1 option for a 3-week period. Both periods of time must exclude weekends. So a 2-week event would be for 10 business days, and a 3-week event would be for 15 business days.
So in this example, the 2-week event would end January 15, 2013, and the 3-week event would end January 22, 2013.
Are these variable settings possible for Event Espresso?
One way to do this would be to create two separate events, one for each of these choices. Another way would be to offer these options as price options. If you go with the first option, you can duplicate the two week event option by using the Duplicate event feature, then change the end date for the other event choice.
Viewing 1 reply thread
The support post ‘Fixed Event Periods (period lengths)’ 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.