|
Jason Lee
|
December 7, 2021 at 1:20 pm
Hello!
We have one user (out of several thousand) who is getting the following notice when trying to make a reservation:
Thank you so much. Your ticket selections have been received for consideration.
Our events are all free to paying members (through the s2member plug in). This is the only member having this issue, and other members are able to reserve for the events she’s having trouble with.
Thoughts?
|
|
Seth Shoultes
|
December 7, 2021 at 1:57 pm
Hey Jason,
Have you double-checked the s2Member account permissions for the user? Also, verify the user name is correct and that they are logging into the correct account.
|
|
Tony
|
December 7, 2021 at 2:28 pm
Hi Jason,
Just add some additional data here, I’m not aware of anywhere in our code that has that specific string so could this could be from some custom development you’ve had done?
|
|
Jason Lee
|
December 7, 2021 at 2:55 pm
Hey Tony and Seth,
Thanks for getting back with me so quickly.
Checked everything on the user and it looks correct. We don’t have any customizations that use this specific output. I did find this support post from 2016 talking about a bot-trap or something that does use that output: https://eventespresso.com/topic/cant-checkout-after-ticket-selection/
For a little more information, I found out the user was using an “AOL Browser.” I had no idea AOL had their own browser or that people still used AOL. The user tried a different browser and had no problems reserving.
|
|
Tony
|
December 7, 2021 at 3:29 pm
Schoolboy error on my part, assumed you were using EE3 and yes, that string is in EE4!
The bot trap in EE4 is really simple in that it adds an additional email field that is hidden, users should never be submitting values in that field but…. bots will, hence it’s a bot trap.
What it sounds like was happening with this user is they have autofill enabled and it’s adding a value to that field. Now… before we consider discussing troubleshooting that user, it’s important to note that the AOL browser final release date was May 10, 2006 (Yep, 15 years ago) and in short should not be used. I’m not aware of any updated version from that point so it’s wayyyyy behind literally any current browser.
If you have reCaptcha enabled on the Ticket Selector/registration form you could disable the bot trap to prevent something like this from happening again but to be honest, its rather rare.
|
|
Jason Lee
|
December 7, 2021 at 4:10 pm
No worries! We’ve talked a ton here and with premium support on EE3 over the years, but we finally made the jump over 🙂
And ahhhh, that makes sense. Pretty clever feature! As for troubleshooting this user, I think upgrading their browser choices is probably the best fix. We have several thousand users who make a lot of reservations and this has been the only person in five years that has had a problem.
|
|
Tony
|
December 8, 2021 at 12:43 pm
No worries! We’ve talked a ton here and with premium support on EE3 over the years, but we finally made the jump over 🙂
Nice 🙂 we have some nice changes coming soon with the recurring events manager for EE4 (a new event editor to go with it etc)
And ahhhh, that makes sense. Pretty clever feature!
It’s a simple yet clever feature but with that, it’s fairly simple to workaround. So helps with basic bots that just submit forms but shouldn’t be the only method relied on.
As for troubleshooting this user, I think upgrading their browser choices is probably the best fix. We have several thousand users who make a lot of reservations and this has been the only person in five years that has had a problem.
Agreed 🙂
|
