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
Transfer Attendee to Different Event and keep payment records | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Transfer Attendee to Different Event and keep payment records

Transfer Attendee to Different Event and keep payment records

Posted: January 24, 2013 at 7:43 am

Viewing 3 reply threads


Shannon Bentley

January 24, 2013 at 7:43 am

Just wondering if it was at all possible to transfer or move an attendee to a different event yet? This is pretty crucial to most event planning. I wouldn’t mind re-registering people EXCEPT the problem is, all the payment details are lost and the associations with multiple events are broken by re-doing their registration or “Adding a New Attendee”


Josh

January 24, 2013 at 10:35 am

Hi there,

One of the developers was working on an add-on that we are planning on releasing for free. Once it’s ready, I’ll post an update here.


Shannon Bentley

January 24, 2013 at 2:14 pm

Awesome! Thanks Josh. :)


Seth Shoultes

  • Support Staff

    •

May 2, 2013 at 3:31 pm

The Attendee Reassignment Addon is now available in the pre-release channel.

Viewing 3 reply threads

The support post ‘Transfer Attendee to Different Event and keep payment records’ 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 Seth Shoultes 11 years, 8 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server