recoding from a premier ticket

Hi Ray, a while back you helped me with custom shipping rules based on weight and also product options (it was quite technical the product options) in a premier ticket (back when I was using MySQL) Soon I will be recoding Dinky Fingerprint websie with a fresh design and using up to date MySQLi server extensions) My question to you is, if we do another premier ticket. is it possible to incorporate somehow the custom shipping rules and the product options in eCart control panel within Dreamweaver. Even though it was all custom code, Im am wondering if somehow eCart is able to do? I would like this very much as it keeps my code cleaner and easier to adapt in the future?

Yes, I believe that would be possible to do in a premier ticket.

So to confirm, the premier ticket you did with me a long time ago where we added custom custom on various checkout pages, we could completely remove all that and add it inside the webassist ecart object (where the shipping and other rules are)? How come we didn't do this approach originally as it seems like a much for efficient and cleaner approach?

Chris

No I doubt we could completely remove it. I think we would probably need custom code to store a session variable and then use the session variable in the eCart code.

The truth is that I don't remember the code you are referring to, but my guess is that if we could have done it all in the cart we would have.

I assumed that we stayed away from using the ecart object approach as it was easier for you to hand code since you didnt know the ins and outs of my coding structure etc or some of the things I wanted to do. Would it help if I shared some of the files that you did for me? If you had time to have a look and to recap what you did, it could give you an idea how much we can do in the ecart object? Let me attach some of the files that you did.

Chris

Since we are looking up values from the Database, it requires creating recordsets outside of the eCart object to get the proper rates. We could not do it entirely in the cart.

Ok so we ended up doing all the calculations outside of the ecart object and dos everything on the various php pages, so would it then be possible if we did all the recordsets and they were held as session variables then I could move all the calculations inside the ecart object. To keep things clean in terms of code. I guess there were a few IF statements though that were used that couldn't get moved into the ecart object. I like the idea of doing all my calculations in the ecart object as it helps with making modifications quickly in the future plus it helps revisiting the code if I left it for many months and need to revisit it for what ever reason. So the more I can do in the ecart object the better :)

That makes sense. We should be able to do the calculations from the session values in the cart once they are all stored.