new version of sagepay (v3) coming at end of 2014

[Sheltons]

Well made a booboo - accidentally upgraded the live site before finishing testing on our Dev!

SagePay seems to work OK so all good there but the emails seems to have been broken.

Looking at Actinic.pm to see if there were previously any custom settings from the original developer as I know this file was replaced.

We are hosted on 1and1 and have always had localhost in the SMTP field with no authentication.

Any suggestions would be welcome.

Got an Old laptop with 11.0.5 on so going to try and rollback on the live for now.

John

Getting to the bottom of this one. It does appear that our Actinic.pm had been altered by the original developers and the changes appear to be those suggested by Norman Rouxel in his post http://community.sellerdeck.com/show...4&postcount=68.

I am going to apply the changes to the New Actinic.pm and see if it fixes it. But before that I will give "mrvnet.kundenserver.de" in the SMTP field a try, maybe I wont then need to change the Actinic.pm file.

John.

[Sheltons]

SMTP Broken

Well made a booboo - accidentally upgraded the live site before finishing testing on our Dev!

SagePay seems to work OK so all good there but the emails seems to have been broken.

Looking at Actinic.pm to see if there were previously any custom settings from the original developer as I know this file was replaced.

We are hosted on 1and1 and have always had localhost in the SMTP field with no authentication.

Any suggestions would be welcome.

Got an Old laptop with 11.0.5 on so going to try and rollback on the live for now.

John

[printerbase]

You could try:

Close SellerDeck take a copy of your entire site folder, upgrade and then try it.

If it goes pear shaped just restore the original site folder and start again.

Peter

[kev67]

Cheers Louise as always

What a nightmare this appears to be, I'm ****ing bricks here over this....I'm with UKFast and I've just asked them to confirm the Perl version for me

Registering the IP address is simple enough, but it seems that it's a one shot chance and if it goes belly up, then ....................................

[peblaco]

14.0.3 update has not seemed to affect layouts. The patch was mainly to integrate a new SagePay script. If you upgrade the main issue you want to check is that you add your server IP address to SagePay and check the hosting supports the Crypt::SSLeay Perl module see here.

[kev67]

I recently received an email from SD regarding the latest V14.03 that is fine with Sagepay V3, but has anyone upgraded yet and what bugs if any, have you found as I've spent months sorting out V14.02 and I just don't fancy more months of hassle especially as V14.03 is new

Plus, this comment below bothers me

"Payment confirmation emails to the buyer and merchant are no longer supported. Order confirmation emails from SellerDeck will be sent as normal"

Does this mean that every time you receive an order, you've got to log in to Sagepay or Paypal etc to see if the customer is genuine and paid?, I see that as a bit of a pain in the rear to be honest

Thanks

[peblaco]

SellerDeck posted the new production releases available for integration with SagePay v3 see: SellerDeck for Sage Pay v3. The new patches are SellerDeck 11.0.6, 12.0.6 and 14.0.3.

[peblaco]

SellerDeck sent out an email which included a link to Sage Pay Protocol v2.23 extension – Action required with instructions, Sage Pay v3 announced the same and linked to the knowledge base article.

[Suemoo]

Thanks, I appreciate the info.

Strange that an extension isn't mentioned anywhere in official comments from either Sellerdeck or Sage Pay. All information from Sellerdeck is directed to the post that then directs you to the upgraded betas with the obvious intent that you should use them for v3 integration. So you're given the information that a solution, directed to it and then told not to use it.

Extremely poor all round, I'd say.

[peblaco]

It is possible to use SagePay after 31st without the v3 integration only if you apply to SagePay for the extension.

[Suemoo]

I absolutely understand that although, as it would be impossible to use the site with Sage Pay after the 31st without the v3 integration and that was exactly what the upgraded beta version was meant to fix I sort of expected it, in this instance, to work. Silly me, I guess.

I'll get onto support.

[peblaco]

The beta page says "Current Beta test releases of SellerDeck Ecommerce and EPOS. Beta software is of test quality only and should not be used on a live production site or a live EPOS system". To use older versions after 31st July 2015 you need to contact SagePay and ask for the extension which will allow use of old versions of Actinic and SellerDeck until 30th October 2015.

[Suemoo]

OK, this is probably one of gazillions of problems in upgrading to Sage Pay v3 that are going to be popping up now.

We're still on Actinic/Sellerdeck 11 so upgraded to the v11.0.6 beta, registered the site IP at Sage Pay and all seemed well. However, now I just get a script failure - os000008.pl when going through checkout. I'm afraid here's where my knowledge fails me and I'm not sure what to do next. I'm not sure if it's a problem with something I've done or with the new version of Sellerdeck.

TBH this kind of thing is why I'm moving the store over to a hosted, subscription plan but I would kind of like my old Actinic store to carry on until it's ready.

[malbro]

In Sellerdeck's posting today on this forum, a sticky that is closed so no replies possible, it says that we need to give SagePay the ip address of our server when upgrading to SagePay V3. What server is this? Do they mean the ip address of the website/s? If not, what server do they mean?

Sarah

They are referring to the IP address of your web site.

[saucysal]

IP Address of Server?

In Sellerdeck's posting today on this forum, a sticky that is closed so no replies possible, it says that we need to give SagePay the ip address of our server when upgrading to SagePay V3. What server is this? Do they mean the ip address of the website/s? If not, what server do they mean?

Sarah