|
Leo Oosterloo
|
March 22, 2013 at 7:56 am
Hello,
We are experiencing problems with attendees registering shorty after one other from the same computer.
One situation we are aware of is 60 registrations but only +/- 10 attentees are actually registered!
We experiencing exactly the same problem of this topic: https://eventespresso.com/topic/attendees-not-added-when-they-register-for-an-event-shortly-after-one-another/
I’m running the latest WordPress and EE 3.1.30.2P in dutch.
Installed add-ons: Mailchimp integration, members, permissions, ticketing.
I think we are already missing 100 attendees in our system.
|
|
Chris Reynolds
|
March 22, 2013 at 1:28 pm
The only situation I can see this happening is if you have a caching plugin active and that’s preventing the session data from being cleared when the registrant completes payment. Also 3.1.30.2 is not the latest version, the latest version is 3.1.30.7.
Can you confirm whether you have a caching plugin active? Are you able to reproduce the issue if you deactivate it? Most caching plugins are able to exclude certain pages — the Event Espresso pages (set in the Page Settings in General Settings) should never be cached.
|
|
Leo Oosterloo
|
March 23, 2013 at 6:03 am
Hello Chris,
I dont have any caching plugin active on this WordPress install. Precisely because of the use of forms and so. So that can’t be the problem.
The only plugins I use besides Event Espresso are:
– Akismet;
– BackUpWordPress;
– Simple Google Analytics;
– wpMandrill
Everybody receives an confirmation e-mail of there registration.
Only when more people register shortly after one another from the same computer/ip a lot don’t get registered in our system and they cant download their ticket.
|
|
Josh
|
March 25, 2013 at 8:58 am
Hi Leo,
There were a few hot fixes in Event Espresso 3.30.4 and .5 that fixed issues related to this one. Can you update to the latest version?
|
|
Leo Oosterloo
|
April 2, 2013 at 3:31 am
It looks like the update fixed the problem. In the meantime we switched to Gravity Forms for the registrations. So for now we stick with that. For the next event we will use EE again.
|
