New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty Target Markets config. leaves Country dropdown's empty #711

Closed
visser opened this Issue Nov 25, 2013 · 3 comments

Comments

Projects
None yet
6 participants
@visser

visser commented Nov 25, 2013

Hi gang, set up a new install of WP e-Commerce 3.8.12.1 and noticed that if I didn't fill the Target Countries via Settings > Store Settings then the Country dropdown under both Billing and Shipping were empty. A general notice only for the Adminstrator (store manager capability) should tell the user they need to configure Target Markets with a link to the Store Settings screen) and a default option should be added to the Country dropdowns or hidden from view.

@ghost ghost assigned garyc40 Nov 25, 2013

@instinct

This comment has been minimized.

Show comment
Hide comment
@instinct

instinct Nov 25, 2013

Member

@garyc40 does this happen on 3.8.13 ?

Member

instinct commented Nov 25, 2013

@garyc40 does this happen on 3.8.13 ?

@eujc21

This comment has been minimized.

Show comment
Hide comment
@eujc21

eujc21 Dec 28, 2013

This happens when I leave the target market as empty, that is under 3.8.13.
screen shot 2013-12-28 at 10 01 37 am

eujc21 commented Dec 28, 2013

This happens when I leave the target market as empty, that is under 3.8.13.
screen shot 2013-12-28 at 10 01 37 am

@JustinSainton

This comment has been minimized.

Show comment
Hide comment
@JustinSainton

JustinSainton Apr 9, 2014

Member

I still get the issue originally reported. I don't think we need to change anything on the front-end though, as originally suggested. I think we could show a simple cap-checked admin notice and that would be sufficient. Given that this is the only time we've heard this reported, I'm marking it for the next major release, as we're approaching code freeze.

Member

JustinSainton commented Apr 9, 2014

I still get the issue originally reported. I don't think we need to change anything on the front-end though, as originally suggested. I think we could show a simple cap-checked admin notice and that would be sufficient. Given that this is the only time we've heard this reported, I'm marking it for the next major release, as we're approaching code freeze.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment