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 Autofill members only made by hostes | Event Espresso - Staging Server
Event Espresso doesn’t have that functionality. Can I ask how you’d want this to work? Would the Hostess create the profile as a WordPress user? Then is the host adding the attendee on the front-end or in the WordPress admin?
Yes the idea is that the hostess will do the reservation in the name of the member, so its too slow if the hostess logs in and out very time, so if the hosts could load members info and the system autofills the member info, in order to expedite the reservation.
That’s a great suggestion, but probably not something very easy to do in EE3. Plus, we’d have to consider the load it might put on a server given the fact that it has to try and filter live results based on names. This might be something we could look into for a later version of Event Espresso 4 if you could consider contributing to it (http://staging.eventespresso.com/about/philosophy/#sponsored-development), otherwise we’ll add it to our list of feature requests.
The support post ‘Autofill members only made by hostes’ 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.