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
Incorrect surcharge being added to ticket option on booking page | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Incorrect surcharge being added to ticket option on booking page

Incorrect surcharge being added to ticket option on booking page

Posted: January 22, 2013 at 5:08 pm

Viewing 1 reply thread


ijorgensen

January 22, 2013 at 5:08 pm

I’m currently having an issue where on the booking form it is displaying tickets that have a $0 surcharge/fee as having a $N surcharge/fee (where N equals another ticket’s surcharge/fee). All information has been entered correctly in the WP Admin section (also note that in the General Settings for EE that the surcharge is set to $0):
The tickets available for booking/purchase and their price information in WP Admin

When a user views the booking form, these are the tickets available:
A select drop-down input showing the two available tickets to book, the Bank Transfer option having a surcharge when it shouldn't

After they’ve selected the ticket and proceeded, this is the confirmation page displaying the total amount they’re committing to purchase:
The total cost presented to the bookee for them to confirm their booking with


Josh

January 22, 2013 at 5:17 pm

Thanks for reporting this. It looks like it’s an issue with the Members add-on.

I’m going to create a ticket so the dev team is aware and they’ll fix it.

Viewing 1 reply thread

The support post ‘Incorrect surcharge being added to ticket option on booking 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.

Event Espresso - Staging Server