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
Multi User Profile Event (Pay/no Pay) | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Multi User Profile Event (Pay/no Pay)

Multi User Profile Event (Pay/no Pay)

Posted: October 21, 2012 at 6:50 pm

Viewing 1 reply thread


Adam DaCosta

October 21, 2012 at 6:50 pm

I am creating an event that consists of 3 attendees.

  1. Sponsor – required to pay a sponsorship fee
  2. Attendee – Free to attend
  3. Partner – required to pay a partner fee

Is there any way of accomplishing this? Your help is greatly appreciated, thank you. AD


Dean

  • Support Staff

    •

October 22, 2012 at 3:18 am

Hello Adam,

The simplest way would be to add more price options to an event, therefore allowing the customer to select the correct one. Obviously that would mean the customer needs to know which one they are to select.
Viewing 1 reply thread

The support post ‘Multi User Profile Event (Pay/no Pay)’ 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 Dean 12 years, 3 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server