Most recent edit on 2005-10-13 15:36:58 by TomSmith

Additions:
See: BetterKnowledge, ErrorWidgetsData, StartWithTheErrors
When designing a CheckoutProcess you often build in form validation code to makesure that you PreventErrors and so that people don't submit a form that you know is going to fail. Although the form validation code saves the customer some irritation, if things are seen go wrong in your checkout process, people are rightly going to leave.
So why not, when errors occur, log where it happened and what they entered. You HAVE to know when, where, who and how any errors that occurred, so that you can maybe prevent another customer from making the same "mistake".
Of course bear in mind that it could just be the cat walking across the keyboard that caused the problem.

Deletions:
See: BetterKnowledge, ErrorWidgetsData
If things go wrong in your checkout process, people are rightly going to leave.
You HAVE to know when, where, who and how any errors that occurred in the checkout process happened.

---

Oldest known version of this page was edited on 2005-10-12 14:58:38 by TomSmith []
See: BetterKnowledge, ErrorWidgetsData

If things go wrong in your checkout process, people are rightly going to leave.

You HAVE to know when, where, who and how any errors that occurred in the checkout process happened.