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 Getting rid of coupon code boxes at checkout depending on event type? | Event Espresso - Staging Server
Hi again. I am wondering something. We are using EE for both an after school program and a summer program. None of the summer programs are set to accept coupon codes. However, when I try to check out the coupon code box still displays even though the events listed are set to not accept coupon codes. When I enter a code and refresh the total, the total does not change, which is good. However, I was wondering if there is a way to display the boxes only when the events are part of the after school program and not display them if the events are part of the summer program? Can you tell we go live tomorrow? :-)
That conditional check is not built-in by default and will require the assistance of a developer. We can’t help before tomorrow but I’ll create a ticket so that we can investigate adding it into a later version of EE (no promises though).
It turns out that if you were to not push all the event registration through the cart, the events that don’t have promo codes wouldn’t display promo code boxes. So if this is an important feature that you need, I can suggest making it so the standard registration isn’t disabled.
Hi Josh. I’m a bit confused. We do need all the event registration to go through the cart, I would think. Do I have the standard registration disabled? I took this site over from another developer so I’m still trying to work my way through all the particulars.
That may be the case where you need to have all the events go through the cart. One reason for doing that would be if you’re using the Volume Discounts add-on.
It does look like the single event registration has been disabled though. If you view a single event page the only thing that’s being displayed is an add to cart button. Normally Event Espresso will have a registration form that can be filled out. They may have removed the registration form code from the registration_page_display.php template, which essentially prevents someone from registering without adding an event to the cart first.
Viewing 4 reply threads
The support post ‘Getting rid of coupon code boxes at checkout depending on event type?’ 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.