|
Stewart goodwin
|
February 26, 2019 at 11:30 am
Hi,
I’ve been having issues with a site using EE4, where when a Credit Card payment is declined nothing is shown to the user on the front-end.
By inspecting the network activity, I do see the Ajax request being made, along with the response from the payment processor as seen here:
https://cl.ly/9a77281f0205
However, despite this response from the API, nothing shows up on the frontend, leaving the user without any clue as to why the site does not advance to the confirmation page.
Any idea of what might causing this?
|
|
Josh
|
February 26, 2019 at 11:44 am
Hi,
We saw something similar last week for another site and it turned out to be caused by the theme. What happened was the theme has a bit of JavaScript that stripped away the notification’s placeholder html. So when the error was thrown, there was no html to contain it. Here’s a link to the topic where this was discovered:
https://eventespresso.com/topic/error-messages-in-pop-up-not-displaying-on-registration-form-page/
What you could do is try Health Check plugin to rule out a similar cause for your site.
|
|
Stewart goodwin
|
February 27, 2019 at 8:04 am
Hi Josh,
Thank you for the follow up.
That might be related indeed, although I’m a little confused as to how that empty paragraph would be added to the document. Wouldn’t that be added by the the_content() function?
In any case, I’ve tried adding an empty paragraph <p class="espresso-notices-msg"></p> to the DOM, and it still isn’t filled in with the response from the payment processor.
Anything else I should be looking into?
|
|
Stewart goodwin
|
February 27, 2019 at 8:19 am
Just to add to the info above, I’ve also tried to debug the site with the default theme and without any plugin enabled, using the Health Check plugin, but with that I can’t even enable Event Espresso, it keeps failing with the error message:
When enabling the plugin, event-espresso, a site failure occurred. Because of this the change was automatically reverted.
|
|
Josh
|
February 27, 2019 at 8:35 am
Wouldn’t that be added by the the_content() function?
It’s added before the_content(), somewhere around the loop_start actually.
Since it sounds like you’re having some trouble with the Health Check plugin, which happens, maybe you have a dev server you can troubleshoot this with?
|
|
Stewart goodwin
|
February 28, 2019 at 9:01 am
Hi Josh,
Could you please elaborate on how are those tags injected into the template? I assume they would be added via a standard WordPress hook but that doesn’t appear to be the case.
I did managed to get the notification showing on the production server running Health Check with nothing but Event Espresso enabled:
https://cl.ly/921213879054
The error message is still a bit cryptic for a regular user, and I do see the DOM structure added to the page in this case. That structure includes elements for the Ajax feedback and the confirmation notices, which is missing from the page when I enable our theme.
Could you please elaborate on how those tags are added to a regular page template?
|
|
Stewart goodwin
|
February 28, 2019 at 9:08 am
Sorry, one more detail to this.
If I try adding the markup manually, that is the three divs you see here:
https://cl.ly/515193f3b5c6
The last one with the ID espresso-ajax-notices is stripped out of the page on page load. We don’t have any logic in place to do this, so I assume this is being done by the plugin itself.
|
|
Josh
|
February 28, 2019 at 9:13 am
I can point you to the source code, but the way forward will be to isolate the plugin or the theme that’s causing the conflict.
Hook point:
https://github.com/eventespresso/event-espresso-core/blob/master/core/EE_Front_Controller.core.php#L87
Method:
https://github.com/eventespresso/event-espresso-core/blob/master/core/EE_Front_Controller.core.php#L396
|
|
Stewart goodwin
|
February 28, 2019 at 10:21 am
Thanks so much Josh, this indeed point me in the right direction.
We use Timber on all our project, and the page query was failing the in_the_loop validation, hence the markup was never added to the DOM.
Thanks so much for helping me through this!
|
