They are very light, a few cents after the first 100,000 uses in 2020. Prices are available here: https://developers.google.com/places/web-service/usage-and-billing
It can be due to several things:
– The API key is not the good one or misspelled.
– The key is limited to the wrong domain, we recommend to put domain.tld/* or *domain.tld* which makes sure to support almost everything.
– You have not enabled the correct APIs. The Places API must be enabled otherwise it won’t work. We also ask to set up Maps as a whole and Maps Javascript as well.
– You must have entered your payment card information.
To debug this part, we open the Chrome developer console (See here) and in the Console tab very often appears a red inscription from Google Maps telling you the error.
The easiest way is to start at https://cloud.google.com/maps-platform and then create the key here https://console.cloud.google.com/google/maps-apis/credentials.
Fill in “HTTP Referrer” and put your domain like this *.domain.com/*
Normally, yes! Afterwards, some people don’t meet Prestashop’s standards, but it’s rare. The best-selling modules are supported. It’s been several years since we have had a new request for adaptation.
Yes, on the address creation and order pages. This will not work on module pages without our intervention however.
Google used to allow it before but removed this feature. It is supposed to come back by 2021 and we will implement it when the time comes.
You can submit a correction to Google on this subject: https://support.google.com/maps/answer/3094088
The module can’t do anything about it, much to our regret.
Recommendations are made with the same results as Google Maps. It works everywhere on earth, even in Greenland.
We set up this system of questions-answers based on the requests we receive precisely because to make evolve the documentation attached with the plugin is binding. This allows us to react more efficiently. However, we will be happy to answer you and then complete it.
Let’s talk about it! We’re always receptive to good ideas.
Yes, but not in the context of support, which only concerns the monitoring of the implementation and correction of bugs. If it is a micro adjustment we will of course help you, however if the work is more consequent we will propose you an estimate. Our hourly rate is 60 € without VAT per hour.
Yes, all our modules are multi-language and multi-shop compatible. Configurations may change for each shop.
For Stuart and Deliver.ee, you can also define a pickup point per eShop.
About Magic Redirect 301, you can define which redirections will be used by which eshop. Note that this is automatically done by the system when creating the rules, you will not have to manage the distribution of the rules yourself.
Regarding URL Rewriter (SEO, it supports each of the different eshops separately to avoid creating duplicates.
Lonelystock (Product Isolation) separates each product in the shops but the stocks being managed in a common way in Prestashop, times and quantities are managed together. We simply followed the usual Prestashop behaviour with regard to stocks.
Simple Sitemap is natively made to manage all the complexities of multi shop and multi language, even at the level of other plugins (blogs …) when it is possible of course.
Ha this is unfortunate but certainly not insolvent. Could you clarify and describe a little bit what’s not working? Don’t hesitate to send us your back-office login and FTP (or SSH!) connection so that we can work more efficiently! Don’t hesitate to send us screenshots as well.
We generally answer within 24H working days, 48H during school holidays.
To contact us, please send us a message from the platform on which you purchased the product, so that we can easily centralize the requests and answer you as soon as possible.