Sage Pay Help !!yes again!!

[roundman]

I have followed all the instructions to the letter when changing the Sage Pay URLs, but since i have done this the message i get when going thru checkout is the HTML message about transferring to a secure server, the screen does not redirect and the payment cannot be made.
I was running v8.5.1 but have upgraded to v8.5.3 in the past week, this has not changed anything.
I have spoken to Sage Pay who have told me there is nothing more thy can do for me except give me the URLs and that i should speak to Actinic.
Actinic say it is a Sage Pay problem.
I have changed the OCC files as instructed, changed the increment number by varying degrees, and checked all secret keys and passwords are correctly entered, i am still no further forward.
I have searched the knowledge base but can't see any real answers to this particular problem, so would like to know if anyone here has any ideas.
Would i be better off abandoning Sagepay and moving over to Actinic pay instead??

[Mike Hughes]

This sounds to me like the 'onload bounce' problem. A search for this will throw up quite a few threads. IIRC it's a case of needing the 'onload' javascript to be defined AND having the onload function in your header. Looking at your page I can't see the onload function definition but it's worth checking both areas.

Mike

PS. I didn't see any SSL in the checkout.

[roundman]

ok that sounds bad!!
I don't even know where to start with that!

[roundman]

I have somebody looking into it for me at the moment, they have reverted back to factory settings but this has failed to resolve it, the next button is showing within Actinic but not when published.
I have been told about the code in the top corner and is in my plan to amend soon.

[fibonacci-d]

I'm having the same problem with a client of mine - checked for the onload script and all relevant javascript in JavaScriptFunctions and all seems fine. What's more it was fine previous to the weekend and using v9.05 measn I didn't need to update any OCC files etc to cater for the move from Protx to SagePay.... odd... and as yet unresolved.
Chris