If i use the "Instant Payment Notification (IPN) simulator" on developer.paypal.com with the right IPN handler URL set (mydomain.com/lm_paypal/ipn) i get the following:

Error on developer.paypal.com: IPN delivery failed. HTTP error code 404: Not Found

Watchdog tells me

Error  LM_PayPal  09.01.2009	IPN in failed to run sql: INSERT INTO ...	
Error  PHP        09.01.2009	Unknown column 'unconfirmed' ...	
       LM_PayPal  09.01.2009	lm_paypal_ipn_in post-validate	
       LM_PayPal  09.01.2009	lm_paypal_ipn_in pre-validate	
       LM_PayPal  09.01.2009	lm_paypal_ipn_in called

'address_status' is the problem. If i modify lm_paypal_ipn_in() in lm_paypal.module (put 'address_status' into $ignore_fields and remove it from $ipn_fields and $int_fields) the errors disappear and the IPN is saved.

CommentFileSizeAuthor
#3 address_status.patch2.36 KBmfb

Comments

lyricnz’s picture

lyricnz commented
Status: Active » Postponed (maintainer needs more info)

Yes, I ran into the same thing with my 6.x-2.0 branch - it looks like the format of the address_status field has changed. Can you test with the sandbox backend, and see if this happens there? It might be an issue that only happens with the simulator.

mugginsoft.net’s picture

mugginsoft.net commented

This does seem to be an issue with IPN simulator.
The address_status field data is malformed.

Works fine with the sandbox.

mfb’s picture

mfb
they or he
commented
Priority: Normal » Critical
Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new address_status.patch2.36 KB

I haven't been able to receive real production paypal IPNs after upgrading to the Drupal 6 version of this module so marking as critical.

mfb’s picture

mfb
they or he
commented

Marked #194458: Field address_status in table lm_paypal_ipns needs to be a varchar as a duplicate.

lyricnz’s picture

lyricnz commented
Status: Needs review » Fixed

Committed http://drupal.org/cvs?commit=194166

Thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

maddentim’s picture

maddentim commented

Hello, this bug is causing my IPNs to fail to load on my production site that I took to D6. I see that a fix has been committed, but there has not been a release since the fix. I imagine that if I upgraded to the 6.x-1.x-dev version I would pick up the fix, but am hesitant to use a dev version on a production site. Am I safe to just manually apply the changes in the patch? I want to be able to successfully install the next release when it comes along. I guess I could turn it back?? Please advise. Thanks!