|
Jeremy
|
April 12, 2016 at 6:23 pm
About a week ago we started seeing Failed Transactions appearing, and often more numerous than successful ones (we’ve had them before of course, but just a handful, now there are lots being generated every day).
We updated WP+EE4 two days ago but the level of new Failed transactions continues.
We have confirmed with the host that there is no server caching occuring. There are no plugins with caching turned on.
The Failed transactions contain minimal info, only session info, event + time, so it is hard to compare whether a successful registration follows shortly afterwards (as in did the person successfully register in the end, or not?).
The events aren’t listed in Google, and in general all people visiting an event page are there to undertake their registration.
|
|
Tony
|
April 13, 2016 at 5:04 am
Hi Jeremy,
Have you had any reports of registration issues?
Its most likely spam registrations.
An incomplete registration is created within Event Espreso as soon as you submit your ticket selection (before EE requests attendee information), a registration within EE must have a transaction assigned to it and it creates a ‘failed’ transaction at that time.
If no details are then provided within the registration details step, that is how the registration/transaction remain.
Go to Event Espresso -> Registration Form -> Reg Form Settings.
Do you have ‘Enable Bot Trap’ enabled?
Also do you have reCaptcha enabled?
I can run a test registration if you would like to post a link to an event I can use.
|
|
Jeremy
|
April 13, 2016 at 4:56 pm
Thanks. The website isn’t listed in Google, but I had considered that robots were a possiblity still. The events with Failed transactions appear to be the same as ones that are currently being registered for (there are maybe 30 open now).
The Enable Bot Trap was already on.
I installed the reCaptcha so will monitor that over the next few days and get back to you. I had reviewed 3-4 EE4 support posts about Failed transactions and not seen that advice, so thanks for that tip 🙂
Can I give you the event url without making it public?
|
|
Josh
|
April 13, 2016 at 5:40 pm
Hi Jeremy,
You can send the URL via this form:
https://eventespresso.com/send-login-details/
Since you mentioned reCaptcha, I can let you know that reCaptcha will not help prevent a spam submission to the ticket selector form, which is what starts a transaction. The bot would have to try to fill out and submit the registration form for the reCaptcha field to be effective.
I can recommend a few other plugins that I’ve found to be effective for blocking bots and they are:
https://wordpress.org/plugins/block-bad-queries/
and
https://wordpress.org/plugins/blackhole-bad-bots/installation/
If you install the latter, it involves add a bit of code to a robots.txt file. I’ve found these to be effective for preventing machines from hitting a WordPress site.
|
|
Jeremy
|
April 13, 2016 at 7:25 pm
Thanks. After activating reCaptcha I noticed it appeared on the form, not the ticket selector, so yes, it won’t stop robot entry.
I have now disabled the reCaptcha, as when it was on it caused registrations to not submit, the error being: “A valid transaction could not be initiated for processing your registrations.”
I have sent login details.
We had a pending update to install a firewall, which might acheive the same as the two plugins suggested. It has been activated but is learning for next 7 days.
(just now I updated from 4.8.39.p to 4.8.40.p)
|
|
Josh
|
April 14, 2016 at 1:29 pm
I tend to prefer smaller plugins that do one thing and do it well, but the other plugin you mentioned might also help.
|
