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
With WP user the additional ticket purchase attendee name fields are locked | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium With WP user the additional ticket purchase attendee name fields are locked

With WP user the additional ticket purchase attendee name fields are locked

Posted: November 12, 2013 at 9:48 am

Viewing 3 reply threads


Nicholas

November 12, 2013 at 9:48 am

I added WP user as the membership site I’m working wants logged in users to get free tickets to events but anyone else has to purchase them. I populated the member ticketing fields and it works fine with an instant checkout. But when the logged in user buys two tickets all the personal information fields are pre-populated with the name/email and can’t be edited.

Using the clear field does clear them but a locked symbol appears. How can I capture attendee info for additional tickets?

Thanks

  • This topic was modified 11 years, 2 months ago by Nicholas.


Anonymous

November 12, 2013 at 10:28 am

Hi Nicholas,

If you go to Event Espresso -> Member Settings you should find the option ‘Make autofilled fields editable?’ set this to Yes and click ‘Save Settings’.

This should allow you to edit those fields.


Nicholas

November 12, 2013 at 10:31 am

Perfect thanks…now that option seems to make sense!


Anonymous

November 12, 2013 at 10:46 am

No Problem.

Viewing 3 reply threads

The support post ‘With WP user the additional ticket purchase attendee name fields are locked’ 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.

Event Espresso - Staging Server