Hello, I just added a map element but it doesnāt work. I donāt know how it could work because the map element is not linked to the other. Can you reproduce a setup for this plugin, so as can see what is going wrong ? Maybe your plugin needs other plugin that I donāt haveā¦
We pushed an update to the plugin with addressed issues. Please upgrade to the latest version, refresh the app and give it a try.
It is recommended you delete the element and replace with a new one.
Thanks for understanding.
For newbies like me, go in plugin section and you will see on the right after the plugin name āCan Upgradeā > go and select the last version 1.8.0 in the dropdown. Delete and recreate the elements :
an input with an ID
a Google Autocomplete element, targeting an idea
some field taking the content of Google Autocomplete field : addresse name, full adressā¦
Thank you @ZeroqodeSupport and @levon, but as I told you I cannot share this app for a client. I would be happy to present it on a demo app, but I just bought the licence for my client so it is not possible to show you other things than screenshots.
I thought it was ok but then I put the form in a popup, itās final place. And then big bug here too : the suggestion list go back under the popup, as you can see.
Hi @levon, this time it seems to work well !! Thank you so much, I will continue the project but my tests are working now ! I am very happy of this update, it seems to resolve all my problems and it is a very nice solution to do what I was looking for, easily. I donāt check āmap element present on pageā because sometime it is not on the page (the searchbox is in a reusable header) and it seems to workā¦
Hi @levon sure no problem. On the home page I have a Google Automplete element for the search bar (orange button in the beginning of the above video). Whatās happening is that āGoogle Autocomplete Aās Full addressā when it is picked is being sent to the next page under the parameter ālocationā under the orange button which is a link and not a button. Then on the next page that search bar at the top is contained within a reusable element and when get location from page URL is not empty, itās taking the location from the page url parameter location. As you can see from the video, the location parameter is actually not empty so the search bar should automatically auto populate with the city since it should just be taking data from the url parameter.
On another note, the search bar has another Google Autocomplete element if a user wants to do another search of a city contained within that reusable element.
Figured doing another video wouldnāt show you much and describing it would be easier, but if you need a video to go along with this please let me know! Thanks for the help.
We updated the demo page with your user scenario regarding plugin usage.
Please refer to it as instruction how should be set for it to work.
The parameter addr is transmitted to a new page location via url on search action and in a reusable element header, when url is not empty we set state for address to populate input in header
Hi @levon, happy July 4th! I am just getting back to this now and wanted to bring something to your attention regarding plugin version 1.6.0 vs. 1.9.0 that I believe is a bug on your guysā side.
Please see attached two separate screenshots. The first one shows plugin version 1.6.0 and the second 1.9.0.
I wanted to just put a simple text on the page which is get location from page URL. As you can see in both versions of the page there is a geographic address in the page URL.
1.6.0 allows bubble to display the text fort lauderdale, fl as get location from page url but if you do the same thing using 1.9.0., 1.9.0 basically blocks bubble from getting the location from the page URL even though there are locations in both page URLs and nothing else has changed.
Ever since Zeroqode implemented the functionality requested by @mikescullion, the plugin has mot performed well at all. All sorts of bugs. In my humble opinion, I think that they should just remove that specific function as thereās an easy workaround for that feature.
The āget location from URLā works in 1.9.0 in the same way. You should just pay attention to the parameterās name, itās āaddrā and not the ālocationā.
Please see the screen shotās of the demo setup below: