Support

Home Forums Event Espresso Premium use of shortcode [RECIPIENT_EDIT_REGISTRATION_LINK]

use of shortcode [RECIPIENT_EDIT_REGISTRATION_LINK]

Posted: October 15, 2020 at 9:19 am


channingstrom

October 15, 2020 at 9:19 am

Some reactions to the use of this link:
1) the link allows the one time opportunity for a registrant to make changes to what event they’re coming to (registrants using the user login feature is turned off). When they make a change, the old tickets disappear instead of remaining and showing ‘cancelled’ like moving a ticket. So lacks the history. Not all bad, just a little disconcerting when I’m used to being able to see where we’ve originated from after a move.
2) Have tried to send this code to the primary purchaser/registrant only. This does not appear to work well in my limited experience. It appears that all registrants under the primary purchaser cannot be moved at once – so starts a confusing and non intuitive path for the customer/primary registrant. Is this code intended to be sent to all registrations? If so, to be able to use in my ticketing situation, I need to understand some workarounds I think.
3) I experienced a glitch I couldn’t get past – an email match error that matched but told me it didn’t. (copied and pasted an email address from one registrant to another in refilling out the form) So wasn’t able to get to the next page to confirm schedule.

Is any of the above known/common?
This is an excellent feature and I’d be glad to help work through/attempt to replicate the issues I had if it helps.


Tony

  • Support Staff

October 16, 2020 at 4:13 am

Hi there,

1) the link allows the one time opportunity for a registrant to make changes to what event they’re coming to (registrants using the user login feature is turned off).

That link shouldn’t allow the user to change the ticket selection, its for editing the registration details on the reg form.

When they make a change, the old tickets disappear instead of remaining and showing ‘cancelled’ like moving a ticket. So lacks the history. Not all bad, just a little disconcerting when I’m used to being able to see where we’ve originated from after a move.

The above link shouldn’t ‘move’ anything, and I think it ties in with how you are using it above, can you provide the steps you ate taking here, please?

2) Have tried to send this code to the primary purchaser/registrant only. This does not appear to work well in my limited experience. It appears that all registrants under the primary purchaser cannot be moved at once – so starts a confusing and non intuitive path for the customer/primary registrant. Is this code intended to be sent to all registrations? If so, to be able to use in my ticketing situation, I need to understand some workarounds I think.

The primary registrant is considered by Event Espresso to be the registrant that is managing the group, so if you send the link to the Primary Registrant they should be able to edit all of the registrant details they provided in the beginning.

If you send the link to a specific registrant, they should be able to edit ‘their’ details on the registration form.

3) I experienced a glitch I couldn’t get past – an email match error that matched but told me it didn’t. (copied and pasted an email address from one registrant to another in refilling out the form) So wasn’t able to get to the next page to confirm schedule.

EE doesn’t have a ‘confirm match’ check, it does has a ‘reject match’ check though.

Meaning if you input registrant details for a user that exists on your site with their own user account it will reject the registration and tell you that user needs to log in.

If you wish to disable that you can use a snippet like this:

https://gist.github.com/joshfeck/1131145859a3fab58f4d#file-disable_email_match_everyone-php

But not that registrations made for those users will not show in their EE ‘my events section’ unless they were logged into their account.

You must be logged in to reply to this support post. Sign In or Register for an Account

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3 Documentation for Event Espresso 4

Status: publish

Updated by  Tony 1 week, 3 days ago ago

Topic Tags

Notifications

This topic is: not resolved
Do NOT follow this link or you will be banned from the site!
[gravityform id=80 title=false description=false ajax=false]
<div class='gf_browser_unknown gform_wrapper' id='gform_wrapper_80' ><form method='post' enctype='multipart/form-data' id='gform_80' action='/topic/use-of-shortcode-recipient_edit_registration_link/'> <div class='gform_body'><ul id='gform_fields_80' class='gform_fields top_label form_sublabel_below description_below'><li id='field_80_1' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_1' >First name<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_1' id='input_80_1' type='text' value='' class='medium' aria-required="true" aria-invalid="false" /></div></li><li id='field_80_2' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_2' >Email address<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_email'> <input name='input_2' id='input_80_2' type='email' value='' class='medium' aria-required="true" aria-invalid="false" /> </div></li><li id='field_80_3' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' >GDPR Agreement<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_checkbox'><ul class='gfield_checkbox' id='input_80_3'><li class='gchoice_80_3_1'> <input name='input_3.1' type='checkbox' value='I consent to have this website store my submitted information so they can respond to my inquiry.' id='choice_80_3_1' /> <label for='choice_80_3_1' id='label_80_3_1'>I consent to have this website store my submitted information so they can respond to my inquiry.</label> </li></ul></div></li><li id='field_80_4' class='gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_4' >Email</label><div class='ginput_container'><input name='input_4' id='input_80_4' type='text' value='' autocomplete='off'/></div><div class='gfield_description' id='gfield_description_80_4'>This field is for validation purposes and should be left unchanged.</div></li> </ul></div> <div class='gform_footer top_label'> <input type='submit' id='gform_submit_button_80' class='gform_button button' value='Download Now' onclick='if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} jQuery("#gform_80").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_80' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='80' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_80' value='WyJbXSIsIjBiNjdjZjkyMDUzOWUxOWY5Y2NiZjIwMzM4YjA1Mjk4Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_80' id='gform_target_page_number_80' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_80' id='gform_source_page_number_80' value='1' /> <input type='hidden' name='gform_field_values' value='' /> </div> </form> </div><script type='text/javascript'> jQuery(document).bind('gform_post_render', function(event, formId, currentPage){if(formId == 80) {} } );jQuery(document).bind('gform_post_conditional_logic', function(event, formId, fields, isInit){} );</script><script type='text/javascript'> jQuery(document).ready(function(){jQuery(document).trigger('gform_post_render', [80, 1]) } ); </script>
[i]
[i]