Support

November 24, 2017 at 12:56 pm

Hi Laura,

May I ask is there something specific about the checkout page you’d like to change?

If the whole thing looks awful you might consider clicking on the Customize button and previewing some other themes to see it that makes a difference.

Please feel free to start a new topic or add a reply here with your question about the pricing and we can help you with that too.

November 24, 2017 at 4:52 pm

The theme is indeed causing the formatting problem. Do you see how all of the required fields aren’t displayed? That’s the theme’s CSS kicking in and preventing them to display. You can override the theme’s CSS with the following:

input:invalid{
outline-color: currentColor;
outline-color: invert;
outline-style: none;
outline-width: medium;
border-width: 2px;
border-color: initial;
border-style: inset;
}

input[type="text"],
input[type="datepicker"]
{
min-height: 45px;
font-size: 1.5em;
}

The above will only go so far (the select inputs need CSS help too). Maybe the theme support staff can help with that part? If not, I can recommend some other themes. You’ll see an example of a nicely styled registration form on this testing site (it uses the Munsa lite theme):

REMOVED

I will be having multiple corporate sponsors that will purchase multiple teams of 4 people on each team for $3000 each team, and each team member will have to be registered in the system to receive a badge for the event. The way I have it set now is not working. Do you have any suggestions as to a way this could be set up to work?

You can set up a ticket bundle (4 for $3000) by following this guide:

https://eventespresso.com/wiki/create-ticket-bundle/

November 29, 2017 at 8:59 am

I’ll follow up with each of your questions below:

In making the guide a required ticket, Can you make it required only for certain types of tickets?

No.

All of these tickets will be requiring a badge to enter the facility as well. So, if I understand how this works, they will have to have a ticket (either free or paid) to be entered into the database that I will later get the CSV file from to send off for printing badges. Is this correct?

What’d I’d recommend is you make a copy of the event, then do some test registrations on that test event. Then you run the CSV registration report from the Event Espresso > Registrations page and check that report to make sure it has what you need for the badges.

Would it be best to set these different ticket types up as different events?

I think you’ve already made the conclusion that this would not ideal, and I agree with that.

I also just thought about the different bundles you were speaking of for the teams. Is there a way to have more than the one mandatory guide for each of the teams if it were done this way? hmm… Maybe we make a free ticket for “Team Guide” with the description “Anglers are allowed one free guide for each team of four purchased. Please make sure to select a guide for each team to register them for entry into the event.” I could also place something along these lines in the description for the the Team tickets. What are your thoughts on this method?

I think that would work well, and with a bit of custom jQuery added to the page, you’d be able to enforce the quantity selection of guides. Technically speaking, that would involve adding an event listener to the ticket selector’s quantity fields to watch for the selections and automatically update the guide ticket quantity. For example if someone selected 8 tickets from the 2 team fee row, then the Free Guide option would automatically get set to be 2. If you need help with setting up that custom jQuery I can put together a code example for you.

I am also curious about the discounts I’ve seen under the “Price Types” tab in the “Event Espresso – Pricing” area. Since the Sponsor/Anglers are receiving a discount of $400 on the Anglers, perhaps we could show this as a discount? Is this what they are for and, if so, how do I implement them?

You don’t actually directly set those up within the price types, what you can do is set up a discount price modifier for each of those tickets within the ticket editor. How that works is you set the full price in the ticket price field, then input the discount amount in a price modifier. The end result price will be the same, but they’ll have the opportunity to see the discount amount in the ticket details.

Also, one other problem I’ve noticed on the Team ticket is that the purchaser has the ability to add more tickets at the lower bundle price. This will not be an available option. They would have to purchase an additional Angler ticket at a higher price if they want to add an Angler to a team. Is there any way to turn off the ability to add tickets in this manner?

You’ll need to deactivate the Multi Event Registration add-on to prevent that from happening.

November 29, 2017 at 10:08 am

I have never done any alterations with the functions.php file. I assume this is where the jQuery code would have to go?

We actually do not recommend altering a theme’s functions.php file for a few reasons. Instead, we recommend adding code to a functions plugin. We’ll be more than happy to help you with putting together the jQuery code.

They may like to have the ability to send just to the Volunteer group or just to the Angler group.

If that’s the case, then the solution may be to break out the Volunteer-related registrations into their own event. This would not require the Multi Event Registration plugin. The only reason to use Multi Event Registration would be if someone volunteering was also registering for the Anglers and wanted to do that in one big transaction. Even in that case it will probably be best to keep those in separate transactions (instead of in one transaction).

November 29, 2017 at 11:07 am

A site functions plugin is not the same as a theme’s functions.php file. Generally speaking a theme’s functions.php file is best used to add functions that will be used by the theme. A site specific plugin is best used to add specific customizations that will be used by the site in general.

It’s really your choice, but again, we do not recommend putting non-theme related code functions into a WP theme’s functions.php file. It works, but it’s not best practice to put one-off code customizations that aren’t related to the theme’s functionality. There are gotchas that can happen (related to code load order and maintenance issues) when non-theme related code is packed into a theme. These and other gotchas can be avoided by keeping plugin customization related code in its own separate plugin.

December 14, 2017 at 9:59 am

They’d ideally have sone experience with PHP & JavaScript, specifically the parts related to using the WordPress plugin API & the jQuery library respectively.

The recommended approach will involve not making any direct edits to core files, and this is possible because the copy_attendee_info.template.php template can be copied over to the active WordPress plugin, then edited there. Event Espresso will check the theme for that file first.