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 Problem configuring go to cart shortcode | Event Espresso - Staging Server
I’d like to skip the add to cart/view cart step when using MER and multiple events. So I set up the shortcode so when they click the “Register” button, they go to the cart and see 6 events, choose the number of people and enter attendee info. This worked how I wanted it to yesterday. Today when testing, when I click enter attendee info, I get the following:
Attention
For BABC 2014 Full Conference With Evening Events, please make sure to select at least one attendee or delete it from your cart. Remove this item from your cart
Attention
For Conference Single Day – Tuesday, please make sure to select at least one attendee or delete it from your cart. Remove this item from your cart
Attention
For Tuesday Evening Reception Only, please make sure to select at least one attendee or delete it from your cart. Remove this item from your cart
Attention
For Conference Single Day – Wednesday, please make sure to select at least one attendee or delete it from your cart.
Not sure what changed between yesterday and today…
How can I set it up so they don’t have to remove non-selected items from the cart?
It turns out that if an item is in the cart, it either needs to be selected or removed. It may be better to let the attendees select what options they want instead of automatically adding all of them at once to the cart.
If you go into the Event Espresso>General settings there is an option to set “Fancy Email Headers” which will change the from line to what is set in the above Organization settings.
Viewing 2 reply threads
The support post ‘Problem configuring go to cart shortcode’ 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.