It is in a regular HTTP request. I actually somewhat later when someone
turned up to a gig believing they had paid as they had a confirmation
email, but the database still said pending.
There is no way the database record could get reset to 'pending'.
Execution must have passed through the
transaction.status='booked'
transaction.update_record
lines in order for the email to have been sent out. So the only explanation
seems to be that the update_record failed to carry out its task. Clearly
this is disconcerting.
The ticketing system has been running for a couple of years now and I have
not been aware of this happening before.
Peter
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
