Issues with live 2.4 deployment

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
12 years ago
Hi,  having some strange problems with a conversion from 1.9 to 2.4 on a live site, here is the most major one at the moment

1) Seeing Payment information is not entered errors with some users in checkout.  different browsers,  so far IE, FF and safari.  The user will enter their payment information / its setup for manual credit card then when they hit confirm order they get the message and it gets logged.  if they hit back the payment information is there and they go back and forth.  It seems that if if happens to someone it will always happen.  other make it through fine.  probably atleast 4 out of 10 orders tho.  I havent been able to reproduce this, but getting quite a few calls

The error
System.Exception: Payment information is not entered at Nop.Web.Controllers.CheckoutController.OpcConfirmOrder()
Presentation\Nop.Web\Controllers\CheckoutController.cs:line 1369

page URL : /checkout/opcconfirmorder/
12 years ago
Just confirmed that its both manual and purchase order

Thx
-Keith
12 years ago
I presume that your site is hosted on web farm (or any other technique which uses several servers). In this case just ensure that session state mode is set "State Server" or "Sql Server" (more info here)

P.S. Or ASP.NET session is periodically cleared on your server for some reasons
12 years ago
Thx for the quick reply,  no just shared a shared hosting account with the sql server on a seperate box and ive added the machine key also.

but I was having alot of issues with the machine key with 1.9 so maby the host has something funky going on.  ill give them a ring,  makes sense since ive had some new call thats some people can hit back and the info is there then the 2nd or 3rd time trying they can complete the order

Thx
-k
12 years ago
Andrei,  thanks for the input it was definiatly a session problem.  we moved the site to a new webserver and its flying now.  I also replace the load all paged, stored procedure with the updated one and the site is very fast now.

Thanks again
-Keith
12 years ago
I don't understand. Why do we need to select "State Server" or "Sql Server"??

why wouldn't it work with InProc.

I have run into this problem trying to upgrade our payment plugin. It basically means that the plugin will not work if you set up the site using InProc session state, which is by default.

It seems like I get this error because I am using in my plugin controller:

_httpContext.Session["OrderPaymentInfo"]


Using the constructor parameter:
HttpContextBase _httpContext 


while before I was just using
this.Session["OrderPaymentInfo"]


Is there any difference/advantage in using: _httpContext?

Hope it makes sense.

Thanks

Carlos
12 years ago
carlosmartinezt wrote:
I don't understand. Why do we need to select "State Server" or "Sql Server"??

why wouldn't it work with InProc.

You don't need to do it if you have only one server.

carlosmartinezt wrote:
Is there any difference/advantage in using: _httpContext?

No, it's the same (just injected using constructor)
12 years ago
Hi Andrei, thank you for your such a quick response as usual.

I am still having problem upgrading the SagePay plugin to 2.40 but the problem is only when using One Page Checkout.

Basically the Session object does not persist between the ajax requests.

But don't worry, i will try to re-organize to code to avoid using Session.


Thanks.
Carlos
12 years ago
Hi Carlos,
              Have you made SagePay working with 2.4 version.  

Thanks,
Rahol
12 years ago
Has anyone got SagePay to work with 2.40? I keep getting an error once installed??

thanks

Mike
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.