Paypal Express checkout problem - special instructions box related (?)

[zgap111]

Every week I have a customer that says they can't checkout or the special instructions they put did not appear on the final order...

So I'm looking at the past fixes I had to implement and found one called : "Paypal Express Order Box Fix.txt"

1. in OrderScript.pl, locate the line
================================================

$::g_sShippingDump = ActinicOrder::GetShippingDump();

================================================
and just after it, add
================================================

$::g_sShippingDumpEx = ActinicOrder::GetShippingDumpEx();

================================================
2. Open ActinicOrder.pm, locate the sub IsShippingInfoChanged and replace
================================================

sub IsShippingInfoChanged
{
my $sShippingDump = ActinicOrder::GetShippingDump();
if ($::g_sShippingDump ne $sShippingDump)
{
$::g_sShippingDump = $sShippingDump;
return $::TRUE;
}
return $::FALSE;
}

================================================
with
================================================

sub IsShippingInfoChanged
{
my $sShippingDump = GetShippingDumpEx();
if ($::g_sShippingDumpEx ne $sShippingDump)
{
$::g_sShippingDumpEx = $sShippingDump;
return $::TRUE;
}
return $::FALSE;
}

sub GetShippingDumpEx
{
my ($sKey, $sKeys, $sValues);
foreach $sKey (keys %::g_ShipInfo)
{
if ($sKey !~ /^USERDEFINED/)
{
$sKeys .= $sKey . "|";
$sValues .= $::g_ShipInfo{$sKey} . "|";
}
}
return $sKeys . $sValues;
}

================================================

I had a look at the OrderScript.pl & ActinicOrder.pm in Sellerdeck v18.06 and it doesn't have "sub GetShippingDumpEx"

So I searched this code my emails and found "SDCS-44807 Checkout Loop - Paypal Express Problem?"

In my notes it's : PSP-579
and I see it in the fixes in v18.00

Did Sellerdeck use a different code for this fix?

[brucet]

I can confirm that PSP-579 is the bug that was linked to SDCS-44807, and it was fixed in v18.0.0. It's possible that the final fix was not the same as the fix originally supplied to you via support.

There may also have been some rationalisation of the script in v18.0.5 when the integration with PayPal Commerce Platform was added, but I don't know if that subroutine would have been implicated.