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
Attendee and existing user matching | Event Espresso - Staging Server

Support

Home › Forums › WP User Integration › Attendee and existing user matching

Attendee and existing user matching

Posted: November 4, 2013 at 3:21 pm

Viewing 1 reply thread


Laurent van der Straten

November 4, 2013 at 3:21 pm

Hi,
Is There anybody who get a solution to match existing users with attendee?

Thanks


Anonymous

November 5, 2013 at 6:07 am

Hi,

Unfortunately there’s no easy way of doing this currently.

The wp_events_member_rel table stores information to collate ‘users’ with events. You’d need the event_id, user_id, user_role and attendee_id from various locations and then collate the information together.

Using phpMyAdmin or equivalent you could search the attendees table to find the attendee information, you’ll need the right attendee_id based on a completed transaction and the event ID’s for the attendee (as some attendees will be registered on more than one event) then search the wp_users table to get the user_id (based on email)
Viewing 1 reply thread

The support post ‘Attendee and existing user matching’ 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.

This is a meta description test for the WP User integration.

Status: closed

Updated by Anonymous 11 years, 2 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server