|
scboston
|
November 14, 2012 at 9:53 am
As of the latest update, all attempted payments are failing with the following error:
The following errors have occurred. (270) Line item 1 is invalid.
I’ve deactivated and reactivated our Authorize.net information. We had been using the SIM setup, though we’ll use whatever is needed to make it work. Please advise.
|
|
scboston
|
November 14, 2012 at 11:31 am
Just spoke with Authorize.net. They’re saying the issue is us communicating the field of “x_line_item” to them. Further suggestions?
|
|
Tim Priebe
|
November 15, 2012 at 12:07 am
I’m using Authorize.net AIM, and I’m getting the same error message.
|
|
Dean
|
November 15, 2012 at 2:26 am
Hi,
Can you provide some more information please?
Is that the full error message or did it advise which file is generating it?
When and where does this error occur?
|
|
Tim Priebe
|
November 15, 2012 at 9:07 am
Dean,
Here’s the error I get:
Attention: your transaction was declined for the following reason(s):
Line item 1 is invalid.
Response Code: 3
Response Subcode: 1
I get it immediately after submitting payment information. I believe I first got it when going through the initial registration process. At this point, I’ve followed the payment link from the registration email, and am getting it there.
|
|
scboston
|
November 15, 2012 at 9:26 am
After many hours of Googling and reading all day yesterday, I came across suggestions on other eCommerce website forums that lead me to find that the issue seemed to be with the number of characters in the product name. It seems that Authorize.net, under certain circumstances, has trouble dealing with more than 30 characters in a line item. Given that my items were all relatively lengthy (had full location, date, session #, etc.) in them, I went through and changed them all to shortcode versions and it seemed to resolve the issue. Annoying, since it wasn’t a problem before the last series of disastrous EE updates, but a fix nonetheless.
|
|
Tim Priebe
|
November 15, 2012 at 9:59 am
Wow, that will be severely limiting if that’s the case. That actually raises another possible issue I hadn’t thought of. My event title actually has a question mark in it. Could that be causing the issue? If so, what would the workaround be?
|
|
Dean
|
November 15, 2012 at 10:05 am
Hi
I havent been able to recreate this as yet on my test server, but I have raised a ticket with the developers to look into.
|
|
Josh
|
November 15, 2012 at 10:10 am
Hi Tim,
Can you try changing the event title so that it does not include the question mark and let us know if that makes a difference?
|
|
Seth Shoultes
|
November 15, 2012 at 10:42 am
@tim Priebe and scboston are there files in your wp-content/uploads/espresso/gateways/ directory?
|
|
scboston
|
November 15, 2012 at 10:49 am
No, wp-content/uploads/espresso/gateways/ is empty for me.
|
|
Tim Priebe
|
November 15, 2012 at 10:54 am
It worked. My title was over thirty characters and had a question mark in it. I eliminated the question mark, but then had to reword it and it ended up less than thirty characters. So I’m not sure which one of those issues fixed it, but it’s fixed.
However, I really, really liked the title I was using from a marketing standpoint. When this issue gets fixed, I would greatly appreciate knowing.
|
|
Seth Shoultes
|
November 15, 2012 at 11:00 am
I will create a ticket to limit the amount of text that is sent in the title to Authorize.net. That way it will automatically strip the end of the title before posting to Authorize.net.
|
|
Davy
|
November 15, 2012 at 7:42 pm
Hi Seth – I am having the same problem. Please let me know when this is finished. Very important that we get this fixed. We have multiple events enabled and all of our transactions which are for multiple events are getting this same failure code.
|
|
Seth Shoultes
|
November 15, 2012 at 9:46 pm
Hi Joshua,
I think I found a fix, but I have not tested it completely. Which Authorize.net gateway are you using?
|
|
Dean
|
November 25, 2012 at 11:38 pm
@mhackman
Hi, the images you posted do not contain the same error described by the original poster for this thread. Can you define your issue please? IT may even be worth starting a new thread if the issue is not the same as the original posters.
Thanks.
|
|
Davy
|
November 26, 2012 at 2:00 pm
@seth Shoultes – We are using AIM. Also, I uploaded the old payment gateway files, from our initial download (3.1.26), and it is working again. I too believe that the problem is with the characters being in excess of 30. Is this fixed in the new version 3.1.28.5p?
|
|
Josh
|
November 26, 2012 at 3:08 pm
Hi Joshua,
The fix didn’t make it into 3.1.28.5.
You can manually apply the fix to the current version’s (3.1.28.5) Authnet AIM gateway by changing lines 61 and 62 of /gateways/aim/aim_ipn.php to the following:
substr_replace($item->event_name, '...', 28),
substr($item->price_option . ' for ' . $item->event_name . '. Attendee: '. $item->fname . ' ' . $item->lname, 0, 255),
|
|
Korey Kalman
|
November 26, 2012 at 10:41 pm
I experienced the same thing -> over 30 characters won’t get processed.
|
|
Seth Shoultes
|
November 26, 2012 at 10:43 pm
Korey,
Please see the fix directly above your post. If you need help with this, please let us know.
|
|
Korey Kalman
|
November 26, 2012 at 11:06 pm
Yup – that fixed it. Thanks.
|
