[Done v1.3.6] bug with state selection check on registration

[DrByte]

That's great Dr. Byte, I will refrain from doing any further work for now then!

Is the official bug fix going to hide the state field when it is not required?

Thanks,
Jeff

Yes .

[ben_golant]

DrByte - this code has been in testing for some time now - since the 6th I believe - as of the 18th, do you have an ETA for this fix? Many businesses are reporting sharply reduced sales and are thus quite significantly impacted - so any ETA you could provide would be welcome news.

Thanks.

[jetx]

Can't you just roll back to your previous version?

I can't figure out people who rely on internet sales so much and yet take a huge risk in going live with an upgrade before they (you) have fully tested it.

What I did was this: installed all security patches to existing shops, installed 1.35 on a testing server (but could also be your service prodiders server, another directory), spend time looking at everything, every calculation, rounding, tax, etc, etc.

anyway, end of rant.

[ben_golant]

Look - innocent store owners upgrade because they receive a Security Advisory to do so. They upgrade - all appears to look and test ok - and then code problems emerge.

Store owners can't know that there are rather arcane bugs as this one is - the question I raised was - as there is a code-fix in testing - could DrByte or Ajeh just indicate when that fix might be released.

[Shelia]

Any ETA on fix?

[dbrewster]

I have seen no complaints since I added these lines to this popup error message:

Until a fix is available:

includes/languages/[your custom template directory]/english.php (or your preferred language define)

define('ENTRY_STATE_ERROR', 'Your State must contain a minimum of ' . ENTRY_STATE_MIN_LENGTH . ' characters.\n\n **If you cannot complete your edit or selection of your state, this is a software error. Please *close* your browser window, reopen, restart your registration and select state before hitting Submit.\n\n We regret the error. Thank you for your patience.');

This at least will tell customers what is going wrong and what to do about it. For a workaround, all they have to do is close the browser window and reopen it. This is slightly aggravating but at least does not result in lost sales. The problem is in how to instruct customers what to do until you have a fix.

---Diana

[Badabing]

Unfortunantely, that doesnt really help if you have an international store where customers CANNOT choose any country. Has "some" impact on sales...

[imac]

Can't you just roll back to your previous version?

You can. But that's almost twice the work. And moving on is always preferable to moving back. More to the point, what do you roll back to? The new version included a fix for what was an even bigger bug in the previous version. So fixing it would mean rolling back two versions, not just one

What I did was this: installed all security patches to existing shops, installed 1.35 on a testing server ... spend time looking at everything, every calculation, rounding, tax, etc, etc.

So did I. Over several days in fact. But you can't cover all the bases all the time. I only discovered this bug myself by accident 2 days after we'd gone live. If the good Doctor himself needs 2 weeks to test it then how can mere mortals be expected to do it in less?

- the question I raised was - as there is a code-fix in testing - could DrByte or Ajeh just indicate when that fix might be released.

Personally I find that coding is painstaking work, best done at your own pace, without deadlines or anxious bystanders breathing down your neck. And I also happen to think that things would be much better (in the rest of the world, outside Zen Cart that is) if more people stopped promising things they never intended to deliver.

On the other hand, we are talking about ecommerce. With my store-owners hat on for a moment, it has to be said that rocking and rolling back and forward over the same-old ground does entail some kind of cost - of opportunity if nothing else... When you're doing that you're not getting on with something else. So, if the fix is weeks away it may well be worth patching or rolling back. But if it arrives five minutes after you've spent half a day carefully undoing what you've already spent several days doing, then you'd probably be kicking yourself. So, on balance, I'd have to say that some kind of loose - hassle free - no sweat - laid-back - ball-park kind of feedback on the sort of timescale we might be looking at - could have its attractions

[JeffD]

I feel certain that the development team is working very hard to get an update out to correct the problem as soon as humanly possible. There are many different store configurations to test, many different browsers to test against as well as three different UI's in the store which require this fix be applied. The result is it takes time to test all of the permutations. I can tell you from testing that the proposed solution as of a few days ago works perfect under our configuration(s) and I would expect that a publically available solution will be released very soon.

Jeff

[Moebiusenterprises]

Unfortunantely, that doesnt really help if you have an international store where customers CANNOT choose any country. Has "some" impact on sales...

actually, once I installed the workaround snippet, I've not had any problems. We also work with an international customer base, so it's not causing a problem there.