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 Id # vs ID # - need shortcode for shorter # | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Registration Id # vs ID # – need shortcode for shorter #

Registration Id # vs ID # – need shortcode for shorter #

Posted: September 9, 2013 at 12:18 pm

Viewing 1 reply thread


abaldwin

September 9, 2013 at 12:18 pm

When I look at the top of the “Edit Attendee Data” page, I see the following:

Registration Id #26-522df519cee1d | ID #566 | Name: …

I want to use that ID #566 as the registrant’s ID #, but I cannot find the shortcode to include that in the Confirmation Email. Our registration process is already live, so I’m scared to mess around too much with it, trying to guess what it might be. Can you help?

Thanks!


Sidney Harrell

  • Support Staff

    •

September 9, 2013 at 2:31 pm

There isn’t one built in. You can open up includes/functions/email.php and go to line 8 and add the following line so that it then reads:

$SearchValues = array(
"[attendee_id]",

then go down to what will then be line 59 and add the following line so that it then reads:

$ReplaceValues = array(
$data->attendee->id,

this will add the shortcode [attendee_id]
Viewing 1 reply thread

The support post ‘Registration Id # vs ID # – need shortcode for shorter #’ 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.

The original Forum description...

Status: closed

Updated by Sidney Harrell 11 years, 4 months ago ago

Topic Tags

Tagged: , , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server