|
Antenna Digital
|
March 11, 2020 at 6:38 am
I have both Pay by Credit Card and Pay by Check available on the checkout page. Pay by Credit Card is selected by default. I had thought that when a use clicks Pay by Check the Credit Card form would be hidden ut that is not happening.
We’re using Authorize.net for the CC gateway, and it’s currently in Test Mode (could that be why?)
How do I get the form to hide is Pay by Check is selected….it would likely be a bit confusing for our visitors
Thanks
|
|
Tony
|
March 11, 2020 at 7:12 am
Hi there,
That should happen by default and if not it usually means there is a JavaScrip error being thrown on the page.
I had a look over your events but all tickets are hidden behind a log in, can you either create a password protected event we can run a test registration on and post the password here, or send temp login details we can use to view the tickets using this form:
https://eventespresso.com/send-login-details/
|
|
Antenna Digital
|
March 11, 2020 at 7:31 am
This reply has been marked as private.
|
|
Tony
|
March 11, 2020 at 7:47 am
Unfortunately, the link posted is behind basic auth so I can’t view it without a username and password.
|
|
Antenna Digital
|
March 11, 2020 at 7:54 am
This reply has been marked as private.
|
|
Tony
|
March 11, 2020 at 8:06 am
Thank you.
So there is a JS error being thrown:
jquery.min.js:2 Uncaught TypeError: $(...).unload is not a function
at Object.disable_caching (single_page_checkout.js?ver=4.10.3.p:194)
at Object.initialize (single_page_checkout.js?ver=4.10.3.p:167)
at HTMLDocument.<anonymous> (single_page_checkout.js?ver=4.10.3.p:1483)
at l (jquery.min.js:2)
at c (jquery.min.js:2)
Likely caused by loading version jQuery v3.3.1 rather than the version included within WP Core, if you switch over the bundled version with core, does it work as expected then?
|
|
Antenna Digital
|
March 11, 2020 at 8:22 am
That was it Tony, thanks.
Once you mentioned it I looked back at a different site I worked on before the new year. We had a similar problem with Restrict Content Pro.
I’m going to have to talk to our team and see if we can consider changing our framework to use the default rather than the 3.3.1 since this is the second time it’s caught me out.
I appreciate the help on this Tony.
Consider this issue resolved.
|
