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
Split: Modifying field names and options - EE4 | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › Split: Modifying field names and options – EE4

Split: Modifying field names and options – EE4

Posted: March 19, 2014 at 12:12 pm

Viewing 2 reply threads


Lisa Fritsch

March 19, 2014 at 12:12 pm

Hi Garth,

I am interested to know before I buy if certain modifications can be made to EE4.

For instance, we don’t sell “tickets,” we sell “registrations.” I would need to modify the field to say Registration Options, not Ticket Options.

Also we don’t want a “QTY” field because we have one primary registrant who then adds additional attendees during the registration process. And it can’t be a group registration because we charge one flat fee for each registration, and that fee includes up to 4 attendees.

Thank you!
Lisa


Garth

  • Support Staff

    •

March 19, 2014 at 3:49 pm

Lisa,

Many of the front-end UI elements can be controlled and modified by creating a child theme from the templates provided. See http://staging.eventespresso.com/2014/02/developers-corner-theming-event-espresso-4/

With EE4 if you want to collect each individual as a registration then they will each need to purchase a ticket. You can set up a min/max quantity to be purchased so they can only purchase the allowed number; each ticket is priced on a per-ticket basis. See http://staging.eventespresso.com/features/multiple-ticket-pricing-options/.

Does that make sense?


Garth

  • Support Staff

    •

March 19, 2014 at 9:20 pm

You could alo create two tickets, the one for the primary registrant costs whatever $$$ and has Min and Max Qty of 1 so it MUST be purchased, then the additional attendee tickets are free and have a Min Qty of 0 and a Max of 3.

Does that also help?
Viewing 2 reply threads

The support post ‘Split: Modifying field names and options – EE4’ 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.

Status: closed

Updated by Garth 10 years, 10 months ago ago

Topic Tags

Tagged: , , , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server