"Your session has timed out" on OPAY screen

[Mike521w]

One of the sites I work on has suddenly started having a problem where users get to the OPAY screen and get a message saying "Your session has timed out". After lots of tinkering I realized that Miva is not creating the basket-id and checkout-session cookies.

I was able to work around the issue by adding a meta tag to the basket page that creates the basket-id cookie, and another meta tag to the OSEL screen that creates the checkout-session cookie.

The missing checkout-session cookie is what caused the timeout error. On a working Miva installation, that cookie is created on the OSEL screen (I figured this out by tinkering with a Miva 9 demo store).

The only change I made to my settings was on Domain Settings > Domain Details > Cookie Settings > Non-secure Miva Merchant Cookie Output. It used to be "Set only on HTTP connections..." and I changed it to "Set on both HTTP and HTTPS connections..." - this is on purpose and needs to remain. However, out of curiousity, I changed it back, wiped all my cookies and started fresh, and still got the timeout error, so I don't think this has anything to do with it.

It seems like the system has just decided to stop creating these cookies on it's own, and I can't figure out why. I'm not the only one having this problem, we were alerted to it by customers calling, so I'm sure it's not a peculiarity of my computer or my web browser.

Anyone have any idea why the system would stop creating those cookies?

[Mike521w]

Of course, 10 minutes after posting this, I figured out the problem. There was another change I made that I forgot about - I added line to our head tag content that created a cookie (completely unrelated) using the toolkit. Maybe we have to update our toolkit module or something, I don't know, but it was blocking Miva from creating it's own cookies.

The line in head tag content was:

<mvt:item name="toolkit" param="setcookie|g.cookieValue|cookieName|720|0" />

Maybe you can only set cookies once, and toolkit was doing it first, blocking Miva from doing it (one of those headers already sent issues)? Anyway, something to keep in mind for anyone else who has a similar issue - this is one thing that can cause trouble.

[satkins]

Hello Mike521w,

I just wanted to make sure you are good to go? I didn't see a domain name to try and place a test order on for you.

[Mike521w]

Yep everything is good now, thank you though