PHP error on Sellerdeck payments v16.02

[guccij]

Both for MOTO and online payments, Sellerdeck Payments return a PHP error on order download. The payment goes through, but the error pops up each time. Can't commit, refund or void via the order panel either.
Website definitely running PHP 5.6.
The attached image is an example of a void fail.
Any thoughts, gurus?

[Duncan Rounding]

Has this just started happening since upgrading to 16.0.2 Jules?

[guccij]

Yup. Was fine on v16.0.1 and v14. Also - all orders have, annoyingly, the time they were downloaded and not the time the order was placed shown in the Date Ordered tab.

[guccij]

Another annoying issue:

When issuing a refund, say after a customer returns an item, the date ordered and date shipped change to the date you issued the refund.

Am I really the only person who's seeing this?

[malbro]

Both for MOTO and online payments, Sellerdeck Payments return a PHP error on order download. The payment goes through, but the error pops up each time. Can't commit, refund or void via the order panel either.
Website definitely running PHP 5.6.
The attached image is an example of a void fail.
Any thoughts, gurus?

This is the back office of SellerDeck and is not running on your web site, it is running on your PC so it is the version of PHP on your PC that you need to check.

[guccij]

This is the back office of SellerDeck and is not running on your web site, it is running on your PC so it is the version of PHP on your PC that you need to check.

Actually no idea how to do this despite hours wasted googling. This is a Windows 10 PC with a standard installation. Why doesn't Sellerdeck just work?

[NormanRouxel]

The PHP that's erroring isn't part of Windows but is embedded in SellerDeck itself.

Put this (temporarily) into a Fragment or Product Description, Preview the page and it will tell you a lot about the embedded PHP:

!!<<actinic:block php="true">phpinfo();</actinic:block>>!!

The version number is right at the top.

[guccij]

Thanks Norman. I've done that and yes there is masses and masses of info generated. It shows the PHP version as 5.6.10.
Unfortunately I don't know what to do with that information so unless Support have a solution, I will be moving platforms.

[NormanRouxel]

That 5.6.10 is what it should say so the problem may lie somewhere else.

I don't use SellerDeck Payments so can't even try to replicate you error.

It may help others help you if you give a detailed walkthrough of the steps that produce this error.

[guccij]

As mentioned initially, both for MOTO and online payments, Sellerdeck Payments return a PHP error as the order is being downloaded. The payment goes through, but the error pops up each time. Can't commit, refund or void via the order panel either.
I can close the php error box and continue, but I'd rather not have an error at all.

--edit--

I should add that the order time issue I was also having problems with has been resolved with Support's help. There's a setting in Business Settings > Order Processing called Reset Date Ordered on Full Payment Received. This was ticked. I have unticked it now.

[Mike Hughes]

Just a random thought that might be worth checking:

I've notice that on my PC the Sellerdeck V16 executables are being limited to 'Low Restricted' rights in Kaspersky because there's an 'Error verifying signature' on the Digital Certifcate. I've had to manually set these to 'Trusted'.

Among them is something from 'The PHP group' that calls itself CGI/FastCGI.

I wonder if the two things might be related?

Mike

[guccij]

Will check. We use BitDefender but there might be a similar issue.

By the way, an update on the Business Settings > Order Processing > Reset Date Ordered on Full Payment Received thing: it is ticked by default in 16.0.2 but that's a bug which will be resolved in the next version apparently.

[Paddington Bear]

Same problem

Hi there,

I get the same problem, but I get it when I do an order download - if there are orders.
Sellerdeck 16.02, Windows 10.

It doesn't seem to cause any problems, but is obviously not good. It is clearly Sellerdeck causing the problem, not my computer.

[guccij]

That's a relief in a way. I knew it couldn't just be me.

[zgap111]

Has the problem been resolved?
- I'm holding back on updating from v16.01 because of this