Tell us what you are trying to do?
Display a map
Is there any documentation that you are following?
No
Is there a similar example that we can see?
hidden link
What is the link to your site?
hidden link
Hi,
Thank you for contacting us and I'd be happy to assist.
From your message, the requirement about the map is not clear, but, in most cases, an address type field is needed to show map markers connected to posts on the map.
Here is the guide on adding an address type field, using the Toolset Maps plugin:
https://toolset.com/lesson-placement/lesson-placements-1622939-1625485/
Once, you have saved the post's location using this address field, you can show a map with this post's location marker, on the single post page:
https://toolset.com/lesson-placement/lesson-placements-1622939-1621393/
And to show the map markers of multiple posts on a single map, you can create a view, as explained here:
https://toolset.com/lesson-placement/lesson-placements-1622939-1620853/
I hope this helps and please let me know if you need any further assistance around this.
regards,
Waqar
Hello Waqar, I am struggling with Google map functioning.
Thanks for writing back.
From the error message, it seems that the APIs necessary to geocode addresses are not active for this key.
In your Google Maps Platform dashboard, click the blue "Enable APIs and Services" button and enable Places, Geocoding, and Geolocation APIs to start with. Then try to test the API again at Toolset > Settings > Maps tab.
I hope this helps and please let me know how it goes.
Hello Waqar,
I followed your instructions, and at least a map shows up, but so does the same message. Perhaps its the IP address, what IP address should I be using, my server or my ip location on map?
I'm not seeing the same error when I use the check API button, so it looks like you've removed the IP restrictions from your Google Maps API key.
( screenshot: hidden link )
When only the main/primary key is added, it is used for both the client-side and the server-side requests.
The key with IP/domain restriction works for the client-side requests, but not for the server-side ones. To overcome this limitation, the second optional key field was introduced.
When you'll include a second optional key, that will be used for the server-side requests, allowing you to use a primary key with the IP/domain restriction turned on.
If your hosting server has a static IP, you can optionally enable IP/domain restrictions on the second key too, but it is not necessary, since this second key for the server-side requests is not publicly exposed.
I hope this explanation helps.
My issue is resolved now. Thank you!
