Google places Autocomplete on content pages gives error

Wappler General Bugs
#21

Issue no.1 -
API Key does not save in the Wappler UI.

  • Easy way to replicate this: Add the API Key then add a ‘type’ the API Key then disappears.
  • Another way to replicate this: Add the API Key and then go and edit any other element on the page. The API Key then disappears.

The API Key I am trying to use is working fine elsewhere. Regardless, I created a new one, ensured that it works for Maps JavaScript API - and tried again. Same issue.

I am not a developer - hence using Wappler. I am not able to effectively debug a feature you have released by articulating the problem is that the key disappears from the js include.

Please explain exactly how I can identify, find and check the js include?

Issue no.2. (Maybe or maybe not related to issue no.1 - but I am no developer)
I have implemented the new feature released today - Google Places Autocomplete. This isn’t working. When dynamic data is selected - the screen whites out. When viewing in browser - page loads, no specific errors are thrown.

#22

Issue n2 is the effect of issue n1… without an API key added to the include it won’t work.

It just needs to be added here in the maps js include…

<script src="https://maps.googleapis.com/maps/api/js?key=YOUR_KEY_GOES_HERE&libraries=places"></script>
2 Likes
Bug with GoogleMaps and Api Key configuration
#23

Ok, thank you - let me try that right away

#24

@Teodor so this fixed it, thank you.

So I assume then the bugs are:

  • The API Key is not being stored by Wappler or included in the main js include -
  • The changes to the UI keep removing the key from the autocomplete component in AC?
  • The whiteout still happens with dynamic data - but works fine when rendered in browser.

Will you be providing any additional documentation? With the places autocomplete standard API response you can get the places_id (might be called place_id) without any additional api calls - with this integration it is just returning the text value.

Will we be able to get more from the autocomplete, and if we can, will this be provided in any documentation that is coming?

As a side note - if your audience is primarily non-developers (as I understand it). Sure, there are some very experienced, very smart people on this forum - but please just simplify things a little bit so it’s easier for mere mortals like me to fully understand in the first instance.

1 Like
#25

That’s an issue only affecting content pages with NodeJS, so the API key just doesn’t get added on the main page.
We will improve this in the next update.

As for your other questions, please post a different topic with the questions you are having and the features you are missing so we can add them in the next update.

2 Likes
#26

There still seems to be an issue with this. I’ve converted an input to a Google Places Auto Complete and pasted the API key but the script added to the head section doesn’t include the &libraries=places part. I found this thread trying to work out what the problem was and entered that part manually to get it to almost work. However, the console is showing a response from Google with the results but it’s not showing on the page (the dropdown doesn’t appear at all).

Google autocomplete doesn’t show results
#27

3 posts were split to a new topic: Google autocomplete doesn’t show results

#28