Skip Navigation

[Resuelto] Google Maps in China – Maps Autolocation Still Uses Google.com, Errors

Este hilo está resuelto. Aquí tiene una descripción del problema y la solución.

Problem:
In China, Toolset Maps does not work

Solution:
This is related to .com blocking in China (hence, Toolset Maps fails, as the service is from Google Maps).

But we solved this issue in Toolset Maps and you are able in the current stable release to use it as well in China.

This support ticket is created hace 7 años, 6 meses. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 5 respuestas, has 3 mensajes.

Last updated by Beda hace 6 años, 7 meses.

Assisted by: Beda.

Autor
Mensajes
#436667

Hey team,

Our website is based in China, so we use the google.cn/maps codes provided in the past by Toolset. These work fine on the front end when displaying maps, but when entering an address in wp-admin or if a user is filling out a CRED form with a maps address field, the Google autocompletion service causes problems because it's still being called from: hidden link?

I was in the US for the past few months, so I didn't notice the issue until I came back to China. Is there any snippet I can use to fix this? Thanks!

#436758

Juan
Supporter

Timezone: Europe/Madrid (GMT+01:00)

Hi George

Thanks for the feedback, and sorry for the inconveniences this might be causing you.

I reviewed the Toolset Maps, code, and we are actually just loading two scripts from the Google Maps API: one for their JS API and another for their geocode API. Nowhere in our code we do a direct call to maps.googleapis.com/maps/api/place/js, which means that this is a call strated by our plugin but not done by us.

Tying to find some information about this, I found a bug reported against the Google Maps API, that is basically this same one:
hidden link

Basically, even when using the right Google Maps API URLs that they provide for usage in China, their own responses contain traces and URLs that need to get called, and that point to the natural Google Maps APIs, not the one sin China. As a result, the autocomplete feature is compromised, and the places API cna not be entirely used in China.

I am adding my voice to that bug report to Google, but this is out of our hands to fix this, as this comes from a response provided by their own version of the API used for China, not from our own responses.

Sorry that I do not have a better answer at the moment, but I do hope it helps.

Regards.

#437032

Juan,

Thanks for your reply. Now I understand how this works. It seems that the thread you linked was closed, so I don't think Google reads it anymore. I opened a new one here:

hidden link

In the meantime, would you have any idea on how to kill that particular request IF the user is unable to connect to .com servers? Obviously some users will be outside of China, or on a VPN, but for the ones who can't connect, the page keeps loading and blocks other elements from displaying.

I found something on StackOverflow that might point in the right direction:
Thread: http://stackoverflow.com/questions/28725144/chinese-cn-api-calls-com-autocompletionservice-which-results-in-failure

Code they used: hidden link

Thanks

#437091

Juan
Supporter

Timezone: Europe/Madrid (GMT+01:00)

Hi George

Thanks a lot for the input. We will definitely be implementing something like this on Toolset Maps, even adding some visual hints to users to explain why some things are not working properly. I am adding a ticket for this right away, as I also understand this is a blosking problem for some of you.

This will surely get included in our next version, and as soon as I have a working version, we will publish an errata with a patch that you will be able to use on your site right away.

Thanks again.

#437839

Thanks, Juan!

#560758

This has been released and fixed.
I close this.

Please feel free to open new tickets in case you have other issues or questions!

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.