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 Surcharges displaying incorrectly | Event Espresso - Staging Server
WordPress Version: WordPress 3.5.1
Event Espresso Version: Version 3.1.30.7P
Every time there is an update to either WordPress or EE, I install it. There have been multiple EE updates over the past few weeks.
Website link to event: http://www.cpnaz.com/event-registration/?ee=3
I have been running EE for several months now, though its only been free, demo events that I’ve set up to test previously. Yesterday I set up my first, paid event and then attempted register, but ran into a problem with the surcharges.
I created the event with three different event pricing options: (1) non-food vendor ($25 fee + $0.76 surcharge), (2) food vendor ($100 fee + $2.56 surcharge), and (3) sample vendor ($0.00 fee + $0.00 surcharge). The latter was added simply to allow me to test the registration. I verified all the amounts and clicked “update”. However, when launching a separate browser to perform the registration (I didn’t want to be logged in and get member pricing) the first two options show up OK, but the “sample vendor” shows a $2.56 surcharge.
Again, I went back and verified that I had typed in the right amount, but it’s still incorrectly displaying a surcharge for one of my three items. What needs to be done to fix this?
It looks like it is an issue with having a surcharge set to 0 and having WP User Integration active.
I will get a ticket raised to look into this. Right now the options would be to turn off WP User Integration or make sure the surcharges are all above zero.
I need to be able to charge a surcharge, which offsets the exact fee that PayPal charges my organization. So for now I will disable the WP User Integration. However, as I’m sure you know, this isn’t a good long term solution, so I would appreciate an update after you’ve had a chance to review and resolve this. Thanks.
I understand completely, as mentioned I have a developer ticket in place for the developers to review and resolve. I can’t guarantee an individual response back to you directly, but if you monitor the change log when an update becomes available it will advise what has been updated, fixed and added.
Viewing 3 reply threads
The support post ‘Surcharges displaying incorrectly’ 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.