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 TIP - Pretty Unique Event Identifiers | Event Espresso - Staging Server
Normally, EE adds a lot of extra digits like “myUEI-2-52ce26434f171If” to a UEI of “myUEI”. I read a support forum post about the issue http://staging.eventespresso.com/topic/edit-unique-event-identifier/ and I wanted to let everyone know what I discovered. If you import your events, EE will not add all that extra code. Everyone in Support says we don’t need the UEI but why is the Shortcode generator button available then? Of further note, if you fail to include a UEI in your import CSV, no UEI is displayed. Of course that is a absolute minimum field requirement so I couldn’t have possibly forgotten a few in my test runs. Oops!
Just wanted you to know I just signed up for VIP. Thought I’d try to be an active participant with a few Tips and Bug Reports, I have discovered. Of course Help is always nice when I need it.
Only had EE for a couple days. Took forum advise and switched from GoDaddy to BlueHost, too.
Thanks for the tip! I’m sure it help help out the community.
The UEI is very underused from an Admin point of view though it is used in some areas by the plugin itself, so for most use case situations it can be safely ignored.
Viewing 2 reply threads
The support post ‘TIP – Pretty Unique Event Identifiers’ 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.