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 Duplicating Payment Options (or a better solution!) | Event Espresso - Staging Server
Espresso includes payment options for Purchase Order and Cash Transfer – but neither in their default state covered what I needed which is essentially to attach an invoice. So to cover both I have chose Invoice Payment which allows people to download an invoice. Accept now I really need two options for this to cover Cash Transfer and PO.
I’m assuming I can just duplicate the necessary files in the ‘gateways’ folder – but how would I have them appear as two options in the back-end?
Duplicate the files will not work because you’d end up duplicating functions, which would then throw fatal errors because functions can not be declared twice.
What would work is to activate all three options, but set the invoice payment option to not display on the payment overview page. Then if you place the [invoice_link] email shortcode in the registration confirmation email they can download an invoice.
Another thing you can try is copy the section of code that displays an invoice link from /gateways/invoice/invoice_vars.php into the other two gateways x_vars.php files where you want a download invoice link to be displayed.
Viewing 3 reply threads
The support post ‘Duplicating Payment Options (or a better solution!)’ 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.