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 Auth.net SIM | Event Espresso - Staging Server
I have an SSL and have installed WordPress HTTPS. I get the same thank you page with the broken images regardless of whether I have checked “Force HTTPS on Return URL”
WP-cache is disabled. Thank you page is correctly configured and the page url in the payment settings field (yellow text field) is exactly what I entered. Auth.net support (via chat) said the return url could not include script variables (e.g. /?page_id=#) – but I assumed you have already tested that.
(2) Second issue is that I am using both credit card and invoice payment options. When the registration payment page loads with both payment options, there is a significant gap between the payment option title and the credit card payment button. CSS inspector shows that the hidden fields are being separated by , thus creating the spacing issue and bumping the button so far down.
Yes, relative links to images will not work on the receipt page. Authorize.net’s servers will fetch the html of the receipt page from your server and display it to the customer coming from their server. Therefore, if you have a relative link to an image, the customer’s browser is going to be looking to fetch the image from the authorize.net server with the relative path that you specified, which will obviously not work.
Thanks Sidney. I got the SIM working by removing the url from Auth.net and added full paths to the images.
Any ideas on the second issue with the breaks between the hidden fields pushing the payment button down?
Viewing 2 reply threads
The support post ‘Auth.net SIM’ 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.