No worries Jason. As mentioned I'm just experimenting with trying different options within eCart at the moment. As stated, ultimately I want to build the checkout process using the individual server behaviours. And in wanting this, I been experimenting first with the eCart Checkout wizard as I want to learn the different server behaviours it adds and in what order etc. this way I can understand how to create it using the individual server behaviours that eCart provides. As a quick workaround to the mentioned bug in eCart I have saved a previous tested eCart checkout wizard generated pages....I could simply copy the portion of code from that which applies to Local Checkout and then paste that into my new project folder. I was also wondering the persistent code that's generated by Checkout Wizard, is this required by Local Checkout for it to take payments? Is can I just use manually created session variables for my form data? I understand that the persistent code is so that the stored variables can be used on an external website. I'm just trying to think in what scenario I would require that feature? I be using the paypal express button as a second payment method directly on my site where the customer enters their billing, shipping and credit card details and tugs is processed by paypal payments pro on my website page (hence local checkout) or am I missing the bigger picture....Even thought I have a form on my website that allows credit card input...do I need to use persistent variables to communicate that data with paypal?
Oh while on the subject, can I also use WorldPay as a payment provider (not at computer right now so cannot see if their is an option for that)
Also my client wanted to store payment details so a returning customer doesn't have to enter in those details again (I told her not to store card details on her website as that's a big no no concerning security). But is there an alternative where a customer doesn't have to type in their card details if they are a returning customer (a lot of websites do mask all but the last 4 digits of a card number. So I assume they store the customers card details on their website)