|
fayboydsfineartschool
|
September 6, 2018 at 9:56 pm
I was advised of this error this morning.
When filling in a registration form with all the required fields and checkboxes, pressing submit registration produces this error message.
I have disabled all plugins except event espresso.
I have disabled WordPress AMP.
I don’t know if it is related but when on mobile browsers, both Chrome and Safari, and a country is selected in the registration form it does not automatically display the correct states in the state drop down picker. (Works fine on desktop browser)
The first time I disabled all the other plugins the form worked correctly and went to the payment options screen.
I enabled each plugin from the top of the list down one at a time and tested until I found that a plugin to allow admin tickets – Event Espresso – Admin Only Tickets, Version 0.1.0 | By Chase C. Miller caused the problem to resurface.
I disabled it again and the error still pops up.
I have looked at caching, cleared history and cookies on desktop and mobile, still get the error.
All other plugins are disabled again.
I searched the forums and found quite a lot of posts related to this error but nothing exactly as it is occurring with us, I tried every suggestion.
I would appreciate your input with this problem
fayboydsfineartschool.com
|
|
Josh
|
September 7, 2018 at 6:41 am
Hi,
I checked and it appears your website is hosted on the Pressable infrastructure. That particular hosting platform isn’t known to be compatible with Event Espresso 4 due to the nature of its aggressive caching.
You’ll need to contact your web host and ask them if there’s a way they can either exclude the built-in caching from the registration-checkout page, or if there’s a way they can move the site to a server that isn’t being served from a cache.
|
|
fayboydsfineartschool
|
September 7, 2018 at 4:39 pm
Thanks, I will contact them. Although it is strange because we have used Event Espresso since April this year with no problems and this only started occurring yesterday. Our site is a WordPress dot com site.
|
|
fayboydsfineartschool
|
September 7, 2018 at 5:11 pm
I contacted WordPress and this was their reply:
Alright, I asked one of my colleagues who confirmed that we can’t disable caching for your site. Apparently this is a long-standing bug the Event Espresso won’t fix, which would affect any host using caching.
|
|
Josh
|
September 7, 2018 at 9:31 pm
That’s an interesting comment. If it’s a long-standing bug that Event Espresso won’t fix, then how is it that you “have used Event Espresso since April this year with no problems and this only started occurring yesterday”?
Other hosts that use caching like WPEngine allow for cache exclusions so the apparent bug, as they assert, does not affect that host and a number of others.
If they have any specifics about the apparent bug that needs fixing we’d all really appreciate it if they could open an issue report on GitHub.
|
|
fayboydsfineartschool
|
September 7, 2018 at 9:58 pm
Their suggestion is to find a different plugin instead of Eventespresso or a different host.
I explained that considering we had only just purchased Eventespresso and a premium hosted site on WordPress dot com in April that that suggestion was not an option.
He flushed the cache his end but it made no difference.
I restored the site from a backup prior to the problems and it appears to be fixed but that doesn’t tell any of us why it happened.
I’ll keep an eye on it and keep you posted in this thread.
|
|
fayboydsfineartschool
|
September 7, 2018 at 11:41 pm
Update.
Same problem has surfaced but it appears to be random. I was speaking with someone who wished to register and was stepping them through the form and when they clicked the button to proceed it worked.
The very next person I spoke to was trying to register in the same workshop and they received the error.
We have 20 workshops/events and I tested all this morning and they worked fine after the website restore. Now some work and some don’t but it is random.
Can you think of anything that might be causing this.
|
|
Josh
|
September 8, 2018 at 9:16 am
The seeming random nature indicates it’s related to the caching mechanism. I’ll to explain what’s going on with a little story:
Imagine there’s a bucket brigade and they’re passing a bucket from the street to a building. In between the street and the building there’s also a crane, outfitted with a wrecking ball. The wrecking ball is in perpetual motion running perpendicular to the bucket brigade line. The members of the bucket brigade are spaced apart just enough to stay out of the path of the wrecking ball, and generally they’re quick enough to get the bucket safely to building.
However, every so often the timing is just right where the bucket is in the general path of the wrecking ball. When that happens the bucket brigade member will drop the bucket (or the bucket may even get get hit) and its contents are emptied. So that emptied bucket gets passed back to the start of the line to be filled again.
How does this apply to your site? Well, the content of the bucket is your session ID. Each time you navigate from one page to another, and progress through the steps of a registration or other series of page visits, that “bucket” is passed along so the software can keep track of what you’ve done from one page to the next. Specific to Event Espresso, you select some ticket quantities, then move on to a registration form, then move on to the payment step, then finalize the registration. The session ID is used, in part, to identify your registration in progress and keep it separate from anyone else’s.
The danger to the session ID is the way the server side caching does housekeeping items like rebuild the cache (because the cache becomes stale over time) and scheduled garbage collection. When those types of processes are run, it’s just like that wrecking ball that swings by at the regular interval with the result of the bucket getting emptied. So the session has to start over because it could not maintain state. It’s at that point you’ll see the “Form data could not be applied to any registrations” error.
Ultimately we’d love to know how it’d be possible to keep the session to maintain state while these other processes are happening. So far the only solution we’ve seen is to disable caching for the page that handles registration checkout. That’s what the WPEngine offers their customers and it works quite well.
|
|
fayboydsfineartschool
|
September 18, 2018 at 7:34 pm
Same problem has resurfaced in the last week or so, random again. Was working fine since we last communicated then suddenly it is back.
I sent the WordPress team this link so that they can see what you guys recommend and if a work around can be applied.
They told me that changing servers is not an option. If there is anything specific they could do to make the plugin work add it here because they are following this thread.
|
|
Josh
|
September 18, 2018 at 7:43 pm
You do have the option to change servers.
It would involve moving to another host, and I can recommend any of the following web hosts including (but not limited to) Kinsta, Pantheon, WPEngine, or Flywheel. These Managed WordPress hosts are more than willing to work with you, they listen, they take matters like these seriously, and they have options to allow configuration (if need be) to have no issues with running Event Espresso.
|
|
fayboydsfineartschool
|
September 18, 2018 at 7:45 pm
Yes I realise that I can move hosts, I wanted them to move our site to another compatible server as our shop has been offline for 26 hours now.
|
|
fayboydsfineartschool
|
September 18, 2018 at 7:46 pm
They can’t answer the question why did it work flawlessly from April to September 6.
|
|
Josh
|
September 18, 2018 at 9:03 pm
The specific thing they need to do to allow Event Espresso to consistently take registrations without errors is configure the server to not delete or reset the PHP session in progress. Otherwise you’ll need to move to a recommended host.
|
