Posted: April 11, 2016 at 1:42 pm
|
|
Looks like a fantastic plugin, and one that might be MUCH better than my client’s existing tour/booking plugin. I do have a few questions before we decide to purchase. I’ve set up a demo site and it seems like it might work really well for us. My client runs a business that runs approximately 20 walking tours PER DAY, 365 days per year. Each tour takes up to 15 individuals through three ticket types. This creates a LOT of individual, recurring daily tours. 1) Listing 20+ tours on each Calendar day of a Calendar. I noticed that I could list zero tours for each calendar day via shortcode, and it creates a “View More” link rather than showing ALL tours for that day. Is there a way to customize that message so it says “View Tours” OR is there a way to make the calendar day be a link to the daily list of tours? 2) Loading this many daily tours is REALLY bogging down the load-time of our current booking calendar. I’m concerned that Event Espresso will be equally slow trying to load all the tours, as well. Related to Question #1: Is there a way to keep the month Calendar from loading all the tours until the customer clicks on the date they want? 3) All of our tours are paid when the customer shows up in-person for the tour so there is NO online payment at all. I see I can create and customize the Invoice payment option, which is great. But is there a way to mark all incoming reservations as automatically paid in the admin side? We don’t want thousands of “pending” payments. We want them to be marked PAID when they make their reservation, but still want it to email the customer a receipt/invoice. 4) Our 20+ daily tours are divided up into two Categories: Winter tours, which run November-February and Summer tours, which run April-October. Can we set these up to recur every year so we don’t have to go in every year and create new recurring tours for each season? Meaning: I want to set up all daily Winter Tours that will automatically reoccur every year, Nov-Feb. 5) I created a test reservation on my demo site for an hourly tour on a specific date (April 20th, 2016 at 8am, for example). This single reservation included 2 adults, 2 young children, and 1 infant. I only had to enter the contact information for ONE person … the person making the reservation, which is what I want. But in the admin area, there were FIVE separate confirmations, all with the name of the one person, under the different ticket types. Is there a way to keep ALL people attending the tour, no matter their ticket type, under ONE name? |
|
Hi GHDesgin, How are you today? I’ll break down each question as best I can.
Currently neither of those options are available without modifying the calendar core file. The ‘View more’ link is a simple text change that can be made within the espresso_calendar.js file. So you could remove the original JS file from the calendar and load your own custom version (which would just be a copy with your text change) using a custom functions plugin. However note that the events are still pulled from the database, the calendar JS counts the events and display View More. Forcing the calendar to be clickable per day would basically require a custom calendar. Event Espresso pulls the events and list the events on top of the calendar, each link take you to a specific event. You would need each day to take you to a page containing the events for that day, it sounds similar but unfortunately works completely differently.
The answer above relates to this, the short answer here is No. It would be possible, but would require the calendar be re-written.
Within the event you can set the Default Registration Status to ‘Approved’, which means every registration on that event will apply to the sold values. They will not show as ‘Paid’ as the transaction will be incomplete. But Approved registrations apply to the event regardless of transaction status, is that what you are looking for?
Currently EE4 does not officially support recurring events, which means each of those events will need to be manually created. You can duplicate events and then change the details within the duplicate but there is no automatic event create available currently. EE3 does support recurring events, it has an add-on that will basically loop over create duplicate events but adjusts the dates within those events based on a formula. However you’ve been testing EE4, which works very differently from EE3. If you need recurring events functionality I’d recommend testing driving EE3 to see if it suits your needs – Test Drive Event Espresso 3
No, a ticket has a 1:1 relationship with a registration. So each ticket will create a new registration, if you only collect the Primary Registrants details, EE will loop over the registrations using those details. You can also set EE4 to collect details for each individual user if you prefer. However just to confirm, is this just to make it easier to view within the admin? I’m just checking I understand your question correctly. |
|
|
|
Hi Tony… thanks for the great feedback. To answer your last response to my #5 question: Yes, this is really just so the admin tour management staff can view tour reservations under ONE registrant/reservation easily. Many times, customers contact our staff and ask to have their reservation changed … different tour time, add/subtract attendees, etc. If each ticket is separate and not gathered under a single tour reservation under one name, it makes this type of editing difficult. Not to mention with 660 hourly tours to manage each month, if all registrants are separate, that makes the backend/admin management even more complex. Regarding EE4 not supporting recurring events… really? Why did the previous version support and the latest not? I can understand not creating recurring events in strange time blocks like I suggested. But when you say it doesn’t support recurring events, does that also mean hourly? Meaning: If I create an 8-9am tour with 3 ticket types, maximum of 15 tickets total per tour, that runs every day from January – June, I can’t just automatically tell the system to auto-duplicate that tour within the set month parameters? If that’s the case, I’d have to create and/or duplicate by-hand almost 8,000 individual hourly tours each year! That’s a deal-breaker, for sure. Are EE3 and EE4 separate products that will both be maintained or is EE3 just an older version that will someday be phased out? |
|
|
Nevermind about my last question. I see that EE3 will eventually be phased out. When will EE4 get the recurring event feature added? |
With EE4 you currently can not move registrants from one event/datetime/ticket to another, you need to set the original registrations to cancelled and then re-create the registrations on the correct event etc.
EE3 progressed over time to support recurring events and the same will happen with EE4. We have recurring events on our roadmap here: https://trello.com/c/7E8HquIj/12-add-on-recurring-events
No, I mean at all, but to explain that better I mean the ability to create an event in the admin an set it to recur X amount of times (be that instances of the event, datetime or ticket etc) It may help if you see the EE3 recurring events manager (REM for short) to understand this better, take a look here: https://eventespresso.com/product/espresso-recurring/ Then view the ‘features’ tab and you’ll see this – http://take.ms/Gb1Gok So you create a single event and then told EE to create a recurring series of that event (it could create any number events for that series depending on your settings) That’s what EE4 does not currently support and when it does, will likely be done differently.
Yes, with EE4 you can not do that. EE3 has the recurring events manager to allow you to do what you are asking.
As you mentioned in your reply after this, EE3 is a separate product that will eventually be phased out. However that’s not going to happen tomorrow, or within a relatively short period of time. EE3 will begin to be phased out when EE4 supports all (or very close to) the features that EE3 has, Recurring Events being one of those main features preventing this change over. We continue to support EE3 and there are valid reasons to continue to use EE3, recurring events imo is one of the biggest ones. Eventually when EE4 supports some form of REM you can migrate over to EE4.
We currently don’t have an ETA. The next release for EE4 will be 4.9 which forcuses changes on the message system. Once that has been released will be using the roadmap to help prioritize development on the next feature(s). |
|
The support post ‘Registrants in One Event & Other Pre-Sales Questions’ 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.
