Thank you, guys. I found out what the problem was, now. It was a stupid error in my middleware, which couldn’t handle the empty referstring from paypal... now everything is working fine again
-----Ursprüngliche Nachricht----- Von: django-users@googlegroups.com [mailto:django-us...@googlegroups.com] Im Auftrag von Brian Neal Gesendet: Samstag, 11. September 2010 02:05 An: Django users Betreff: Re: PayPAL-IPN-request doesn't call the view On Sep 10, 12:01 pm, Bill Freeman <ke1g...@gmail.com> wrote: > > My advice is to protect everything with try or by using get, > log your progress (we had a logging model, but you can > also append to a file, wrapping everything in a try-finally > that closes the filehandle to be sure things get flushed > out), and when you get something you haven't provided > for, log the contents of request.POST. It will be something > simple, such as there's some field they no longer provide > or don't always provide. I have to echo Bill's advice here. Use the Python logger generously in your IPN view handling code. Paypal has a habit of subtly changing their API or their POST parameters periodically. Anyway, unless you are getting hundreds of IPN's a day, I'd log all kinds of stuff to a file and study it to see where it is going wrong. Good luck, BN -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
