|
markolson68
|
May 10, 2023 at 10:36 pm
I offer half a dozen courses using EE. Some of them occur over a number of days. I’ve recently decided to allow participants to register for each day separately. So my X class now has X1, X2, and X3, and each month I offer each of these on two separate days so that people can mix and match to get all three in whatever way is best for their schedule. I was hoping there would be a way that I could list the X class and within that sell tickets for all 6 classes for that month (or even more across multiple months), as this would allow students to buy their preferred 3 days at once. but the date/time field makes that not work since it applies to every ticket. The alternative is to make a new event for each day, but that would be a lot of events and more importantly would require people to make separate purchases for each event.
Is there any way that I can do this so that people can signup for multiple days at the same time? Or any better solutions to this? Is there any way to do it so I could sell a set of days at a different price than the sum of individual days?
|
|
markolson68
|
May 11, 2023 at 7:32 am
I think I see how to do it with the advanced settings.
Two things come up:
1. Is there a limit on how many tickets can be set up per event…..it appears that there’s a limit of 16.
2. Is there a proper way in the advanced settings section to assign date times to tickets? I did a bunch of assigning, and then I duplicated date times and tickets, and when I went back to reassign things, it would often tell me that I couldn’t remove a ticket from a date time because the ticket would be left without a date time, but in most cases this wasn’t true–the ticket DID have date times assigned to it…and often many of them. I also noticed that every time I would update the event, all of the tickets would have all the date times unchecked. The date times would have tickets checked, but not the other way around. Is it supposed to do that?
|
|
Tony
|
May 11, 2023 at 9:06 am
Hi there,
So I assume you are creating multiple ticket options for this and assigning them to individual datetimes within a single event? (That is the way you would need to configure this so just checking)
1. Is there a limit on how many tickets can be set up per event…..it appears that there’s a limit of 16.
No limit within Event Espresso itself… but, you are likely hitting your server max_input_vars value (the number of inputs on a page that will be processed before the server ignores the rest).
Now, with the rest of your reply it sounds like you are using the legacy editor and one of the reasons we re-wrote the event editor in EE5 was to work around the max_input_vars issue above (amongst other things) so I’d advise switching to the Advanced Editor.
Go to Event Espresso -> Events -> Default Settings -> Activate Advanced Editor?
Select Advanced Editor.
Now try editing your event, you should see the new editor which should allow you to do the above.
|
|
markolson68
|
May 11, 2023 at 9:14 am
Advanced Editor…got it. Thank you. The whole time I was thinking “I thought I read that they updated this to make it easier, but it sure seems the same to me”.
|
|
markolson68
|
May 11, 2023 at 9:32 am
Is there a way to move the items into a particular order like there was in the legacy editor?
|
|
markolson68
|
May 11, 2023 at 9:43 am
If I have Part 1 on Sept 1 and Oct 1, Part 2 on Sept 2 and Oct 2, and Part 3 on Sept 3 and Oct 3, and all of these items are the same price, would I make 1 ticket or 6 tickets? Would be great if it could just be the 1 and then the registrant indicates which date they are attending, but I’ve been assuming that I have to make a separate ticket for each.
I’m a little confused about the advanced editor. In the legacy editor, I was given an option to make a ticket each time I made a date time. But in the advanced editor it seems like I have to make the ticket first so it will be available to select when I make the date time. This seems more difficult, but maybe I’m missing the key attributes that make the advanced editor easier.
|
|
markolson68
|
May 11, 2023 at 9:49 am
In the advanced editor I am unable to make date times or tickets. The date time editor won’t let me create a date time unless I select a ticket to go with it. The ticket editor won’t let me create a ticket unless I select a date time to go with it. So there’s no way to create either unless I assign things to old items just to get it created and then go back later and adjust it, but that is definitely not easier.
|
|
Garth
|
May 11, 2023 at 10:16 am
Is there a way to move the items into a particular order like there was in the legacy editor?
In the New Editor:
– Go to Tickets
– Click Show Filters
– Click Set Custom Tickets Order
– A new panel will open where you can drag and drop tickets in to order.
Tip: I usually remove all filters (e.g. upcoming or active, etc.) so that all the tickets are displaying before I try to put them in a custom order.
would I make 1 ticket or 6 tickets?
You have options. You can create one ticket that has access to all those datetimes, or a ticket for each datetime, your choice. You simply need to edit the ticket or datetime and associate which ticket/datetime is assigned to the corresponding ticket/datetime.
I’m a little confused about the advanced editor. In the legacy editor, I was given an option to make a ticket each time I made a date time. But in the advanced editor it seems like I have to make the ticket first so it will be available to select when I make the date time. This seems more difficult, but maybe I’m missing the key attributes that make the advanced editor easier.
Correct. We’re planning ways to try and make it easier to add a new ticket with a new datetime. But for now you will need to create a new ticket/datetime and associate that with an existing ticket/datetime, then create the new corresponding ticket/datetime and go back an unassign the old ticket/datetime and assign the new ticket/datetime.
|
|
markolson68
|
May 11, 2023 at 10:24 am
So with the advanced editor, if one is starting from scratch with no tickets and no date times, then there’s no way to begin unless one goes back to legacy, correct?
I understand that I can assign tickets to one or more date times. My “1 or 6” question is in regards to two goals: 1. to make setting up as simple as possible (one ticket for all things that are the same price) 2. Knowing which people are registered for which datetime. If I make just 1 ticket, will I lose the ability to know which date time a person is attending (i.e. do they get to select the date time after they select the ticket or would I just get a notification that they purchased the ticket but have no idea which date time they are going for?)
|
|
Garth
|
May 11, 2023 at 10:41 am
So with the advanced editor, if one is starting from scratch with no tickets and no date times, then there’s no way to begin unless one goes back to legacy, correct?
No, because each event begins with an initial datetime and ticket.
I understand that I can assign tickets to one or more date times. My “1 or 6” question is in regards to two goals: 1. to make setting up as simple as possible (one ticket for all things that are the same price) 2. Knowing which people are registered for which datetime. If I make just 1 ticket, will I lose the ability to know which date time a person is attending (i.e. do they get to select the date time after they select the ticket or would I just get a notification that they purchased the ticket but have no idea which date time they are going for?)
The way you set up the tickets will depend on how you gather data. You will have to choose which competing priority to favor. If you choose one ticket, then everyone registering will be in included in every datetime. If you choose multiple tickets, then people will only be included for the tickets (and associated datetime) that they chose. People do not choose a ticket and then a date. The purchase/registration process choosing a ticket and date(s) are done in one step, not multiple steps.
|
|
markolson68
|
May 11, 2023 at 12:47 pm
I have been unsuccessful in getting the tickets to display in the custom order that I specify. I click the “reorder” button and then drag them around in the new window but none of those changes stick. the moment i’m out of that window, the list is the same as what it was. updating the file doesn’t change this. the order it defaults to is not by ID or date or name, so it’s weird the sequence that it chooses and that it doesn’t keep the changes.
|
|
markolson68
|
May 11, 2023 at 1:37 pm
I deleted all of my tickets where the “taxable item” box wasn’t present and I redid everything thinking that this was the only way to fix this. I made sure that every ticket I was making had that box and I checked it. Each ticket was calculating the correct total with the tax. And now, all of these tickets are missing the ‘taxable item’ box and there’s seemingly no way to get it back.
I am also not having any success in getting ticket items to list in the order that I specify. I got it closer by doing it in legacy mode, but the newest items insist on clustering at the bottom.
|
|
markolson68
|
May 11, 2023 at 1:40 pm
All of the last tickets I made have replaced the ‘taxable item’ with “Percent Discount” and is actually taking the tax % and discounting the items. I never once selected percent discount at any time. I didn’t even use that menu.
|
|
markolson68
|
May 11, 2023 at 1:43 pm
One possible hint to the problem is that the items that stayed in the custom order I specified are the ones that applied a discount. The ones that insisted on staying at the bottom kept the correct pricing. This is for the user display. On the backend, all of them are missing the ‘taxable item’ box.
|
|
markolson68
|
May 11, 2023 at 2:17 pm
I just had a customer register for a course and it didn’t apply the tax. This is for an event that I have NOT changed since the last person registered and it DID apply the tax. The tax is not showing anywhere on the front or back end and there’s no option to select it anywhere. In the settings, I have ‘yes’ selected for choosing to show a tax but there is no longer a place to set the tax anywhere within the plugin.
|
|
markolson68
|
May 11, 2023 at 5:22 pm
I fixed the tax issue. The default tax item had been deleted. This is concerning because it got deleted out of nowhere. I didn’t even go into those settings prior to it being deleted.
I keep making tickets that span multiple date times and those tickets will disappear if I make them in the legacy editor, even though the legacy editor is the only one where I can assign the tickets to the date times. In the advanced editor, I keep getting messages that some tickets don’t have date times assigned to them, even though all of them do. It will bring up a table with tickets along the top and date times on the side, and all of them are checked…but it won’t let me submit it.
|
|
Garth
|
May 16, 2023 at 9:51 am
If you want us to take a look, you can give us access here:
http://eventespresso.com/send-login-details/
Please point out which ticket(s) are still doing that?
|
|
markolson68
|
May 16, 2023 at 10:00 am
At this point, I have it working. I have no idea how some of these various issues actually got resolved, and I’m not confident that I wouldn’t run into the same problem again. There remain various mismatches between whether tax is applied or not–in many cases it applies the tax even though the payment section doesn’t indicate that it will be doing so. So many weird things like that I can’t keep them straight, but it works. Perhaps it’s best I start a new thread if it becomes a problem again.
|
|
Garth
|
May 16, 2023 at 10:03 am
Switching from the legacy to the new editor can be tricky, and we do think there was a bug in the process. So, let’s keep an eye on it.
|
|
markolson68
|
May 16, 2023 at 10:06 am
If I make new events, or new date times, or new tickets, is there any basis for thinking that will go better if I start new rather than duplicate something made in legacy mode? Or should that not matter?
|
|
Garth
|
May 16, 2023 at 12:42 pm
Yes, it may make a difference if you start with the new editor compared to starting or using the legacy editor.
|
