-
Notifications
You must be signed in to change notification settings - Fork 15
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
Ability to have auto generated Zip Codes #25
Comments
Zipcodes/postcodes aren't always that easy. For example, in England the same town can have numerous codes depending on which part of the town they are in. Or do you mean have a drop down box with all the options? |
I mean a dropdown with options. Countries with one zip code like Uganda would have that auto-filled in so save some time and errors for shop owner. |
I just wanted to say this is a bad idea for the US. Most larger cities have multiple zip codes. In New York City, for example, there are multiple boroughs (Brooklyn, Queens, Bronx, etc.). Each one has dozens of zip codes. So if I enter Brooklyn, NY there would be 47 zip codes to choose from. That's a long list of numbers. Not good for UX. The goal is to make this easier and pre-fill info if possible for the user. What we've done instead is to ask for zip code first, then use Google Maps API to get city/state/country and pre-fill those fields. So instead of pre-filling 1 field, we pre-fill 3 fields for the user. Saves more time. They can also edit those fields in case we got it wrong. Here's an example: We probably can't use Google Maps API, so we need to find a zip code database/API to use. |
This is good feedback. I come from a continent where we have one zip for a whole country.
CC has its own hard coded location information in files. I guess this is to remove the requirement for a internet link if one is setting up offline and also to check for errors in location. Is there a way we can leverage this to achieve the above? |
I'm not familiar with what location information comes bundled with CC/Woo.
Can you point me to the files or documentation?
…On Fri, Nov 22, 2019, 9:30 PM Laurence Bahiirwa ***@***.***> wrote:
This is good feedback. I come from a continent where we have one zip for a
whole country.
We probably can't use Google Maps API, so we need to find a zip code
database/API to use.
CC has its own hard coded location information in files. I guess this is
to remove the requirement for a internet link if one is setting up offline
and also to check for errors in location. Is there a way we can leverage
this to achieve the above?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#25>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM5HOGG6PWOA4GNRGDFQVDQVCITZANCNFSM4I25D2SQ>
.
|
Check the https://github.com/ClassicPress-research/classic-commerce/tree/develop/i18n folder. All files are in there |
I really wouldn't waste too much time on this. It seems to me to be a feature that sounds nice but is not important at this stage and will be very difficult to implement. As I mentioned above, England postcodes define a small area, virtually a few blocks of streets. Small cities can have many hundreds of them. It's not that hard to type in your own postcode. |
I agree it should be postponed until later version once we figure out what's the best approach. The i18n stuff is the basic stuff that's already being used, so there's nothing extra in there to do what we're discussing here. One additional alternative is to use IP location to detect the country and city. There are free databases that can be bundled with CC to do this. It's not very accurate, but can be helpful. |
This is an enhancement for a future release. Please check #102 for what’s urgent. |
Having auto complete options for state are well done but issue is that there are no auto generated zip codes to match the state on signing up the shop. See image below
It would be very nice to have zip codes generated on input of states just like country currencies codes are input on adding the country.
The text was updated successfully, but these errors were encountered: