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 single confirmation page | Event Espresso - Staging Server
Hi
I have MER installed and it works fine. I’m setting it up so people can book life drawing classes in batches and the only awkward thing about the process from a user point of view is the point when having chosen 5 or 10 classes to book they have to confirm each one. I know the contents of the fields can be copied across all of them but I was wondering if there was a way of displaying only one box.
Currently no. The copy across feature was added to help alleviate this but right now the details are still needed as the way EE is set up means that the person will be registered in the database for each event. With 3.2 we change the way this works so it is more likely that this situation can be reduced further or possibly eliminated altogether, I havent got full details of what the devs are planning for this yet, but as far as I know the attendee will only be added once and have events attached to them, rather than the current attendee being added X number of times.
We have no release date yet, this year, ideally this quarter, but it has been in the works for a year already so its hard to say.
What I can advise though is that we are prioritising 3.2 workload so other areas such as feature development for 3.1.x are on hold whilst we push to get 3.2 stable and released.
Viewing 3 reply threads
The support post ‘single confirmation page’ 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.