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 Wrong price displaying on payment page | Event Espresso - Staging Server
I have multiple prices setup for an event but once the user registers, the payment page defaults to the first pricing option.
I am not running the user/members add-on and I have the latest versions of EE installed. I am using custom templates and really just need someone to point me to where I can fix the $total_cost/correct price option on the payment page. Maybe the selected price option is not posting when the form is submitted?
Customers end up getting registered and pay for the first price option regardless of their selection.
Are they custom templates that were derived from older versions? If so, which templates? You might have a copy of an older template that is using the older pricing functions that were used in prior versions of Event Espresso.
Full logging shows the first option in the price dropdown always being selected even after I verified the second option was selected when submitting a registeration.
I have done a deep comparison of all the template files and I’ve updated my custom ones with the proper updates. They still default to the first price option through registration.
Thanks for checking out the files in /wp-content/uploads/espresso/templates. Are there any files in /wp-content/uploads/espresso/gateways from a prior version? Also, are there any custom functions that were added?
Have you tried temporarily switching to the default templates and gateway files instead of overriding them with your custom ones?
I found the issue. Some javascript was modifying the form.
Thanks for the help!
Viewing 8 reply threads
The support post ‘Wrong price displaying on payment 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.