Posted: June 9, 2015 at 8:48 am
I am having the exact same issue with my site and registrations. Get error code: “An error has occurred: This is peak registration time for our camp and despite following other instructions, clearing cache, turning off caching, etc., this issue persists. We need help with this ASAP. Thanks! http://www.saintjohnscamp.org is the domain. |
|
Sidenote – this seems to ONLY happen with Chrome. I can get the registration to submit with FF. -LB |
|
Hi there Luke, I’ve split your support post reply from the original support post here: https://eventespresso.com/topic/split-many-failed-transactions/#post-160436 If you see an existing support post that sounds like your issue or question, then please create your own support post and then include a link to the support post that you saw. This will help us prevent confusion when multiple members are posting. Could you tell us about the caching that is in use on your site? Is that through a caching plugin like W3 Total Cache? If so, turning off the plugin does not necessarily disable caching on your WordPress site. Please double-check that no-caching rules are setup for your Event Espresso pages through your caching plugin: https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/ — |
|
Hi Lorenzo – sorry I”m just now responding. We use wordfence for security and there is no caching turned on. It was previously, but after trying the exceptions listed in another support forum to no avail, we disabled it completely and cleared the cache. After updating the EE plugin and migrating data this morning, the error is still happening. Here is the current error when I try to submit an application from Chrome: EE_SPCO_Reg_Step_Attendee_Information – process_reg_step – 598 We’re at the peak of our Summer Camp registration and this is a very big problem for us and is causing loss of registrants, so anything you can do to help me expedite a solution would be appreciated. Thank you! -LB |
|
Oh – and the support post you linked above is exactly what I did prior to disabling all caching through Wordfence. We do not use W3 Total Cache. |
|
Hi Luke, who is your web host? — |
|
Hostmonster |
|
Hostmonster should be fine. Could you backup and update to the latest software? https://eventespresso.com/wiki/ee4-changelog/ If the issue continues, then try temporarily deactivating other plugins to rule out a conflict. If that still doesn’t help, then follow up here: https://eventespresso.com/send-login-details/ — |
|
The plugin is already at the current version – as I said I just updated this morning and merged database. 4.7.1. I’ll try deactivating other plugins and then send login details if that doesn’t work. Thanks. |
|
Same problem and error code after disabling all plugins. Just submitted login info. Thanks. |
|
Hi, there is an issue with the login. Could you double-check it and reply to the email? Thanks — |
|
Already did. 🙂 |
|
Ok, after deactivating Jetpack, I was able to retry the registration and it worked. It appears that once Jetpack is both activated AND connected with WordPress.com the error begins to occur. If Jetpack is just activated as a plugin but not connected to WordPress.com then it makes it through the first phase of the registration to the payment page, but then throws a different error and can not complete. Jetpack appears to be the issue, after testing it multiple times now. |
|
More testing. Jetpack is indeed the issue. I’ll leave credentials up if you need to do more testing. I can disable jetpack so that our registrations can proceed, but this is a very standard wordpress plugin that gives us a lot of insight into our website, especially statistics. Please let us know when this conflict is fixed. Thank you! |
|
Hi Luke, Can you try re-activating Jetpack, then go to the Jetpack dashboard and disable the features that you don’t use? Then, if it turns out the conflict is from a feature that you are not using, you’ll still be able to use Jetpack. Please keep in mind we cannot guarantee all features of all WordPress plugins can be made to not conflict with Event Espresso. |
|
The support post ‘Split: Split: Many failed transactions’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.