Skip to content
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

Google API #76

Open
kcad opened this issue Jul 18, 2022 · 2 comments
Open

Google API #76

kcad opened this issue Jul 18, 2022 · 2 comments

Comments

@kcad
Copy link

kcad commented Jul 18, 2022

Where is the Google API information derived from? We did not see a way to add.

@tempsaint
Copy link

Just to clarify what the issue was... on a test server, we have workflow submissions waiting. When trying to approve the submission we get an error

ERROR: Could not geolocate meeting address. Please try amending the address with additional/correct details..

We are assuming that the test root server doesn't have a Maps API key set (which makes sense for a test root server) but we don't see anything in the workflow-submissions settings about Maps API or anything.

@nigel-bmlt
Copy link
Collaborator

The plugin will retrieve your gmaps key from the server configuration (via logging in to the admin page and scraping it from the google_api_key in the response from index.php) and use that.

We've talked about moving this to a BMLT server side geocode API here bmlt-enabled/bmlt-root-server#458

Unfortunately there's no nice way around it without that - we can't submit a meeting change without successful geolocation, but we don't want to make the plugin need an API key all on its own.

The quick fix is to add your real API key into the test server. If that's not workable let me know and I'll think about what other options we have.

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

No branches or pull requests

3 participants