This may be a silly question and I am sorry if it has been answered before. But my search on drupal.org has been fruitless. So, I am asking it here:

I have setup and configured the e-commerce PayPal module. My users are able to select products and proceed to pay with PayPal (currently PayPal sandbox). PayPal hits back my server with IPN. But, even after the IPN is received the transaction is still marked as pending, I have to go in manually and change it to 'completed'.

Is this the expected behaviour? because it is labour intensive and error prone.

If not, how do I go about fixing it?

I have enabled PayPal IPN debugging. The debug E-mail I receive contains lots of transaction related info which all looks good. But the last line, reads "The transaction has returned an invalid result from PayPal". Does this say anything about my problem? I can post the whole debug E-mail, if it helps.

Thank you in advance.

Regards,
Massoud

Comments

ñull’s picture

ñull commented
Status: Active » Closed (duplicate)

Paypal module is not suitable to Sandbox test the IPN feature. Beside the hit from Paypal, your server needs to confirm it to Paypal. This is done to a hardcoded URL that cannot be changed in the configuration and of course it points to the live paypal URL, not the sandbox. Look here for more information and a fix: http://drupal.org/node/50312

mass0ud’s picture

mass0ud commented

I applied the patch as you have suggested in the other thread. I guess, now my server reconfirms the IPN with PayPal to complete the IPN handshake. Also, the 'invalid result' message has disapeared from the IPN debug E-mail. So, thank you!

But, still the "payment status" for the new transactions are set to pending, even after I receive the IPN from the sandbox. Is this the expected behaviour? or else, please point me in the right direction.

Thanks,
Massoud

ñull’s picture

ñull commented

I don't know how far you are with setting up Drupal, but if I remember well, it is important that you have a cron job frequently calling the cron.php script. May be you forgot about that? To see quick results you can run it manually from your browser. For the rest I had a look at the other issues that I discovered around Paypal. Before this patch, I applied the following:

http://drupal.org/files/issues/paypal-module-localisation-country-shippa...

I noticed even many other changes that I did back then and they are not documented and they could be related. I don't have the time to look into it again. Try to apply it before the other patch and report back your experiences.

mass0ud’s picture

mass0ud commented

First off, thank you for trying to help me out. Much appreciated.

Second, I tried applying the ble.patch to the paypal.module. I am getting this error:

# patch -p0 patching file paypal.module
Hunk #1 FAILED at 1.
Hunk #3 FAILED at 97.
2 out of 7 hunks FAILED -- saving rejects to file paypal.module.rej

I tried applying it to the original e-commerce 4.6.0 paypal.module as distributed. I also tried applying it to the paypal.module patched with the first patch that you sent. I Recevied the same error.

Shall I try it against the CVS HEAD? If so, is it possible to use CVS paypal.module, but for the rest of the modules just use e-commerce 4.6.0?

Regards,
Massoud

mass0ud’s picture

mass0ud commented

My previous post was truncated for some reason, so I am posting the error that I am getting:

patching file paypal.module
Hunk #1 FAILED at 1.
Hunk #3 FAILED at 97.
2 out of 7 hunks FAILED -- saving rejects to file paypal.module.rej

I am applying it to the 4.6.0 package, shall I try applying it to the CVS HEAD or some other revision?

Regards,
Massoud