divine_comedy

Well, it seems I made too early a judgement. Tracing through the code reveals that everything is just fine except for the links and password request (which is debatable) anyway. I apologize if this caused any confusion :P

Some suggestions: If customer request a password (when he is a guest), then an error message should be displayed even when his email exists. No links should be sent in any email when the customer is a guest. especially if you are using OSCommerce's default email template. Another thing I noticed is that Guest Account creates an implicit account, but when a guest comes back and checks out (as a guest) with the same email, another account with an invalid email address ( some extension appended with the valid email address ) is created so that the guest will not receive any email. Any justifications on that weird email extension ? Feedbacks on the above points are welcome. Again, I am not trying to be critical, I thought the contribution is great. In fact I am trying to close all the loopholes. I'll even program it and contribute it when it's ready.

I haven't checked whether this is a problem. Customer gets an email after creating an order. The email contains a link to the order history page. When customer clicks on the link, he is redirected to the login page, WHERE HE CAN REQUEST A CHANGE OF PASSWORD. in my opinion this defeats the purpose of the text that NO ACCOUNT WILL BE CREATED, or does it ?

Sorry wrong post !!

Will STS work with MS3 right out of the box ? This is probably the only concern I have about this contrib. I have a store that has lots of contribs installed (around 7), and I am thinking of modifying the stock look of os commerce. Can anybody offer a suggestion on how to do this in the shortest time possible ?

Great Contribution, but there's a small bug in the get_order_totals function: if ( $i == 0 ) { $first=$col_value; $last=$col_value; ==> Added by me, otherwise with only one order in a store, the order_total for a given month will appear as zero. $i++; } else { The bug occurs when there's only one order for a given month ( I know this is not noticable when you have a live store), but I am including it so the function is functionally correct, and i notice this because my store is not live yet !! :)