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
Editing database to move attendee to a different event | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Editing database to move attendee to a different event

Editing database to move attendee to a different event

Posted: February 7, 2013 at 1:47 am

Viewing 2 reply threads


Lucinda Dalrymple

February 7, 2013 at 1:47 am

I was looking in the support forum for info on how to easily move an attendee from one event to another and found this topic: Best way to move attendees from one event to another.

That looks like a good solution until the add-on for this is ready.

My question is this: Can/should I change the Registration ID too, so that the first digit matches the Event ID? Will it hurt anything if I do? Will it help? Does it matter?

Thanks for your help!


Dean

  • Support Staff

    •

February 7, 2013 at 4:15 am

Hi,

No just change the event_id, you can leave the registration_id alone.

The registration_id affects other tables in the database including but not limited to the answers and multi event registration tables.

So I think it is best left untouched.


Lucinda Dalrymple

February 7, 2013 at 8:26 am

Excellent!

Thanks for you quick and helpful response — as always.
Viewing 2 reply threads

The support post ‘Editing database to move attendee to a different event’ 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 Lucinda Dalrymple 12 years ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server