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 Formatting issue with registration confirmation page + pay at door | Event Espresso - Staging Server
Issue 1: Formatting problem when confirming price, time, etc, payment. See below image. Where exactly is this block coming from, and how do I get rid of it?
Issue 2: I’ve been fiddling around trying to find a solution to the “Pay at the Door” problem. I’ve changed the Check/Money Order settings as you can see in the below image, but the warning below still describes check and/or money order payment. Is there a way to change the text in the warning? (I’ve not found it yet.) Having a simple pay-at-the-door solution (and a smoother way for multiple people to pay multiple prices, as in adults and kids coming together when the event charges less for young’ns) seems a little obvious, surprised it isn’t easier in EE.
It is the background rule which is causing the grey box. This is used to style your navigation menu but as EE is also using a class of .header it is applied here also.
I would recommend changing the selector of that rule-set to
To alter that text you need to edit event-espresso\gateways\check\check_payment_vars.php line 60.
I would recommend copying the whole ‘check’ folder to wp-content\uploads\espresso\gateways and editing the file there, this will stop EE updates replacing your customized file.
Thank you for your feedback, both those issues are something we are working on improving as much as we can.
Regarding multiple prices you can use the Multi Event Registration Add-on to allow you to add multiple ticket prices to a ‘cart’ and then check those tickets out in one transaction.
Viewing 1 reply thread
The support post ‘Formatting issue with registration confirmation page + pay at door’ 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.