street number is missing practical, two working solutions

yes I agree with (@tobias_conrad). following this topic for solution.

@natekinkead mentioned this situation in the topic below as well,
https://www.ads-software.com/support/topic/address-auto-fill-truncates-the-street-address/

Solution:
source: https://webapps.stackexchange.com/questions/28288/search-by-street-number-in-google-maps

@jstradersborivali
@auludag
@natekinkead

ask for the street number first in a seperate field and sent the number and the street to the google api.
This twoo seperate fields can be virtual(not save any data) and only for getting the right adress in the default WOO street field.
Practically please see the screencast: https://screencast-o-matic.com/watch/cFiFjTF5tG

Thanks for implementing
Tobias

Additionally:
Entered:
“street number streettt”
Need do you mean:
“street number street”

If somebody do not know the exact writing of the street.

@tobias_conrad and @auludag,

Thank you for your analysis and suggestions. I spent a while looking into this today.

I really want to avoid messing with the checkout fields like adding a street number field since that will likely cause conflicts with other plugins, or would mess up the styling.

Plus, that kind of solution makes the checkout form even more complex, which goes against the whole purpose of this plugin… to make checkout simple and fast.

Please consider that most of the world has the street number at the beginning before the street name, so for most people, they will not run into the issue you demonstrated because they enter their street number in first. I would rather keep it clean and simple for the majority of users.

Anyway, I can see that something needs to be done because you’re not the first to bring this up.

I was digging into the “types” parameter of the Google Places Autocomplete API because according to the docs, it sounds like that should only allow returning of precise addresses.

HOWEVER, after much troubleshooting, it turns out that it’s actually working as Google intended, but not as I envision it. After changing the “types” parameter from “geocoding” to “address”, it now doesn’t show zip codes and cities in the results, but it will still show a street name without a number. Apparently Google classifies that as a precise address???

So, the solution I came up with is to alert the customer if they select an address that is not considered a “street_address” type of place. I released version 1.9.8 which includes this new feature. After you update, you will need to go to the settings page and enter your warning text to enable it.

Let me know what you think about this solution. Thanks.

@natekinkead

Could you create a video demonstrating this new feature?

Solved nicely.

Great! Thanks!

@rabidgopher04, here’s a couple screenshots showing selecting a street without a street number and the popup that shows (you can customize your own message)… https://imgur.com/a/WxDTBOQ

Thank you!

You’re welcome!

Hi, thanks @natekinkead. but after this update, -I guess- state section are not updated automatically anymore . am i wrong?

(I am saying – i guess- because: since I updated already, i don’t know if the previous version was updating state automatically)

@auludag, can you give me the link to you site so I can check it out?

@natekinkead, sorry for late response. here revealit link.

https://revealit.me/74ffa17b68

ps: i also use checkout field editor plugin same this topic OP (https://www.ads-software.com/support/topic/city-province-not-auto-populated/)

• This reply was modified 6 years, 6 months ago by auludag.

That user and pass is not working. I still can’t view your site.

You might want to check out the solution that the other person provided for getting it to work with Checkout Field Editor.

@natekinkead updated. can you check the link inside revealitlink

https://revealit.me/4efc449f5a

The problem with customizing js files of a plugin that those changes would disappear with next updates.

• This reply was modified 6 years, 6 months ago by auludag.