Take this scenario, a customer logs in, orders items goes to check-out and 
then presses ok. The server for some reason stops or slows way down. User 
browser times out. FreeTrade has an invoice left in an unknown state.
This happened 2x today for some reason, two different customers. I will now 
go through the code and fix what really needs to be fixed. This could be 
hard because F%^&ing MySQL doesn't support transactions. End result, if you 
are lucky the customer calls, most say F this site and never come back.

The processing needs to be more bulletproof.

Another inconvenience is the refresh on back button. Sometimes shit happens 
and you get a page that won't show, I don't know if it is a browser issue 
(IE is definitely lazy) or what. It is really irrelevant. Say you check out 
after entering your CC you go to hit the OK button.. IE generic piece of 
shit error message comes up. This happens to me at home so knowing it is 
not the server I hit back, of course the fricking page needs to hit refresh 
(The customer by this time has said hasta luego to this piece of shit 
store) and viola, all my information minus any I added/changed is there.

I remember someone else wanting to change the page refresh and Leon or 
someone saying this was done for security. This is an important issue to 
fix. Breaking the back button is one of the worst things you can do to 
novice users.

Last on my rants for today, why in the hell can't a user order some stuff, 
decide they think the site is cool, create a login, login, and have thier 
shopping cart update correctly? I know that this is setup correctly by SID 
but try it. After they go to checkout all the old stuff is in their cart so 
I know that the info is there.

Thanks,
Jon Griffin
[EMAIL PROTECTED]

Check out:
<http://www.salsablanca.com>
<http://www.jongriffin.com>



------------------------------------------------------------
To subscribe:    [EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Site:            http://www.working-dogs.com/freetrade/
Problems?:       [EMAIL PROTECTED]

Reply via email to