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 Authorize.net SIM Transaction Goes through, Unformatted Thank You Page results | Event Espresso - Staging Server
I’ve looked through all the threads mentioning this but can’t fix my problem. Using the latest version of EE and the Multiple Registration Add-on – I’m running authnet on Test Mode and transactions come through just fine using the test Credit Card numbers. The problem is that once you hit Submit on the Authnet page (where you put the CC in) you get sent to an unformatted Thank You page on this URL: https://secure.authorize.net/gateway/transact.dll
@Dean – the issue is that I’m on a development server with a long link that is not going to be the fully qualified domain name — the way I understand it, using Rackspace Cloud Sites, I cannot do anything with a new SSL Certificate until I’m working on the live site. If you have a way around this so that I can test functionality right now then I’ll appreciate any advice. Otherwise, it looks like I have no option but to tell my client that their website will have to go down for several hours while we switch nameservers, propagate, install the SSL Certificate, then troubleshoot any potential issues w/ the SSL and Event Espresso.
If you look at the URL on the return page, you’ll notice that it’s coming from authorize.net, and it’s trying to load the resources from your dev site as https. Since it cannot do that, you’ll get an unstyled page.
One way to work around this would be to test with a gateway like Stripe, which doesn’t load up the thank you page on their servers.
Viewing 3 reply threads
The support post ‘Authorize.net SIM Transaction Goes through, Unformatted Thank You Page results’ 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.