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
Transaction always returns "incomplete"; WP Engine, Authorize.net AIM, and SSL | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Transaction always returns "incomplete"; WP Engine, Authorize.net AIM, and SSL

Transaction always returns "incomplete"; WP Engine, Authorize.net AIM, and SSL

Posted: March 28, 2014 at 7:13 am

Viewing 3 reply threads


conrad strabone

March 28, 2014 at 7:13 am

After submitting the credit card form to complete the purchase, the form loads the thank you (payments) page with payment status “incomplete”. This seems to happen even with invalid card info, as long as the form validates.

WP Version 3.81
Espresso Version 3.1.36.4.P
Espresso Calendar Version 2.2.2.p

This is a new installation.

Link to registration page:
https://salesgenerators.com/event-registration/?ee=4

Other info:

The site is on WP Engine, and the three pages as specified in the SSL instructions have been set to be served via SSL. The “Force HTTPS on Return URL” is unchecked, as I read was the correct thing to do with a WP Engine SSL install, although checking it had no effect on the issue.

We’re trying to use Authorize.net AIM. This is all set up and in LIVE mode, the API key & secret has been checked and re-checked.

I noticed that I’m getting a javascript error on submitting the form, complaining of EEGlobals being undefined. The error itself is innocuous, only preventing loading graphic from loading on form submit in aim.js, but it seems like the missing globals could be a clue to the real problem.

I also noticed a warning in the PHP logs that Espresso was failing to start a session:

PHP Notice: session_start() [<a href='function.session-start'>function.session-start</a>]: ps_files_cleanup_dir: opendir(/var/lib/php5) failed: Permission denied (13) in <omitted>/espresso/espresso.php on line 55


Josh

March 28, 2014 at 7:22 am

Hi Conrad,

From what I’ve seen with this before, the SSL redirect to the return page that WPEngine sets up doesn’t work if custom permalinks are enabled. There is a workaround for this. If you open up event-espresso/gateways/aim/aim_vars.php you can change line 33 from:

<form id="aim_payment_form" name="aim_payment_form" method="post" action="<?php echo $home . '/?page_id=' . $org_options['return_url'] . '&r_id=' . $registration_id; ?>">

to 

<form id="aim_payment_form" name="aim_payment_form" method="post" action="<?php echo add_query_arg(array('r_id'=>$registration_id), get_permalink($org_options['return_url'])); ?>">

This will make it so the form action URL matches what the return page redirects to regardless of how the permalinks are set up.


conrad strabone

March 28, 2014 at 7:51 am

Yes, that resolved it. Thanks!


Josh

March 28, 2014 at 8:12 am

Your welcome Conrad. We’ll be including this fix in Event Espresso 3.1.37.P. There may be a hotfix released before .37 is ready, so I can recommend copying over the aim folder to /wp-content/uploads/espresso/gateways and that will keep the changes from getting overwritten in the event there’s another hotfix released for Event Espresso 3.1.36.P
Viewing 3 reply threads

The support post ‘Transaction always returns "incomplete"; WP Engine, Authorize.net AIM, and SSL’ 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.

The original Forum description...

Status: closed

Updated by Josh 10 years, 9 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server