|
Greg Davis
|
October 21, 2014 at 8:47 pm
I thought the problem might be due to a plug or theme conflict, put I tried deactivating all and using a standard WordPress theme and still no luck. The EE3 options area to manage payment gateways has a problem for me as I cannot open any (or close ones already expanded) of the payment options. They are listed fine, but when I click on them to try to open any of them nothing happens!
Is there a bug with EE3 or jquery versions? I checked and I see version 1.11.1 of jquery is loaded.
|
|
Tony
|
October 22, 2014 at 2:20 am
Hi Greg,
On the Payment Settings page, if you open Chrome Dev tools (Settings -> More Tools -> Developer Tools), select the Console tab – http://take.ms/fWKSr
Do you see any JS errors there?
Also is your site hosted using WPEngine?
|
|
Greg Davis
|
October 22, 2014 at 4:01 am
Hi Tony,
I don’t have any JS errors on the console tab and yes I am hosted with WP Engine. I did also report the problem with them and they did point out this in an error log:
[Tue Oct 21 18:08:51 2014] [error] [client 69.7.237.251] PHP Warning: file_get_contents(/nas/wp/www/cluster-1648/parchedpainter/wp-content/plugins/event-espresso/gateways/atos/default/pathfile) [<a href='function.file-get-contents'>function.file-get-contents</a>]: failed to open stream: No such file or directory in /nas/wp/www/cluster-1648/parchedpainter/wp-content/plugins/event-espresso/gateways/atos/settings.php on line 75, referer: http://theparchedpainter.com/wp-admin/plugins.php
Do you think that could have something to due with it?
|
|
Tony
|
October 22, 2014 at 4:11 am
That shouldn’t do no.
We have a ticket regarding that warning and it is fixed in the next version of EE3 but it is nothing major and should not cause problems for most users.
However, we have seen a similar issue to this before on WPEngine caused by changes they make in the Admin, @josh has a small plugin to work around this:
https://gist.github.com/joshfeck/1afd180884f9c603d4f5
Can add that to your plugins directory, activate it and see if that fixes the payment settings.
|
|
Greg Davis
|
October 22, 2014 at 5:48 am
Thanks Tony, that seemed to do the trick for that part!
However, we are having a problem with “Incomplete” transaction payment status with Authorize.net and I wonder if there is anything related?
We did reset the AIM transaction key with Authorize.net and I did validate that it works (using Gravity Forms plugin with Authorize.net add-on). But for some reason EE isn’t able to process transactions using the same gateway.
Have you seen any reasons for this?
|
|
Josh
|
October 22, 2014 at 6:19 am
Yes Greg. Which version of EE3 is installed? Also, are the EE checkout pages set up to redirect to https?
|
|
Greg Davis
|
October 22, 2014 at 6:38 am
We are using the most recent version: 3.1.36.6.P
Should the EE checkout pages be setup for https?
|
|
Greg Davis
|
October 22, 2014 at 7:10 am
I did add the checkout and return pages for https but still getting the same “incomplete” payment status.
|
|
Josh
|
October 22, 2014 at 8:26 am
Hi Greg,
Since the site is hosted on WPEngine, you’ll want to be sure to set the pages to be https following their guide under “How to configure installed SSL Certificates”:
http://wpengine.com/support/add-ssl-site/
Then if you’re using pretty permalinks, you’ll want to be sure that the form action is pointing to the correct URL. You can do this by opening up gateways/aim/aim_vars.php and 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'])); ?>">
|
|
Greg Davis
|
October 22, 2014 at 2:30 pm
Thanks Josh, that seems like it may have solved the problem! Since this is a change to the standard aim_vars.php code, I assume it would have to be re-done in the future if there is a new release in EE3?
|
|
Lorenzo Orlando Caum
|
October 22, 2014 at 2:42 pm
Hi Greg,
In Event Espresso 3, you can relocate customized gateways to a safe location. Here is how to do that:
1) Login to your site with an SFTP client
2) Browse to this location:
wp-content/plugins/event-espresso/gateways/aim
3) Download the folder to your computer
4) Browse to this location using your SFTP client:
wp-content/uploads/espresso/gateways
5) Upload the aim folder there
—
Lorenzo
|
|
Josh
|
October 22, 2014 at 3:44 pm
I assume it would have to be re-done in the future if there is a new release in EE3?
That’s an incorrect assumption because the next release of EE3 will include this change.
|
|
Greg Davis
|
October 22, 2014 at 7:01 pm
Thanks Josh – that helps!
|
