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 Rapid 3.0 Gateway Error since last EE upgrade | Event Espresso - Staging Server
My customer are currently receiving the following error message when they attempt to use Eway as the payment method. This has only been brought to our attention today, but we have not had any payments via eway since the last EE upgrade.
Can you please urgently assist? This is the error message:
Secure Payment Transactions Processed by Eway Rapid 3.0 Payments Pro
An error has occured in the using of the Eway Rapid 3.0 payment gateway. Please try a different gateway
I am also in touch with eway. It’s been working brilliantly up to now.
The error message that you are seeing fires if either of these two conditions are met:
The form action URL isn’t correct or the the Eway Access code is missing/incorrect.
Can you verify that the Eway Rapid 3.0 API key, username, and password are correct in the Event Espresso>Payment settings?
The other thing you can try that will make a difference if there is an issue with the form action url redirecting is change one line of code in the Eway gateway.
This change can be made in eway_rapid3_vars.php ~ line 45
The support post ‘Eway Rapid 3.0 Gateway Error since last EE upgrade’ 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.