Algolia Places provides a fast, distributed and easy way to use address search autocomplete JavaScript library on your website. It has been designed to improve the user experience of your forms.
It harnesses OpenStreetMapās impressive open source database of worldwide places.
For details, screenshots and demos please visit the plugin page: at | Zeroqode
Levon Terteryan
Founder @ Zeroqode
Hi, I am setting this plugin now and have got a question.
While restricting the type of search results, is it possible to select 2 specific types such as address and city, instead of choosing only one type?
If possible, how can I do that?
Hi, unfortunately, it is possible to have only one type selected or all as by default.
Hi,
How do you restrict the result so that it must come from the auto complete? I.e. if a user leaves in an incomplete address or an address Algolia does not recognize then the input is invalid.
Thanks
Hi @Dimitrii,
Thanks for reaching out. In case you want to restrict the results from auto complete, you can add a button to your search and implement logic to display data only when you press the search button.
Best regards,
Zeroqode Team
After purchase of this plugin are there any monthly fees or any other costs involved in using the plugin? Specifically wondering if I need to subscribe to algolia or OpenStreetMapās?
Hi @boston85719
yes, youād need to have an algolia account
you can see the pricing details here: https://community.algolia.com/places/pricing.html
Thanks for the link.
I am confused about which choice would be better for my app based on potential costs associated.
My goal is to allow users to enter their address for the purpose of providing search results close to their location. These search results are coming from my D.B. of saved retailers and job listings. The main purpose of the plugin is only really to fetch the city, state and country once the user has inputted and selected their address.
Looking at Algolia pricing, it seems that once my app has exceeded 100,000 requests for places there is a charge of $0.40 per 1,000 requests.
My assumption is that a request is simply a user inputting their address into the search input. So for example, a user navigates to the search page, inputs a single address into the input and selects, that alone is a single request. So if the same user changes their address using the search input, that would be a second request and so this single user has made two requests.
Then looking at google pricing, which is so much more confusing than Algolia.
I have a really hard time understanding which of these two pricing structures would be used when I have the Zeroqode Fastest Google Places Autocomplete plugin used for the purposes of allowing a user to enter their address and select it from the list of choices and subsequently extracting that address city, state and country.
Could you shed some light onto the google pricing that is associated with the zeroqode fastest google places autocomplete plugin and if my assumption of the Algolia pricing is correct?
I really donāt know which google pricing is used, the SKU: Autocomplete - Per Request or the SKU: Basic Data.
Hello @boston85719, thank you for reaching out!
Yes, your assumption regarding Algolia pricing is correct. The pricing model for Google Places Autocomplete is SKU: Autocomplete - Per Request.
Best Regards,
Zeroqode Team
Thanks for the confirmation. Seems like Algolia is the way to go then.
Comparing the two looks like Algolia gives for free what Google charges $283 a month for being the first 100,000 requests a month.
Going to a higher range of 500,000 requests a month Algolia is $160 compared to Google at $1,135.
I guess the real trick to saving money on searches is grabbing the users location and having it as the default value in the input and hope they donāt even need the autocomplete.
I just bought the plugin.
Wondering if there is any way to customize the icons a bit? Mostly thinking just having the ability to change the color of the search icon.
Also the search icon is getting cut off a bit
And the border is set with a grey color border. I have my plugin element set up as seen below with no border but as seen above there is a grey border.
I also tried to add a border color of my own, but it is just overlapping the grey border so the grey border is still visible regardless of setting my own border color or having settings set to none.
And could you please let me know how I could set focus on the input? Iām thinking a easier way to ācustomizeā would be to have it hidden and show it when I click another element and once it is visible to āset focusā on it as can be done with other input elements.
I know that I can use the bubble input element but it is much slower returning suggestions, so Iād prefer to type in the plugin element.
Hi, @boston85719!
Than you for reaching out!
Weāll look into this use case and check if and how feasible to do this and get back with an update on the matter, ASAP.
Regards,
Zeroqode Team!
Thank you, I appreciate you looking into the use case of focus the input.
In the meantime, is it possible to push a fix on the bugs indicated?
The location icon being cut off on the left side, as well as the border color bug?
I am trying to implement this plugin into my app. The issues concerning the design with border colors and icon are something I am trying to workaround on my own, however, this causes me to run into other issues with workflows and functionality.
If there is a way to āclearā the algolia value, how do you do it? If there currently is not a way to clear the value, would it be possible to add a workflow event to clear the value?
Hi, @boston85719!
Iām afraid, there is no such action to trigger Algolia to reset input value via workflow. However, āClear inputā is part Algolia Element itself by pressing (x) icon after the input value is changed.
Weāve taken into consideration your feedback regarding the potential of adding a workflow action to clear the value. Weāll need to see the how feasible is to implement.
Thanks.
Regards,
Zeroqode Team!
Thanks for taking that idea into consideration.
Could you please address the bugs?
The bug concerning the location icon being cut off on the left side.
And the bug concerning the border color issue.
Hi, @boston85719!
Weāre working on it. Weāll do our best to push a fix on bug concerning icon beign cut off on the left side. As per bug concerning the border color issue, thatās the way plugin works at this moment. So, weāve already taken this case into consideration and were checking if and how possible to do this. Please bear with us while we check, it may take some time
Regards,
Zeroqode Team!
Hi, @boston85719!
Weāve tested the location icon. Unfortunately, this issue is not reproducing on our side. To help you faster and better regarding this issue, could you , please, add our support@zeroqode.com account to your collaboratorās list in Settings -> Collaboration so we could check the issue inside your application. Plus, please tell us the name of your Bubble application and page name where you develop it, it would be way easier for us to help you solve the issues.
Note: avoid the warning message regarding plan, as we are an agency and you can easily add us to your collaborators.
Regards,
Zeroqode Team!
Hi, @boston85719!
The good news- weāve fixed the border customization problem and problem with display icon. Also, weāve added focus customization for input and customization icon. Please install the pluginās latest version, refresh the browser and give it another try.
Kind Regards,
Zeroqode Team!
I just upgraded the plugin in my app. I am not seeing anything fixed, just a bit more brokenā¦sorry but I have to be honest there.
Now, the border color that is set, doesnāt even show at all.
Now, the border roundness can not be changed and is always exceptionally round - looks like a preset of 15 -20.
Now, the location icon is still getting cut off on the left side.
As you can see in the screen shot, none of the elements are any different, because they are not responding to any of the settings I put on it, such as border color, border width and border roundness.
I had upgraded the plugin. Then tested. After getting these results, I closed the app and opened it again, but still donāt get the results expected.
