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 Discrepency in naming of discount field | Event Espresso - Staging Server
If you click on a single event to register the name of the discount field is “Promo code”.
If you have MER activated and you “add to cart” then the text assigned to the discount field is named “Enter Coupon Code”.
This should be streamlined and either named the same thing or there would be a choice in the settings. I think it’s best to name it “Discount Code” as it used to be in a previous version of EE. (Yet a third naming for this field.)
Additionally the position of the discount code/promo code box is very awkward if you are a user registering for a single event but signing up multiple attendees. The promo code box sits under the first attendee’s info not at the very bottom of the screen. As a user that’s confusing. It should either be at the top or the bottom, but not in between user info.
PS–I’ve been submitting ideas/bugs that I’m finding since I just updated to the newest EE from a very old EE and I’m sifting threw new features and trying registration from a user viewpoint so I can support my customers. I’ve been a beta tester in a previous job so it’s in my nature to report issues with software. I’m not a programmer, don’t know any code, so I’m a good representation of the normal user. If you’d rather me submit this stuff off forum just let me know how.
Thanks for taking the time to leave this valuable feedback. I’ve registered your suggestion and we will keep it in mind for future features and updates!
Viewing 1 reply thread
The support post ‘Discrepency in naming of discount field’ 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.