Support

Home Forums Event Espresso Premium EE4 Error: Selected payment could not be determined.

EE4 Error: Selected payment could not be determined.

Posted: April 7, 2017 at 1:27 pm

Viewing 9 reply threads


tbex

April 7, 2017 at 1:27 pm

Guests are getting the following error when trying to register for our event:

An error has occurred:
The selected method of payment could not be determined. Please ensure you have selected one before proceeding.

I am unable to recreate this error on my end. When I test out registration, as if I were a guest, I am able to proceed without any issues at all.


tbex

April 7, 2017 at 1:33 pm

Guests are getting the following error when trying to register for our event:

An error has occurred
Your form data could not be applied to any valid registrations

I am unable to recreate this error on my end, when registering as if I were a guest.


Josh

  • Support Staff

April 7, 2017 at 1:46 pm

Hi there,

I’m looking into this right now. One issue I see happening is there’s a bit of JavaScript near the top of the page that’s trying to use jQuery, and the jQuery library isn’t loaded yet. Can you remove this?

https://www.evernote.com/l/AAQo0EUPbDNAD4LWWzCStKmAKjszB5fwmuo


Josh

  • Support Staff

April 7, 2017 at 1:49 pm

You can also make sure that your caching plugins and/or caching services do not cache the /events/ pages and the registration-checkout page on your website.

https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/


tbex

April 7, 2017 at 2:18 pm

where can find the location of the JavaScript to remove it?


tbex

April 7, 2017 at 2:19 pm

We’ve already set up our caching to exclude the event pages and registration check out page.


Josh

  • Support Staff

April 7, 2017 at 2:49 pm

The JavaScript might be located in the theme’s header.php file.

Can you doublecheck the cache exclusions that were set for Sucuri? The reason I ask is because the registration-checkout page includes a response header “X-Sucuri-Cache: HIT“. X-cache:HIT means that your request was served by CDN, not origin servers. There’s more info from Sucuri about troubleshooting issues related to caching here:

https://kb.sucuri.net/cloudproxy/Troubleshooting/troubleshoot-cache-issues


tbex

April 7, 2017 at 3:27 pm

I cannot find the javascript in the header file for our current theme. Would it be in an old theme?

I re-added the cache exclusions just in case.


Josh

  • Support Staff

April 7, 2017 at 3:58 pm

If the code isn’t coming from the WordPress theme, then it may be from another plugin that’s activated at the moment. It would not come from an old theme because any old themes on your site can’t load code unless they are activated. It’s a real problem because the theme is forcing the jQuery library to load at the bottom of the web page, and the little snippet of code is loading near the top of the page requires the jQuery library.


tbex

April 7, 2017 at 4:03 pm

So what can I do to find out which plugin is causing the issue? If I’m unable to replicate the errors others are getting, is there another way to figure out which plugin it is?


Josh

  • Support Staff

April 7, 2017 at 4:18 pm

Your site has more than one issue happening and causing breakage. So issue #1 is your theme is forcing the jQuery library to the bottom of the page, which breaks the code that appears near the top of the page. This code that normally would be fine, but is broken because of a dependency:


jQuery("#top li:has(ul.sub-menu)").hover(function() {
    jQuery(this).children("a").removeAttr('href');
    jQuery(this).children("a").click(function () {
        return false;
    });
});

One possible way to resolve issue #1 is check in the theme’s options to see if there’s a setting that allows loading the jQuery library at the top of the page instead of the bottom. Another way to resolve this is move the code to the bottom of the page.

The errors that others have reported generally happen if there’s a problem with caching. It appears that there are two types of caching happening. One is from Sucuri and the other from the W3 total cache plugin. Is that the case? If so, do you need both types of caching? It may even be that the two aren’t compatible with each in which case only one should be used.

Viewing 9 reply threads

The support post ‘EE4 Error: Selected payment could not be determined.’ 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.

Event Espresso