AbanteCart Community

Shopping Cart Operations => Support => Extension Support => Topic started by: thedarksyde on June 18, 2014, 03:54:11 PM

Title: Incorrectly Formatted Item Paypal Order with credits. V 1.1.9
Post by: thedarksyde on June 18, 2014, 03:54:11 PM
Hello I made this post http://forum.abantecart.com/index.php/topic,1716.msg7248.html#msg7248 on v1.1.8 about the issue and it wasn't addressed except for one post and no other responses.  I submitted a defect, donated money and tried whatever I could do to provide as much information as I could.  When I didn't hear anything I decided to wait for 1.1.9 to see if it was fixed.  Well today my customers said it happened again, he had a credit.  So I am making another post about it. 

The issue is when you have a credit for a customers account and they order over that amount and send the order to paypal it sends the credit value as well and it is a negative number and it breaks paypal.  Is there anything I can do to make someone look at this and fix it?  I am using default paypal.
Title: Re: Incorrectly Formatted Item Paypal Order with credits. V 1.1.9
Post by: abolabo on June 25, 2014, 09:08:28 AM
what version of paypal extension do you use? And what paypal extension you meant exactly?
Title: Re: Incorrectly Formatted Item Paypal Order with credits. V 1.1.9
Post by: thedarksyde on June 27, 2014, 10:28:11 AM
Default paypal standard. 

PayPal   Version: 1.0.1

Installed on Friday 08th November 2013 04:06:42 PM
Title: Re: Incorrectly Formatted Item Paypal Order with credits. V 1.1.9
Post by: thedarksyde on August 01, 2014, 09:26:14 AM
This is a general bump for this issue.  My business is picking up and more credits are happening now.  Please is there anything anyone can do, I can work with you to test.  I am a software tester.  I can fix the code myself if you tell me what needs to be changed and where.  I just need something. 
Title: Re: Incorrectly Formatted Item Paypal Order with credits. V 1.1.9
Post by: thedarksyde on August 13, 2014, 04:35:53 PM
Thank you this has been fixed in the original posting.