LinkPoint and Error SGS-005000

[tstamplis]

I talked with linkpoint API today as I had another issue with an order. They confirmed it was the attributes that caused the error. Specifically, a text input field that had 240 characters in it (this is a text field used to provide layout instructions for the engraving). I THINK the code responsible for adding the attributes to the gateway submission from the linkpoint_api.php is:

// itemized contents
$num_line_items = 0;
for ($i=0, $n=sizeof($order->products); $i<$n; $i++) {
$num_line_items++;
$myorder["items"][$num_line_items]['id'] = $order->products[$i]['id'];
$myorder["items"][$num_line_items]['description'] = substr(htmlentities($order->products[$i]['name'], ENT_QUOTES, 'UTF-8'), 0, 100);
$myorder["items"][$num_line_items]['quantity'] = $order->products[$i]['qty'];
$myorder["items"][$num_line_items]['price'] = number_format($order->products[$i]['final_price'], 2, '.', '');
if (isset($order->products[$i]['attributes'])) {
for ($j=0, $m=sizeof($order->products[$i]['attributes']); $j<$m; $j++) {
$myorder["items"][$num_line_items]['options' . $j]['name'] = $order->products[$i]['attributes'][$j]['option'];
$myorder["items"][$num_line_items]['options' . $j]['value'] = $order->products[$i]['attributes'][$j]['value'];
}

Those last six lines seem to fit what I see in the linkpoint cc review screen with attribute "Name" then attribute "Value".

Now I just need to know how to remove it without damaging the rest of the code:)

[Rasyr]

if (isset($order->products[$i]['attributes'])) {
for ($j=0, $m=sizeof($order->products[$i]['attributes']); $j<$m; $j++) {
$myorder["items"][$num_line_items]['options' . $j]['name'] = $order->products[$i]['attributes'][$j]['option'];
$myorder["items"][$num_line_items]['options' . $j]['value'] = $order->products[$i]['attributes'][$j]['value'];
}

is what I tried commenting out and it gave me a blank white page. Apparently it looks for it elsewhere as well.

[DrByte]

I talked with linkpoint API today as I had another issue with an order. They confirmed it was the attributes that caused the error. Specifically, a text input field that had 240 characters in it (this is a text field used to provide layout instructions for the engraving).

It would be more helpful if they could tell you which specific fields are allowed to have which lengths, as it relates to products and options. Their API documentation does not specify *any* restrictions whatsoever. Having the details will help determine the most correct solution to the problem.

[Rasyr]

It would be more helpful if they could tell you which specific fields are allowed to have which lengths, as it relates to products and options. Their API documentation does not specify *any* restrictions whatsoever. Having the details will help determine the most correct solution to the problem.

Yeah they could be more helpful...

But, in the first post of this thread, I posted a definition of the error message which said that <item><description. field wasn't supposed to be more than 120 characters long.

And it has been verified that the Attributes are being counted towards that field. It would appear that the solution would be to NOT send Linkpoint the Attribute Information. We only send Name and Value anyways, not any addition information such as its individual costs, that is totaled into the full price.

What we are looking for is a way to NOT send those attributes to Linkpoint. We already know that if we can remove those Attributes from what is sent. Even if it is just replacing the list of Attributes with something that says Attributes Present instead of listing all of them (so that we know that they purchased something with Attributes when looking at the CC log for Linkpoint.

I just want to be able to offer multiple attributes without it causing every transaction containing them to fail.

[DrByte]

This is the part that's building attributes:

      if (isset($order->products[$i]['attributes'])) {
        for ($j=0, $m=sizeof($order->products[$i]['attributes']); $j<$m; $j++) {
          $myorder["items"][$num_line_items]['options' . $j]['name'] = $order->products[$i]['attributes'][$j]['option'];
          $myorder["items"][$num_line_items]['options' . $j]['value'] = $order->products[$i]['attributes'][$j]['value'];
        }
      }

If you put /* and */ around that block of code, it should stop sending any attrib details.

You mentioned that you tried that and got a blank page ... which suggests that you caused some sort of other problem in the file by doing so. Are you sure you didn't leave any blank lines at the end of the file?
Try step 2a from this article to help find the bug causing your blank page: https://www.zen-cart.com/tutorials/index.php?article=82

[tstamplis]

It would be more helpful if they could tell you which specific fields are allowed to have which lengths, as it relates to products and options. Their API documentation does not specify *any* restrictions whatsoever. Having the details will help determine the most correct solution to the problem.

They told me the limit was 128 characters. The specific order I called about had 240 characters in one of the attributes values and that was what caused the error. This was from a text input box attribute for describing layout instructions for engraving.

I have a feeling this is a new limit from them as I have never had this problem before and I have used 255 character text input boxes. I am going to try to use your fix noted in this thread and will report back how it goes.

Thank you for your help, it is greatly appreciated!

[DrByte]

You said:

items = Array
(
[1] => Array
(
[id] => 184:722d000d4aa3b69cc6a01b83ec227853
[description] => HARP Combat Cards PDF
[quantity] => 1
[price] => 5.00
[options0] => Array
(
[name] => Download 1
[value] => PDF
)

)

[2] => Array
(
[id] => 384:dca3197a19d64c2e93d1467573da9e4c
[description] => HARP VP 2
[quantity] => 1
[price] => 86.10
[options0] => Array
(
[name] => With Bundled
[value] => PDF
)

[options1] => Array
(
[name] => With Bundled
[value] => PDF2
)

[options2] => Array
(
[name] => With Bundled
[value] => PDF3
)

[options3] => Array
(
[name] => With Bundled
[value] => PDF4
)

)

[3] => Array
(
[id] => 182:f5b9cdbd8bb9608c6dad80b55bbf2987
[description] => HARP Gamemaster Screen
[quantity] => 1
[price] => 22.00
[options0] => Array
(
[name] => With Bundled
[value] => PDF
)

)

[4] => Array
(
[id] => 181:a6d84afbf7f94c38446c7fc11eae6de3
[description] => The Codex PDF
[quantity] => 1
[price] => 8.00
[options0] => Array
(
[name] => Download 1
[value] => PDF
)

)

)

But, none of any of those fields is greater than 128 characters.
So, I still don't have a "correct" solution for you.

You can try the option I posted earlier to avoid sending any attribute info at all.

[tstamplis]

You said:

But, none of any of those fields is greater than 128 characters.
So, I still don't have a "correct" solution for you.

You can try the option I posted earlier to avoid sending any attribute info at all.

I wondered about that too, as I didn't notice anything long in that string. Is the text in your linkpoint cc review (admin/customers/linkpont cc review) for that order the same as well?

[DrByte]

"the text in your linkpoint cc review" ??? I'm not sure I understand what you're asking about?

[tstamplis]

"the text in your linkpoint cc review" ??? I'm not sure I understand what you're asking about?

I was asking Rasyr that question. The text he posted that you quoted saying there are no fields greater than 120 characters came from his debug log. The information I used when calling Linkpoint was not from the log but from the text in the linkpoint cc review section in admin.