|
Renee deVilliers
|
June 1, 2017 at 8:57 am
Since May 23 we have been having any issues with our clients registering for classes on our site.
Many keep getting errors when processing their credit card through Moneris
“ERROR: Sorry, there was an error. Please be sure JavaScript and Cookies are enabled in your browser and try again.” We have a hard time replicating the error. Not EVERYONE gets the error either.
What it does happen is when they go to make payment with their credit card. They click submit on the payment information and it is sent to Moneri and it IS ACTUALLY charged (and then they receive the error message)
Our clients are emailed a transaction statement (by Moneris – as we have a set up with them to send a receipt). The statement of course takes a couple minutes to arrive, and in the meantime the client tries several more times, to no avail (they believe) but in fact each time the transaction processes, even though the error occurs, and they are charged multiple times for their transaction.
Additionally, the Event Espresso back end page NEVER receives the transaction information (even though their card is charged) and therefore, neither the client nor us are made aware of the payment and we have to manually do a lot of searching in our Moneris transactions to find the client’s payments.
We then end up voiding multiple transactions every day (at least five – ten transactions).
We also have to then manually go into the Event Attendee record and manually enter the transaction.
First things to be aware of:
1. We have not changed anything with Event Espresso.
2. We did notice that the java updates out now occurred on May 18th, after which all our problems started.
3. We have also not changed anything on Moneris side of things.
4. We are NOT running any WP Caching plugins.
From your EE System Status Page our current settings are:
Event Espresso version 3.1.37.11.P
WordPress version WP 4.7.5
Installed plugins
Contact Form 7 by Takayuki Miyoshi version 4.8,
Event Espresso – Custom Template Display by Event Espresso version 1.1.p,
The7 Post Types by Dream-Theme version 1.0.4,
Email Address Encoder by Till Krüss version 1.0.5,
Envato WordPress Toolkit by Envato version 1.7.3,
Event Espresso – Attendee Mover Tool by Event Espresso version 1.2.b,
Event Espresso – Calendar by Event Espresso version 2.2.7.p,
Event Espresso – MailChimp Integration by version 1.2,
Event Espresso – Multi Event Registration by Seth Shoultes version 1.0.5.p,
Event Espresso – Recurring Events by Event Espresso version 1.1.8.p,
Event Espresso by Event Espresso version 3.1.37.11.P,
Google Analytics Dashboard for WP (GADWP) by Alin Marcu version 5.0.0.1,
WPBakery Visual Composer by Michael M – WPBakery.com version 5.1.1,
MailChimp by MailChimp version 1.5.7,
Postman SMTP by Jason Hendriks version 1.7.2,
Slider Revolution by ThemePunch version 5.2.6,
WooCommerce Moneris Gateway by SkyVerge version 2.7.2,
WooCommerce Canada Post Shipping by WooCommerce version 2.5.2,
WooCommerce by Automattic version 3.0.7,
WooCommerce Helper by WooCommerce version 1.7.2,
WP-SpamShield by Scott Allen version 1.9.11,
YITH WooCommerce Zoom Magnifier by YITHEMES version 1.2.29
Settings
Home URL https://www.allaboutdogs.ca
Site URL https://www.allaboutdogs.ca
Registration Pages
Event Page #35804 – https://www.allaboutdogs.ca/event-registration
Payment/Thank You Page #35805 – https://www.allaboutdogs.ca/thank-you
Transaction Notification Page #35807 – https://www.allaboutdogs.ca/transactions
Cancel Return Page #35806 – https://www.allaboutdogs.ca/registration-cancelled
Server Environment
PHP Version 5.6.29
Server Software Apache
WP Max Upload Size 64 MB
Server upload_max_filesize 64 MB
Server post_max_size 64 MB
WP Memory Limit 96 MB
WP Debug Mode No
Espresso Logging Log directory is writable.
PHP Sessions
Session save path /tmp is writable.
Session name PHPSESSID
Remote Posting/IPN
fsockopen/cURL Your server has fsockopen and cURL enabled.
We are using The 7 Theme and it is up to date. Version: 3.6.1
These problems seem to keep popping up for us, and they do so very suddenly. We have been running events and taking payments for months now without incident, and now a flood of multiple transactions and clients who are frustrated by the multiple charges and the not knowing if they paid multiple times, or not.
Can you please help us.
Thanks.
|
|
Josh
|
June 1, 2017 at 12:33 pm
Have you contacted Moneris? They may have changed their API recently or their servers and their integration may need an update.
|
|
Renee deVilliers
|
June 1, 2017 at 3:55 pm
We have contacted Moneris, we are using hosted pay page so API is not applicable (according to them), and nothing has changed on their end.
|
|
Tony
|
June 2, 2017 at 4:54 am
Hi there,
I see you have WP-Spamshield activated on the site, can you deactivate that plugin and test some payments to see if that prevents the error?
|
|
Josh
|
June 2, 2017 at 4:59 am
Great! So for the time being, I can advise deactivating the WP-SpamShield plugin. That plugin has some known issues where its security features block payment notifications. We know that the payment response from Moneris is not spam, and we’ve reached out to the plugin author about this before but I’m afraid there wasn’t much willingness on their part to make changes to that plugin.
|
|
Renee deVilliers
|
June 4, 2017 at 11:35 am
Have deactivated the Wp-Spamshield plugin, and this week coming up we will see how payments go.
|
|
Renee deVilliers
|
June 15, 2017 at 11:49 am
So, we discovered that we needed to put Moneris IP Addresses into the WP-SPAMSHIELD WHITELIST, to avoid the transactions that use POST method of communicating to Event Espresso being rejected as spam.
So far in the last two weeks we are not getting any duplicate payments and people are not getting errors or waiting and refreshing. It is processing now normally WITH WP-Spamshield Active.
So, if anyone else is having issues, you might try this solution!
|
|
Josh
|
June 15, 2017 at 2:04 pm
You might also make a note to periodically check to see if the IP Addresses that Moneris uses get updated, in which case you’ll need to update WP-Spamshield’s list again.
|
