State/Province data not carrying over

[lesliekirk]

If a customer creates an account and then goes to checkout, the State does not carry over to the OCST page. If a customer logs into an account and then checks out, the State does not carry over to the OSCT screen. I've updated the code for the ACAD, ACED, and the OSCT screen thinking maybe it could be something there but it didn't help. The State does appear on the ACED screen.

What should I be looking for? I didn't update the javascript file. Does it need updating?

[Matt Zimmermann]

Hi Leslie,

Can you post a link to the site so I can investigate? I have tested the process on the demonstration site and was not able to duplicate your concern.

[lesliekirk]

Hi Leslie,

Can you post a link to the site so I can investigate? I have tested the process on the demonstration site and was not able to duplicate your concern.

Sure can, go here.

[Matt Zimmermann]

Looks like this is stemming from US being the only country available. Making the following changes should correct it.

In readytheme settings (content section readytheme):
Replace this:

<script>
var theme_path = "&mvtj:global:theme_path;";
</script>

with:

<script>
var theme_path = "&mvtj:global:theme_path;";
var default_country = "&mvtj:global:store:country;";
</script>

in scripts.js:
find:

if( $select.val() === 'US')

replace with

if( $select.val() === default_country)

Also if they want the default estimate shipping "reset" to be with their country..
replace this:

$('#js-shipping-estimate-country').val('US');

with this:

$('#js-shipping-estimate-country').val(default_country);

[lesliekirk]

Coming back to this. There also seems to be an issue using the state name instead of the state 2 letter code. The state name gets rejected, the 2 letter code does not. Is it possible to put the drop down list back?

Also, there also seems to be a really back caching issue. Even after logging out of an account, when going back to the OCST screen all of the address information is there again. Is that the browser? How can it be prevented? It seems to be hanging on to the lack of state code being in the field.

[Matt Zimmermann]

Looks like there would be one more update in scripts.js.
Change:

var $countries = $('#ShipCountry, #BillCountry')

To:

var $countries = $('input[name="ShipCountry"], input[name="BillCountry"]')

As for the caching of the form data, that is built into the OCST and OSEL pages. You can remove the functionality by removing the saved fields code from the Customer Fields section on OCST and the Header on OSEL.

[lesliekirk]

As for the caching of the form data, that is built into the OCST and OSEL pages. You can remove the functionality by removing the saved fields code from the Customer Fields section on OCST and the Header on OSEL.

Yeah...that's a problem...it's caching the error the store owner keeps getting. The state field isn't being populated and it keeps perpetuating the problem.

Another oddity, she can't enter the state code in the field, she is having to enter the state name. When I tested it, I couldn't use the state name, I had to use the state code. I feel like I'm chasing the Cheshire Cat.

[lesliekirk]

ps...the update to the scripts.js file resolved the drop down menu issue - thanks!

[Jim Cockerham]

Leslie, did the above changes fix your problem? I am seeing the same thing on my site.

[lesliekirk]

Leslie, did the above changes fix your problem? I am seeing the same thing on my site.

Jim, I will have to go back in and double check what I did to make this work.