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 too long | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Registration ID too long

Registration ID too long

Posted: August 7, 2012 at 10:54 am

Viewing 8 reply threads


Krista

August 7, 2012 at 10:54 am

Hi
I am using the premium version of EE – Version 3.1.25.P
In this version there a way to shorten the long registration ID code that the attendee will receive? How can I get the Reg ID to be a shorter number?

Thanks
K.


Seth Shoultes

  • Support Staff

    •

August 7, 2012 at 2:15 pm

You can create a custom filter (filter_hook_espresso_registration_id) to create a unique id.

Here is an example of what is there now:

//Build the registration id
function espresso_build_registration_id($event_id){
return uniqid($event_id . '-');
}

//Registration id filter
add_filter('filter_hook_espresso_registration_id', 'espresso_build_registration_id', 10, 1);


Krista

August 7, 2012 at 6:26 pm

Thanks for that… I am not too familiar with creating custom filters.
I got your example but what part do I replace? Where would I put that if I want it to start at “100” for example.

Thanks for your help…


Seth Shoultes

  • Support Staff

    •

August 11, 2012 at 4:33 pm

So you want the registration id to start with “100”?

Eg. 100-3892304 ?


Krista

August 13, 2012 at 11:45 am

Hi Seth
Yes anything shorter than what it currently is. I am back to using the Lite version at the moment but if the premium version allows this I will keep it. How do I create a filter for that?
Thanks
K.


J.P. Lepez

October 10, 2012 at 1:22 pm

Hi Seth.. Can you follow up to the answer for this? I’m in need of this solution as well and I’m stuck.


Seth Shoultes

  • Support Staff

    •

October 10, 2012 at 2:25 pm

If the registration id is too short, it could cause problems because then it will not be absolutely unique. And also make it easier for hackers to guess the registration ids and possibly steal information about your attendees etc.

If you need to use a shorter number, I would recommend using the attendee id field instead.


Seth Shoultes

  • Support Staff

    •

October 10, 2012 at 2:36 pm

You might try one of the solutions posted here:
http://stackoverflow.com/questions/307486/short-unique-id-in-php


Krista

October 10, 2012 at 3:30 pm

Hi Seth
Thanks for getting back to me… So If I use the attendee ID field? is there a shortcode for this that could be used in the confirmation email? I could not find the shortcode for it.
Thanks agian.
K.
Viewing 8 reply threads

The support post ‘Registration ID too long’ 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 Krista 12 years, 3 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server