Error#11581. Invalid Data (using Coupon code)

Users are getting “Error #11581. Invalid Data. Profile description is invalid” when they apply a Pro Coupon code I created when paying with Paypal. It gives this error ONLY when coupon applied, works fine when users subscribe for a regular price.

Any Ideas what may cause this?

Again, everything works great w/o coupon codes, with coupon it goes like this:
User applies coupon, page reflects the price drop. When user fill paypal info and hit submit, it redirects back to my website (www.photigy.com) with given error code.

Please help.
Thank you in advance!

Hi Alex.

I don’t know, but we can investigate it. I’d like to look at your settings and logs. Could you please submit your site’s info using the contact form? s2Member® » Private Contact Form

If you don’t have logging enabled yet, please do so and run a new test transaction to have it logged with the error. It can be 1 cent, doesn’t have to be your regular full price, it’ll be enough for a test. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging[/hilite]

Thanks!

Thank you Cristián, I’ve just submitted s2member log using the form.
Alex

• This reply was modified 4 years, 2 months ago by  Alex Koloskov.
• This reply was modified 4 years, 2 months ago by  Alex Koloskov.

Update:

It looks like this is what plugin send to paypal :
‘L_BILLINGAGREEMENTDESCRIPTION0’ => ‘COUPON 60% off. ( Now: $13.98 / monthly ) ~ ORIGINALLY: Lighting Master / 34.95 Monthly ( recurring charge, for ongoing access )’,

128 characters

Then we getting this error:

‘L_SHORTMESSAGE0’ => ‘Transaction refused because of an invalid argument. See additional error messages for details.’,
‘L_LONGMESSAGE0’ => ‘Value of OrderDescription element has been truncated.’,

And if we look in paypal API:

OrderDescription field ->>> maximum length is 127. Warning only; API executes.

---

Now, how would I make s2Member not to include such long description?

• This reply was modified 4 years, 2 months ago by  Alex Koloskov.
• This reply was modified 4 years, 2 months ago by  Alex Koloskov.

Ok, I think I’ve fixed it, just changed description in Pro Form, made it less few characters.

Nice, I’m glad you were able to solve it! Thanks for the update. :)

I’ll notify Jason about this problem too, so it’s taken into account by the pro-form to avoid it in the future.

Thanks for the heads up on this thread.

@Alex Kolosko

Thanks for reporting this important issue.

We will certainly take steps to prevent this from happening in the next maintenance release.

Thank you guys! now working like a charm:)

Glad to hear it’s working now Alex. Thank you for the update. :)