Closed Fastjur closed 2 years ago
I'd say the best way to fix this is to integrate the Mollie API into Events directly, instead of using Payments and trying to keep products in sync with it.
@julian9499 does #374 fix (or at least improve) this? :)
Yes it does, but it will still give a non descriptive error when mollie itself won't work
I'm not sure how smart it is to show the mollie errors directly to the users, but if that is no issue we could perhaps show that until we fix this?
I think we can make a better description by adding a form where an user is able to send what they were trying to do to us
I think we can make a better description by adding a form where an user is able to send what they were trying to do to us
Why not something simple like providing a link to send an email? Or set up log monitoring for errors like this?
Currently fixing this issue by making the shopping cart evaluate it's contents when inited
don't mind the dumb product name, but the issue is indeed already fixed!
Right now, the user just gets back a very generic "Owl no, something happened" error page, and the w3cie alias email gets spammed. I think I get a couple dozen of these emails weekly:
I believe the issue occurs when a user adds
Product A
to their cart, does not check out yet, and thenProduct A
gets updated (say the description, or whatever). It is then pushed to Mollie under a new id/url, and the oldProduct A
still in the cart of the user throws the error when they attempt to check out, as far as I am aware.It's not clear to the user that one of their products is old, when the name does not get updated.
Additional context The full stacktrace we get in the email: