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 Allowing Registrants to Edit Their Own Registration Details | Event Espresso - Staging Server
My organization is currently looking to transition from RegOnline to a WordPress event registration solution. One of the features we have used extensively is the ability for registrants to login and edit their own registration details. Is this possible with Event Espresso? Thanks in advance for your help!
Thanks for your question. This is possible with Event Espresso, but it works differently in that users do not log in to edit their registration details. Instead, they can click a link that’s in the confirmation email they get after registering that will take them directly to a page where they can edit their registration details.
I experimented with this feature in the Test Drive, and it seems to work well. Is there any security risk with this editing capability not being password protected?
I don’t claim to be a security expert, but I don’t see a risk with that. Someone wanting to edit someone else’s attendee info would need to know the page ID of the registration page, the ID of the event, the 18 digit unique registration ID, and the simple registration ID then string that all together to get that URL. If you’re one character off, it sends you to an error page.
In the past people have asked how to shorten the registration ID and make it follow a sequence. I’d say that by keeping the registration ID at a longer length and randomly generated keeps that URL from being harder to guess.
Viewing 3 reply threads
The support post ‘Allowing Registrants to Edit Their Own Registration Details’ 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.