Tracing a Java error on UC side

[ultracart]

Tracing a Java error on UC side

[perrytew]

We had a piece of code to handle empty strings being passed into integer fields. It was a big problem to address. But the code wasn't performing like it did in testing. So, we've deactivated it. Your errors should disappear now. Please test it again.

Sorry for the wreck. We've got a test case to look at in dev now. We'll get it hammered out next week.

[radiofreequebecistan]

Hi Perry,

The rollback has made the problem worse, now all I get is:

Invalid JSON.java.lang.NumberFormatException: empty String

The code on our end has not changed. This is breaking the cart and preventing users from adding items. Please advise asap. At the very least, if the code would let me know what key is causing the issue, I can set defaults, but with these error messages there's very little I can do to fix the situation

On Jul 27, 2013, at 1:22 PM, Perry Tew [email protected] wrote:

We had a piece of code to handle empty strings being passed into integer fields. It was a big problem to address. But the code wasn't performing like it did in testing. So, we've deactivated it. Your errors should disappear now. Please test it again.

Sorry for the wreck. We've got a test case to look at in dev now. We'll get it hammered out next week.

—
Reply to this email directly or view it on GitHub.

[perrytew]

I imagine you're passing empty strings to integer fields like cc month
and year. An empty string is not a valid integer. It should be a
null or a number.

The code we removed was a fix for this very issue. With the fix
removed, it's exposing the real issue. Any empty string "" is not
valid json for a number. I've got a call in the see if weekend
support can apply an old hack to work around this issue. When we
removed the misbehaving code, I don't think the old hack was put back
to help code around this issue.

Quick check: look at your month and year cc fields. See if the
default empty value is an empty string. If so, try making it a zero
for both.

select a month<\option>

[perrytew]

The prod guys reinstated the old work around for empty strings. Would you please test your site yet again?

[radiofreequebecistan]

Seems to work now, might have been cookie related? For now seems to behave as before.

jfh

On Jul 27, 2013, at 2:44 PM, Perry Tew [email protected] wrote:

The prod guys reinstated the old work around for empty strings. Would you please test your site yet again?

—
Reply to this email directly or view it on GitHub.

[perrytew]

Nope. It was some back end fix we reinstated. Well get the permanent

Sent from my iPhone

On Jul 27, 2013, at 5:08 PM, catrip [email protected] wrote:

Seems to work now, might have been cookie related? For now seems to behave
as before.

jfh

On Jul 27, 2013, at 2:44 PM, Perry Tew [email protected] wrote:

The prod guys reinstated the old work around for empty strings. Would you
please test your site yet again?

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/12#issuecomment-21672546
.

[radiofreequebecistan]

OK, let me know when you have the new fix in and I'll test on our cart before turning traffic on to it again.

jfh

On Jul 27, 2013, at 3:40 PM, Perry Tew [email protected] wrote:

Nope. It was some back end fix we reinstated. Well get the permanent

Sent from my iPhone

On Jul 27, 2013, at 5:08 PM, catrip [email protected] wrote:

Seems to work now, might have been cookie related? For now seems to behave
as before.

jfh

On Jul 27, 2013, at 2:44 PM, Perry Tew [email protected] wrote:

The prod guys reinstated the old work around for empty strings. Would you
please test your site yet again?

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/12#issuecomment-21672546
.
—
Reply to this email directly or view it on GitHub.

[perrytew]

The fix is in.