I added another payment modifier which uses the same payment provider as the PayInAdvanceModifier to the testshop.
I included the new ComplexPayInAdvanceModifier in the settings.py of the testshop.
I provided a new Test that check the is_active function of all payment_modifiers
I wrote a fix for the PaymentModifier base implementation of is_active
Main change: PaymentModifier:is_active method now uses its identifier property instead of the namespace of its payment_provider. Since the default implementation of the identifierproperty returns the namespace of the payment_provider, in default cases this should not change a thing. If, however, identity is set to a specific value, (e.g. to be able to distinguish between pretty similar PaymentModifier objects) this identity is used.
ComplexPayInAdvanceModifier
in the settings.py of the testshop.Main change:
PaymentModifier:is_active
method now uses itsidentifier
property instead of the namespace of its payment_provider. Since the default implementation of theidentifier
property returns the namespace of thepayment_provider
, in default cases this should not change a thing. If, however,identity
is set to a specific value, (e.g. to be able to distinguish between pretty similar PaymentModifier objects) this identity is used.should fix #778