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 Multi-module (split) events | Event Espresso - Staging Server
I need to do similar to Chris – have what is in effect a single bookable event, but split into two modules. Module one may be a two day event, followed by a further two day event at a specified date at some point in the near future. Here is the course description: http://www.citi.co.uk/delivering-strategic-programmes/
Even if there is a text-field where I can specify the second module dates per event would work? Ideally would be nice to see the second module in the calendar though – although not essential…
As per the previous forum post, you would duplicate the event, and in the Event Options on the right in the event editor set:
Display registration form? as NO
Use an alternate registration page – add the URL of the first event with the registration form here.
This will create a secondary event, but on selection in the calendar or event list it will redirect the user to the first event which has the registration form.
Even if there is a text-field where I can specify the second module dates per event would work?
I tried the duplicate event option – but it meant it wasn’t clear in the calendar if you clicked on the second module that you were being redirected to the first module in the event – and might be perceived as an error!
Thanks for your help though :)
Paul
Viewing 2 reply threads
The support post ‘Multi-module (split) 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.