Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 eway 3.0 Gateway error | Event Espresso - Staging Server
When entering checkout, under the credit card option, the following error message is displayed: “An error has occured in the using of the Eway Rapid 3.0 payment gateway. Please try a different gateway.”
I contacted eway support. They tried re-issuing my API key, but it had no effect… They then suggested uninstalling and re-installing the module, but we don’t want to do this because we have multiple signups for events currently saved in the module. We tried disabling and re-enabling the eway 3.0 payment gateway, but it had no effect.
We have recently changed our domain, but eway couldn’t see how that could have any effect on the payment process.
The error message is due to the plugin requesting data from eway but not getting it. I am wondering if it is a possible SSL issue, as though the gateway isn’t notifying me of an error for the SSL I can’t see one on your site, so can you confirm you have SSL active?
I can confirm there is an SSL certificate installed. We can fix this by altering the return URL (right now it’s pointing to a non-pretty permalink, which will not work with the way WPEngine has the https redirects set up.) Can you send us FTP credentials via this form so we can apply the fix:
The support post ‘eway 3.0 Gateway error’ 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.