|
Amdur Productions
|
March 12, 2019 at 10:49 am
I enabled logging and am seeing no errors. Accepted payments work just fine, but nothing happens if the credit card is declined. An email is sent to the account saying the payment was declined, but obviously I’d like that to happen on the page.
Thanks!
Sam
|
|
Josh
|
March 12, 2019 at 11:16 am
Hi Sam,
May I ask which version of Event Espresso and which payment method from Authorize.net (AIM, SIM, Accept, or other)?
|
|
Amdur Productions
|
March 15, 2019 at 12:28 pm
4.9.79.p and I’m guessing AIM? We definitely do not have the SIM integration plugin.
|
|
Josh
|
March 15, 2019 at 12:55 pm
Yes that’s probably the AIM gateway because that’s bundled with Event Espresso 4. This is the response that normally displays when there’s a general decline by the bank when using the AIM gateway:
https://slack-files.com/T02SY781D-FH0EFKXV1-20f21802c3
If you’re not seeing anything that looks like that when there’s declined credit card, that may be the result of a theme conflict. Is there a way we could download a copy of the active WordPress theme to check on a dev site to see if there’s a conflict?
|
|
Amdur Productions
|
March 18, 2019 at 11:04 am
Yes, we have this set up here:
* redacted *
-
This reply was modified 5 years, 8 months ago by
 Josh. Reason: removed access info
|
|
Josh
|
March 18, 2019 at 12:42 pm
Hi,
I’ve removed the access credentials from your last reply since this is a public forum.
There does appear to be a theme conflict (or a plugin conflict) because no server side validation error messages appear. For example, if you add a ticket to the cart, then try to submit the registration form without completing it, the server side validation message doesn’t display.
Assuming that’s a dev site, if you temporarily switch to one of the default WP themes, do the validation messages begin to appear if you test the same condition?
|
|
Amdur Productions
|
March 18, 2019 at 5:12 pm
This reply has been marked as private.
|
|
Amdur Productions
|
March 18, 2019 at 5:52 pm
After further troubleshooting, I am able to get errors displaying properly, but only with the default page template.
Is there something in particular we’d need to do to get this working with a custom page template that uses ACF for most of the fields rather than the default page loop?
|
|
Tony
|
March 19, 2019 at 6:23 am
EE hooks into the loop_start action, which is fired the first time you call the_post(), which apparently you are not.
You can either add a call to loop_start within your custom loop (although you’ll need so make sure it only fires on the first iteration) or call display_errors directly to add the content to your ‘loop’.
|
