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 Customising the date on the payment confirmation email | Event Espresso - Staging Server
Are you able to advise how to customise the date on the table that lists on the payment confirmation email [attendee_event_list] so that is only shows one date?
Currently it lists the date as 23/07/2013 – 23/07/2013 and feedback from clients says it’s causing confusion having the event start date and end date when they are both the same. Presumably the end date needs to be inserted into the event details but is it possible to only display the event start date on the payment confirmation email, as it does when selecting the number of tickets when purchasing.
The email that gets sent out can be modified. What you can do is go into Event Espresso>General settings under email settings. The first email editor that appears is for the Payment confirmation email. You can remove the [end_date] shortcode from the message template and save the settings.
The default registration confirmation email to the attendee looks like this in the General Settings – http://d.pr/i/8r1r
As you can see the start/end times are shown like this
This event starts at [start_time] on [start_date] and runs until [end_time] on [end_date].
So unless the email has been modified there or in the Email Manager or in the event itself, it is possible that your client is referring to the Admin email, which does show the dates like so http://d.pr/i/7M5j
Unfortunately in 3.1.X the Admin email can only be modified by editing a core file, which we dont recommend, this will change from version 4.0 onwards.
Viewing 3 reply threads
The support post ‘Customising the date on the payment confirmation email’ 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.