|
Marina
|
May 4, 2015 at 12:06 pm
I updated to 4.6.25.p and now there’s a new problem. When attendees fill in their contact details in the registration page and click “proceed to payment options” they receive the following error: “The selected method of payment could not be determined. Please ensure that you have selected one before proceeding. If you continue to experience difficulties, then refresh your browser and try again or contact … for assistance”.
Selecting a payment method happens on the next page, so that doesn’t even make sense. In the backend those registrations appear as abandoned transactions with blank attendee data (except for my custom fields and the permalink with the registrant’s name – so I was able to track back those registrations). All system-side data never made it through.
What can I do? We’ll have to switch our system if I don’t fix this by tomorrow.
Thanks!
|
|
Josh
|
May 4, 2015 at 12:43 pm
Hi Marina,
Can you check to see if any caching is set up for this site? Along with that, which payment methods are active? Can you post a link to a registration page so we can investigate?
|
|
Marina
|
May 4, 2015 at 1:10 pm
Hi Josh,
thanks for your fast reply!
There’s no caching on my website, at least it shouldn’t be. I have invoice and PayPal active. You can check it out here!
Thanks for looking into this!
|
|
Josh
|
May 4, 2015 at 1:17 pm
Hi Marina,
I ran a test registration on your site and I’m not seeing any errors. It allowed me to go to PayPal where I could log in to pay. Can you verify?
|
|
Marina
|
May 4, 2015 at 1:30 pm
Yes, that’s correct. I have all your Info and the transaction is correctly marked abandoned. That’s the frustrating thing about this error, it never occurs during any test runs, but some people have no chance of getting through the registration. Is there anything I’m missing? I don’t do Browser nor Page Caching and this occurs with W3 Total Cache activated and de-activated.
|
|
Josh
|
May 4, 2015 at 1:37 pm
Hi Marina,
W3 Total cache can activate caching while the plugin itself is deactivated. This is because it adds constants to wp-config.php and cache files. So if W3 was simply deactivated, without going through its options and disabling the various types of caching, caching could be the cause of the issue.
The other thing to check is with your host to see if they have any server side caching in place like APC or object caching. This type of caching would not be controlled by a caching plugin.
|
|
Marina
|
May 4, 2015 at 1:51 pm
I excluded all the relevant EE Pages from Caching in W3 and checked with my host – there’s no server side caching.
The first empty registrations went through even before I had W3 installed. But that was a different issue that didn’t occur since the upgrade.
Is there any other possible source besides caching? I’m clueless!
|
|
Josh
|
May 4, 2015 at 2:43 pm
Hi Maria,
The caching settings where you exclude pages only applies to page caching. If object caching is enabled it may cause the issues you’re seeing. It may also help to see if you can reproduce the error with a specific web browser.
|
|
Marina
|
May 4, 2015 at 3:18 pm
I was able to reproduce this error with Firefox 37.0.1 this afternoon, I received the same error when I entered the attendee’s information in the frontend. I was logged in and still received the error on the frontend page. I’m just making wild guesses – special characters in the registration? Any other ideas? Any suggestion might help 🙂
|
|
Josh
|
May 4, 2015 at 3:49 pm
Hi Marina,
I’d like to investigate the registration page further, but currently it’s been shut down.
|
|
Marina
|
May 4, 2015 at 4:22 pm
Sorry – it’s back online now!
|
|
Lorenzo Orlando Caum
|
May 5, 2015 at 9:22 am
Hi Marina,
The link is now working but takes us to a page with an Eventbrite widget. Could you share a direct link to an event page for Event Espresso?
Thanks
—
Lorenzo
|
