Wich django-paypal fork to use

[Diego Cebrián]

I am trying to user django merchant in a project with a custom user confiured via AUTH_USER_MODEL. 

The payments must be done with paypal, and because the rely of external paypal gatway in django-paypal i get an error: 

pro.paypalnvp: 'user' defines a relation with the model 'auth.User', which has been swapped out. Update the relation to point at settings.AUTH_USER_MODEL.

Which fork of django paypal is currently mantained, Copatible with the new django user model and better working?

Thank you.

[Thejaswi Puthraya]

Hello Diego,

The fork of django paypal recommended by the docs is
https://github.com/dcramer/django-paypal But since it has not been
updated for quite some time, you are probably right that we need to
update the docs with a newer fork.

Can you please check https://github.com/spookylukey/django-paypal and
run the merchant tests for paypal and let us know everything works
fine for you?

Thanks.

>
> Thank you.
>
> --
> You received this message because you are subscribed to the Google Groups
> "django-merchant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-mercha...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.



--
Cheers
Thejaswi Puthraya
http://thejaswi.info/

[Ed Patrick Tan]

Hi Thejaswi,

I'm experiencing the exact issue of Diego. I tried https://github.com/spookylukey/django-paypal and ran the tests for paypal. The tests failed at testPaymentSuccessfulSignal (AssertionError: Lists differ: [] != [<django.dispatch.dispatcher.S) and testPurchase (AssertionError: 'FAILURE' != 'SUCCESS'). Do you have updates regarding this issue so that we can use Django 1.5 custom user model with django merchant?

Thanks,

Pat

[Luke Plant]

Hi all,

I maintain https://github.com/spookylukey/django-paypal which is now the official version of django-paypal (I released version 0.1.3 to PyPI recently). Please do send any patches regarding django-paypal to my repo, I will try to merge, especially if they come with tests.

I'm looking at doing some changes to django-paypal, especially the signals. I don't know if this will affect you, but feel free to add your ideas/requirements here: 

https://github.com/spookylukey/django-paypal/wiki/PayPalSignals

Thanks,

Luke

[Thejaswi Puthraya]

Hello Luke,
On merchant, we have only two signals which in some cases (eg: PayPal
offsite) are mapped to the upstream signals. For paypal integration,
we map to `payment_was_flagged` and `payment_was_successful`. Since we
don't expose the upstream's signal to the user we can migrate to the
new signals that you create without breaking backwards compatibility.

Regarding whether you should create a signal for every event or have a
general notification, my vote would be for a general notification and
let the developer handle it.

Ed,
I have created an issue [1] on merchant to keep track of the upstream
issue. As soon as django-paypal finalizes their signals we will
migrate.

[1] https://github.com/agiliq/merchant/issues/94

[Luke Plant]

This should be fixed now:

https://github.com/spookylukey/django-paypal/commit/f9a263b8ef4dd08c13075eae504bd3184a465100

I haven't done a new release, but the version on GitHub should be stable.

Luke