Managed Locations opening Google Maps
By Guest on Friday, 23 March 2018
Posted in JEvents (Free Access)
Replies 6
Likes 0
Views 1.1K
Votes 0
Hi!

We are using the Managed Locations component and found an issue when we click in the icon of the location.
When we click in the location icon the google maps opens and do a search by the name and not by the coordinates.
So, if the name is not found then the google show another location that he thinks is the place. this is wrong because it goes to another place that can be far way from the coordinates we have.
Is it possible to have google search by coordinates and not by the name?

Example:
Now the link is:
...&q=União+Desportiva+e+Cultural+Banheirense&@38.65746307,-9.04571056&ll=38.65746307,-9.04571056&z=10&iwloc=addr
If the link where:
...&q=38.65746307,-9.04571056&@38.65746307,-9.04571056&ll=38.65746307,-9.04571056&z=10&iwloc=addr
It would go to the correct place.

Thanks
Nuno Leite
Hello Nuno,

Actually this was a change in Google API recently and I think carcam had created a patch for the next release of Managed Locations. Can you please confirm carcam?

Many thanks
Tony
Guest
·
Saturday, 24 March 2018 00:28
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes, this will be available in Locations 3.5 but hopefully there will be a patch for current release by next week
Guest
·
Saturday, 24 March 2018 11:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi!

Thanks.
Guest
·
Monday, 26 March 2018 12:03
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi!

I just found that versions 3.0.17 and 3.2.16 are working fine and using the coordinates to open google.
Version 3.2.16 the plugin and the integration with jevents are ok.

Version 3.4.17 is the one that uses the name instead of the coordinates.
In version 3.4.17 the plugin and the integration with jevents have the problem.

I checked the integration with jevents and the plugin of version 3.4.12, and in this version the plugin is ok but the component integration with jevents have the problem.

In resume:
3.0.17 embedded plugin = not tested
3.0.17 integration with jevents = ok
3.2.16 embedded plugin = ok
3.2.16 integration with jevents = ok
3.4.12 embedded plugin = ok
3.4.12 integration with jevents = problem
3.4.17 embedded plugin = problem
3.4.17 integration with jevents = problem

Thanks
Nuno Leite
Guest
·
Friday, 30 March 2018 13:51
·
0 Likes
·
0 Votes
·
0 Comments
·
This is because we moved to the newer Google API in V3.4. carcam has fixed it for V3.5.

Many thanks
Tony
Guest
·
Tuesday, 03 April 2018 22:09
·
0 Likes
·
0 Votes
·
0 Comments
·
Ok.

Thanks
Nuno Leite
Guest
·
Tuesday, 03 April 2018 22:28
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post