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 Cart with Mutiple Pricing Levels | Event Espresso - Staging Server
Is there a way to remove the additional forms for different pricing options on the registrant information page when using the cart? Or have them autofill behind the scenes without being visible?
I have an event with adults and children – basically, I know i don’t want any information beyond the additional registrant.
Well, you could change the additional attendee date to request name and email only or turn it off so no data is collected. We have an option on the form to copy the data across but nothing that works behind the scenes.
I do have it set up to ask for no additional info, however to get the multi pricing levels to show up I need to use the cart which brings up a second registration for the child tickets regardless.
I would really like to hide this form as its completely unnecessary. Any other ideas?
It is currently necessary as that is how the system operates, it requires attendee details in this situation, without them it wont register that person.
In the next major release (4.0, renamed from 3.2) it will be easier to achieve situations like what you want, due to the different way we are taking registrant details.
We are hoping the preliminary version will be out in the next 30-60 days approximately. However it will not be fully functional compared to the current version and may not have what you need out of the box.
Viewing 5 reply threads
The support post ‘Cart with Mutiple Pricing Levels’ 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.