Support

December 13, 2012 at 3:24 am

Hi,

This ticket has been marked as high priority and is being actively worked on, but there is no update on when it will be completed yet.

I will let you know as soon as I do!

December 18, 2012 at 9:56 am

Hi there,

You can apply the fix to the gateway files that you have installed right now. There are four files that will require a few modifications:

First, /gateways/PaymentGateway.php line 9:

if (!class_exists('PaymentGateway')) {

change to:

if (!class_exists('Espresso_PaymentGateway')) {

same file, line 11:

abstract class PaymentGateway {

change to:

abstract class Espresso_PaymentGateway {

Second, within the ideal gateway folder: line 13 of /gateways/ideal/ideal.class.php:

class iDEAL_Payment

change to:

class Espresso_iDEAL_Payment

Third, in /gateways/ideal/ideal_vars.php, line 12:

$iDEAL = new iDEAL_Payment($partner_id);

change to:

$iDEAL = new Espresso_iDEAL_Payment($partner_id);

Fourth, in /gateways/ideal/report.php, line 13:

$iDEAL = new iDEAL_Payment($partner_id);

change to:

$iDEAL = new Espresso_iDEAL_Payment($partner_id);

So in a nutshell, we’re adding a prefix of “Espresso” to each of the classes so that the other plugins that are using the identical classes in their gateway will not conflict.

December 18, 2012 at 3:06 pm

Hi there,

I am so sorry for the trouble that you are having. I ran a few tests with the iDeal gateway and can recommend trying the above code changes with one exception this time: You can leave Paymentgateway.php as is. Can you try making these changes to the iDEAL gateway?

Line 13 of /gateways/ideal/ideal.class.php:

class iDEAL_Payment

change to:

class Espresso_iDEAL_Payment

In /gateways/ideal/ideal_vars.php, line 12:

$iDEAL = new iDEAL_Payment($partner_id);

change to:

$iDEAL = new Espresso_iDEAL_Payment($partner_id);

In /gateways/ideal/report.php, line 13:

$iDEAL = new iDEAL_Payment($partner_id);

change to:

$iDEAL = new Espresso_iDEAL_Payment($partner_id);

December 19, 2012 at 1:42 am

Hi,

I am really sorry that this is occurring, we are trying to to help resolve this as best we can.

2 things if it’s ok.

1) Have you got debugging turned on? If so, please turn it off and test again.

2) if the debugging doesn’t assist, please provide us with login information so we can take a closer look

Please send both WP and FTP details via https://eventespresso.com/contact/

Choose the “I am sending login info as requested” option and fill out the form

Please make sure you add the forum post link to aid us in case another team member picks up the email.

NOTE: login details need to be Admin level.

December 19, 2012 at 5:34 am

Hi, We have your details now, thanks for that. Im going to pass this on to Josh when he gets online, he knows a lot more about the gateway workings than I do, so you will be in better hands there.

December 19, 2012 at 12:54 pm

Hi there,

Can you verify whether the Event Espresso Ideal gateway works as expected if the WooCommerce ideal module is deactived? I’m not able to reproducing the errors you are reporting on my test site with the WooCommerce ideal module installed. I’ll keep working on my site to see if I can reproduce these issues. I’m hesitant to change anything on a live site without being able to narrow down the cause of the issue.

I logged into the site and it appears you have the gateway set up in live mode. Is it possible for you to switch to test mode for a time and run a test registration?

December 19, 2012 at 3:46 pm

That last part sheds more light on what is going on. I was under the impression you were seeing the errors while paying for an event registration. If you have the WooCommerce IDeal plugin enabled, do you get any errors when you run a test registration using the new gateway files I uploaded to Dropbox?

December 24, 2012 at 12:13 pm

This is an update: The developer who is working on the ticket has added a check for the attendee ID so that the espresso process payment does not get called within the woocommerce ideal gateway flow.

In /gateways/process_payments.php, there is a function that is named deal_with_ideal that starts on line 182.
What we’re doing is adding a check for the attendee ID before calling the espresso_process_ideal function. Here is the updated version of that function:

function deal_with_ideal() {
    if (!empty($_POST['bank_id'])) {
        $active_gateways = get_option('event_espresso_active_gateways', array());
        if (!empty($active_gateways['ideal'])) {
            foreach ($active_gateways as $gateway => $path) {
                event_espresso_require_gateway($gateway . "/init.php");
            }
            $payment_data['attendee_id'] = apply_filters('filter_hook_espresso_transactions_get_attendee_id', '');
            if(!empty($payment_data['attendee_id'])){//only process the payment if we can associate it with an attendee
             espresso_process_ideal($payment_data); 
             }
        }
    }
}

Please note: I tested this code running the current version of Event Espresso with the modified IDeal gateway and the Woocommerce plugin +Ideal gateway installed and was able to run through a WooCommerce product purchase without a conflict.

I hope this helps! 🙂