Skip to content
This repository has been archived by the owner on Dec 6, 2019. It is now read-only.

[Feature/Maps] Google maps no longer display #429

Open
nickwesselman opened this issue Jul 11, 2018 · 6 comments
Open

[Feature/Maps] Google maps no longer display #429

nickwesselman opened this issue Jul 11, 2018 · 6 comments
Labels

Comments

@nickwesselman
Copy link
Contributor

Describe the bug
Google maps now display with message, "This page can't load Google Maps correctly."

Sitecore Version
Reproduced on 8.2 and 9.0.

To Reproduce
Steps to reproduce the behavior:

  1. Go to http://habitat.dev.local/Modules/Feature/Maps

You can also install the Google Maps API Checker, which provides the error:

ERROR: This site doesn't seem to be using an API key. Keyless usage will soon be deprecated. Please set up and secure a key for your project.

Expected behavior
Map displays.

Screenshots
image
image

@ksbhatt1107
Copy link

We are facing same issue in using Mapfield in Sitecore 9.0.2. Is there any solution or alternative way to avoid this issue?

@nickwesselman
Copy link
Contributor Author

@ksbhatt1107 I'm not familiar with Mapfield (sounds like a 3rd party extension), but it appears Habitat would need to be refactored to support changes in the Google Maps API. Given the current plans for Habitat, no fix planned at this time.

@VadzimPapko
Copy link

@nickwesselman I am just validated that Google Maps API should be supported. added api key into JS API call and got the result:

image

Is this issue still relevant? If yes, I would refactor there.

@nickwesselman
Copy link
Contributor Author

Thanks @VadzimPapko, the workaround is relevant for others but it would still require Habitat to provide some means of configuring the API Key. We plan on replacing Habitat entirely by the end of the year, so a fix is not planned at this time.

@nickwesselman
Copy link
Contributor Author

@rpmichelson Not really the forum to discuss, feel free to ask in #helix-habitat on Community Slack.

@VadzimPapko
Copy link

Thanks @VadzimPapko, the workaround is relevant for others but it would still require Habitat to provide some means of configuring the API Key. We plan on replacing Habitat entirely by the end of the year, so a fix is not planned at this time.

got it, thanks @nickwesselman for your response there

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants