Browser Caching Issues

[lesliekirk]

This type of request should be handled via a ticket; there's no way to determine what unique characteristics a given store's cache config may give it without looking at it. It may not even have cache enabled, but even if it did, it doesn't apply to pages that involve a session, which ocst, osel, and opay always will if it's a real check-out and not an empty basket just hitting links.

Thanks David, I was in the process of starting one and the store owner said he wanted to investigate more on his end. I don't think he has cache enabled.

[ILoveHostasaurus]

This type of request should be handled via a ticket; there's no way to determine what unique characteristics a given store's cache config may give it without looking at it. It may not even have cache enabled, but even if it did, it doesn't apply to pages that involve a session, which ocst, osel, and opay always will if it's a real check-out and not an empty basket just hitting links.

[lesliekirk]

I wasn't sure where to put this, it is Miva related but it also involves issues with browsers holding data. Store owner placed an order for a customer using Firefox. He then went to place another order for a different customer. His browser retained ALL the information from the previous order including the basket contents. By coincidence his site was moved just moved as part of the Miva's updating. The store owner thinks it was the move that is causing the caching but I think it's the browser. Firefox seems notorious for holding information.

Now to get to my question - should I change any of the Cache Page settings for the checkout and basket pages? Currently the BASK, OCST , OSEL and OPAY are "Cache Only if the Basket is Empty and No Customer is Logged". Should they be changed to "Never Cache This Page"?