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 Removing Credit Card Info section on Reg Confirmation page | Event Espresso - Staging Server
Is there an “easy” way to hide the credit card info section on the Registration Confirmation page if the customer has selected (on the initial registration page) a non-credit card payment option like “Check / Money Order” or “Cash”?
Hoping that there is a setting in the EE dashboard, but if not, then looking for some guidance as to where I would need to change the code.
Hey, sorry about the late reply. What do you mean that the customer has selected “on the initial registration page” a non-credit card payment option? It’s not possible to select a payment option until the payment page, so I’m assuming what you’re trying to do is use a custom question to select the payment method. If that’s the case, no, it’s not possible to do that because there is no correlation between custom questions and payment gateways. What you are describing wouldn’t be “easy” either to develop or to customize.
Viewing 1 reply thread
The support post ‘Removing Credit Card Info section on Reg Confirmation 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.