If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
This is looking more and more like an android browser issue and apparently some iphones. I put some cookie displaying code in a couple of the screens. Then I went to the store with the android cell phone. I got two cookies created. I put xxxxx's below because I did not want my cookie info displayed publically. Anyway there were two instances of the first two below (ie 4 cookies) I have no idea on how you can have two cookies in the same domain with the same name. The names were the same by all 4 values were different.
Name: htscallerid Value: xxxxx
Name: mm5-wcw-basket-id Value: xxxxx
Then I went to my PC and faked that it was ok for the mobile layout. I had no issues at all. I looked at the screens which I had examined prior. This time, the above two cookies only appeared once each so they were good. But now with the PC I have two new cookies (below). The fact that Leslie had to checkin means it was looking for the customer session cookie. I am thinking the reason the OSEL to OPAY page failed was due to the missing checkout session cookie. The latter was mentioned a couple years ago related to PR7 issues, chrome, etc.
Name: mm5-wcw-checkout-session Value: xxxxx
Name: mm5-wcw-customer-session Value: xxxxx
So what does this mean? If you have an iphone you should be able to navigate ok (most of the time). If you have an android, you may have issues. I'm going to go back to my test store (where the mobile worked fine) and retest with the cookie display and see what shows up there. I'll be back in awhile.
I just tried with an android to place another order and I can't stay logged in to complete it Bill.
I was able to login but could not complete a basket because it logged me out. I too am looking to get a mobile version going to help answer Candy. I use my phone all the time for viewing and looking things up but chances are I would come back with a computer to place the order.
This may explain why Larry was not seeing a lot of sales via mobile despite active traffic. Android users are bailing. I took the conditional off the cookie display so that if you login you can look in the footer of any of the mobile screens and see what cookies are there. I suspect with Mark's iphone the customer and checkout session cookies exist but do not exist with the android. With Leslie's it would be interesting to see which of her cookies are populated.
Hi Bill: For what it's worth. I tested your mobile site with Safari/develop/user agent/iphone. Works OK for me both signed in and not signed in. If not signed in, it made me complete the order as a guest however when I tried to checkout from BASK.
Larry.
This may explain why Larry was not seeing a lot of sales via mobile despite active traffic. Android users are bailing. I took the conditional off the cookie display so that if you login you can look in the footer of any of the mobile screens and see what cookies are there. I suspect with Mark's iphone the customer and checkout session cookies exist but do not exist with the android. With Leslie's it would be interesting to see which of her cookies are populated.
So I just tried something different for fun and got my android phone to work. Instead of trying to log in using my e-mail address I just did it with the user name and had no problems. Leslie were you trying to enter your e-mail address? If so try it with just your user name otherwise Bills something is different because my DroidX works this way.
Here is some more info. I hope Miva is listening as they are the only ones who will be able to sort this out. I went back to my test store and used the same android phone which failed in the live store. At the test store checkout both the customer and checkout session cookies were populated and the checkout went fine.
Test store PR7 U10 engine 5.06 works fine
Live store PR8 U4 engine 5.12 fails with android and some iphone
The problem is how to get those two cookies populated in the phones which are failing in PR8 with 5.12 engine.
Bill - FWIW, I'm seeing the cookies in all screens. This morning I've hit some "glitchiness" - now I have to try and duplicate my steps that allowed me to make it to the checkout screen with my data populated in the fields.
Add item to basket
Click Proceed to Checkout
Click Returning Customers
Log in and it takes me to the Customer Info screen with my info populated.
Click Home
Click Basket
Click Proceed to Checkout (again)
Asked to sign in again
If I don't bail during the checkout and go back home, it now seems to keep me logged in. This is different from yesterday's results.
Just wanted to let you know we are watching this thread. We will do some testing today to see if there is a larger issue here or if it is specific settings on devices.
I figured out why the test store worked and the live store does not. The test store is in a domain without a security certificate. So when you use https the first time you get a warning. If you allow it and put it on the exception list you can proceed. So then I looked at the cookies. The customer and checkout are both supposed to be secure cookies (only viewed when secure). There is another cookie (last name) which I set and also made secure to test the theory. As it turns out, the last name cookie does not show up on any page (including https) because it is set as secure. It is not being read. However, the customer and checkout sessions are being read, so somewhere miva is setting those cookies as not secure (I think, can't tell because the mobile browser does not have a cookie inspector). This lets them be read even when the certificate is not valid as they are non-secure. Hence, I can checkout.
Now in my live store, the certificate is valid. The last name exhibits the same behavior as the test site. It cannot be read because it is secure. Since the certificate is valid, both the customer and checkout cookies are getting set secure (opposite from the test store). None of these cookies are getting read. Hence, the need to keep logging in and the inability to get past OSEL.
I'd like to test this on someone's mobile store to see if I can get to OPAY on theirs. If the inability to read secure cookies is an android-wide issue, that would take millions of potential shoppers out of the mix. Perhaps a couple other android users could hit the store and see what happens with the cookies. They are displayed in the footer of the mobile version of the store.
Comment