|
SurfShop
|
April 19, 2013 at 5:19 pm
Hello —
In prior years, we’ve had the frustrating issue of site visitors being able to register more people than the class limit by using the back button after registering one person to register others.
Last year, I was told that this would be remedied in Event Espresso 3.2, but alas, we have another class season starting and 3.2 isn’t ready yet. This was the work around that we used last year: https://eventespresso.com/forums/2012/04/back-buttonattendee-limitcart-clearing-issue/
However, I was wondering if there was a better solution? If not, would you be able to create the workaround that we used last year for me (free of charge, since when software promises attendee limits, it should have solid attendee limits)?
Thanks!
|
|
Chris Reynolds
|
April 22, 2013 at 11:00 am
Can you refresh our memory on what was done last year for your customization? Looking back at the plugin, we added a function that clears the session after a transaction is completed, so a person can go back through the process if they wanted to buy another ticket without overwriting the first purchase.
The text that you posted in the old forums could just be added to your payment page, with a link going back to your calendar or event list.
|
|
Chris Reynolds
|
April 22, 2013 at 11:03 am
Alternately: a workaround is to put a lower limit on the maximum number of attendees and adding an overflow/waitlist event. Then if you sell out (but still have available spaces) you can contact people from your overflow event and either add them in manually or open up the registration for those people specifically. Often large venues will hold back a number of tickets anyway, to keep for promotions or VIPs, etc.
|
|
SurfShop
|
April 22, 2013 at 1:17 pm
Hi Chris —
Thanks for your replies! Unfortunately, the lower limit maximum number/waitlist event option isn’t an option for my client (he has several hundred classes to manage and teach and doesn’t have the time or patience for dealing with anything aside from opening and closing classes and dealing with other client issues). If this was for a one-off event, it would work, but not for the 5 classes a day that he deals with during the summer months.
So, last year, Josh created a php file for us to upload:
“What it will do is if someone has registered using a groupon code, they’ll see additional instructions to not use the back button and a link that will take them back to the original registration page.”
This year we won’t be using the Groupon feature — people will select “Groupon” (or other daily deal option from the price menu) or pay full price. (If they select Groupon, they won’t be sent to PayPal; if they pay full price, they will pay through PayPal). So, essentially, they need to receive the message not to use the back button to register more people at the registration confirmation screen.
As far as the feature to clear the session after a transaction is completed goes, that works fine (the transaction clears). However, if the last person to sign up took the last available space and, after registering, decides to use the back button to register another person, it allows them to, instead of clearing the session and then giving them the screen that tells them that the class is full. What would be most helpful would be if you could create something that will give the class full screen if someone uses the back button and the class is full.
Thanks,
Melissa
|
|
Josh
|
April 22, 2013 at 2:27 pm
Hi Melissa,
Did you make a backup of the file that we modified last year?
|
|
SurfShop
|
April 22, 2013 at 2:35 pm
Hi Josh —
I don’t believe I did, as we’re not using the Groupon feature this year (so, I figured it wouldn’t do the trick). However, I have the original file you sent me to upload into the /templates file — and can email it over to you. 🙂
~Melissa
|
|
Josh
|
April 22, 2013 at 5:14 pm
Hi Melissa,
Whatever we added to the template that displays after a groupon registration could be added to the template that displays payment info. If you can email it to support one of us can take a look.
|
