Ok, and do you raise CheckoutError or CheckoutError('whatever') ?
Because the intended behaviour is to change the exception (which would
cause 500 error page) into a form error which just invalidate it and force
it to redisplay with the error message. If no error message is defined,
then you might not see anything.
Le vendredi 3 avril 2015 03:03:41 UTC+2, Wesley a écrit :
>
> Hi Mathias,
> Sure, I set this guy to my own handler which does nothing but raises
> CheckoutError directly.
> And I find that If I raise Exception('whatever'), exception raised when
> click next on page.
> I see in checkout_steps, it catches CheckoutError and I haven't changed
> the code.
>
> Strange...
>
> Thanks.
> Wesley
>
> Just to be sure and not miss something obvious: does your
>> settings.SHOP_HANDLER_PAYMENT points to your custom function?
>>
>>
>>
>> Le mercredi 1 avril 2015 10:52:56 UTC+2, Wesley a écrit :
>>>
>>> Hi guys,
>>> I hit a situation today when I have a try to customize
>>> shop_handler_payment.
>>>
>>> My customized payment handler do nothing but just raise
>>> cartridge.shop.checkout.CheckoutError exception.
>>>
>>> But, one confirmation page, when I click next button, nothing displayed
>>> on page indicating that this is error during checkout process, page just
>>> refresh and stay in confirmation page again.
>>>
>>> Is this just as designed? Or any special configurations for this
>>> behavior?
>>>
>>> Thanks.
>>> Wesley
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
