|
Landon Stroud
|
January 11, 2015 at 10:41 pm
Hi guys,
we are running Version 3.1.31.B
We would like to upgrade to the latest version including support however I need to know first if some keys sticking point function have been fixed. Please respod to each
1. When setting up multiple Ticket prices, on the booking screen if customer wanted to buy 2 x adult tickets and 3 x child tickets, they would have to do 2 x complete registrations for each price of ticket. Has this been resolved.
2. We sell tickets offline and have the reception lady use the web front end to sell the ticket, then login to the backend to take the payment. Do you have an upgrade more simplified way to sell tickets offline.
3. We have just had an issue whereby we allowed 350 attendees (utilising the seating chart) then we got to 341 attendees sold and we couldnt add anymore even though there was still time. Do you have any reason for this.
We really need answers on the shortcomings so we can choose to upgrade.
|
|
Garth
|
January 12, 2015 at 12:42 pm
Hi Landon,
How are you today?
1) That is resolved with the Multiple Event Registration addon (https://eventespresso.com/product/espresso-multiple/) which allows your audience to purchase multiple TYPES of tickets in one checkout with EE3. That functionality is available by default with EE4.
2) I don’t think that has been significantly changed in EE3, but the process in EE4 is a little easier. You can essentially complete front-end registration process in the back-end, but skip or apply payment if you want.
3) We’d probably need more information here to help. What is the default registration status for the event, and do you have any incomplete registrations that are still not paid for?
In general, Event Espresso 3 will receive fewer and fewer enhancements as it is replaced by Event Espresso 4+, so we recommend considering moving to Event Espresso 4 if you can (based on the availability of add-ons and such).
|
|
Landon Stroud
|
January 12, 2015 at 5:01 pm
Hi Garth, doing well thanks for asking, it seems EE4 adds some functionality we need. The only other thing we require is when using the Seating Chart, we need to be able to sell children and adult ticket prices.???
Also how do I go about getting the upgrade, and will it affect the custom payment gateway we had you guys write for us u?
Does seating chart working with EE4?
|
|
Dean
|
January 13, 2015 at 6:14 am
Hi Landon,
EE4 does not currently have a seating chart available for it.
EE3’s seating chart does not allow multiple tickets per seat at this time.
“Also how do I go about getting the upgrade, and will it affect the custom payment gateway we had you guys write for us u?”
If you are just updating from 3.1.31.b to the latest 3.1.36.6 it shouldn’t have any negative effect (I would still recommend backing up the site or the customised files as a minimum). That being said, your version of EE is over one and half years old so the gateway might need tweaking, it’s really quite hard to be certain without testing.
If you are considering updating to EE4, then the customised gateway won’t work, you would need to see if it is available for EE4 – https://eventespresso.com/features/payment-options/ (make sure you select the EE4 tab).
|
|
Landon Stroud
|
January 13, 2015 at 6:26 am
Hi Dean,
the seating chart is important to us, when will you be brining it into EE4
how much will it cost to get the ANZ Gateway (which we funded the development of initially) to be upgraded for use on version EE?
It seems like we are trapped between version whereby we need the easier offline payment process of EE4 but we need to keep seating chart and our payment gateway. What do you recommend for us moving forward. We are happy to pay for upgrade, but I am feeling your path to version 4 is flawed for our application of your product.
|
|
Garth
|
January 13, 2015 at 9:58 am
Hi Landon,
The upgrade path has been the same for all Event Espresso users. They are welcome to upgrade to Event Espresso 4 if the necessary features are available. There are thousands of users who are still using Event Espresso 3 because it better suites their needs for now. However, we are actively working on the add-ons and features that are needed for you and others.
However, while the Seating Chart is very cool and necessary in some situations, it is farther down on the priority list. There are many factors to the priority list, one of which is that there are fewer Event Espresso users who need the seating chart. Most Event Espresso users want the more common add-ons like Promotions, MER, REM, API, etc., which we are working on as quickly as possible. So, it will be a while before the Seating Chart is available unless someone helps to make it a priority by sponsoring the development. Also, once we do re-write the seating chart, we want it to be far more flexible than the current version, which is why we have delayed pouring resources into it that can be better used elsewhere right now.
We have rebuilt the gateway processing system in Event Espresso 4.6+ so each gateway will be its own add-on. That will help keep the code more modular, which should reduce bugs and increase the speed with which we build features. So, With regard to ANZ, we would need to rebuild the gateway which would be similar in cost and process as it was for Event Espresso 3. But I would suggest waiting to sponsor that if the need for the Seating Chart precludes using EE4.
Does that make sense?
|
