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 Registration Summary email doesn't show amount paid | Event Espresso - Staging Server
Saw an older thread from the decommissioned forum regarding the Registration Summary email (to the site owner) not showing the amount paid, and I’m having the same issue. Email shows the payment option, but not the price.
Is adding this option to the email function now supported in a way that will preserve it on update, or can it be part of the core functionality? It seems like it’s a key option for orgs with multiple pricing scenarios and more than one person handling registrations to keep the pricing straight. Thanks!
Modifying the admin email stills has to be done by a core edit, so updates would over write it.
I have already added a request for future versions to have an admin emails editable, and I believe that the next generation of Event Espresso, version 4.0 will have that ability via the brand new messaging system, making it much easier all round.
There is a Beta version available in the Pre Release section on your account page already. We are expecting to have the release version by around June if all goes well.
Feel free to download the Beta and check it out, however it is not suitable for live (production) sites, does not work with the 3.1.X database so needs a fresh install and there are no add ons available right now for it. It is a Beta!
When 4.0 is actually released there will still be limitations for a while as we bring the add ons up to date. We have effectively rewritten the plugin from scratch , so absolutely everything is being redone.
Viewing 3 reply threads
The support post ‘Registration Summary email doesn't show amount paid’ 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.