This support ticket is created 6 years, 5 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
I have followed all instructions in order to include Maps on my website.
Since Google's new pricing I had to protect my API key to avoid piggybacking.
I restricted the key based on HTTP referrer like so (see image)
On the backend I am able to see the map next to the address field, with the pin in the correct place. The coordinates are also showing. (see admin.jpg)
On the front-end I get a map but no pin and it is centred in the middle of the ocean somewhere. (hidden link)
Maps created before protecting the API key continue to work fine. See hidden link as an example.
Nothing changed in terms of content template except the API key restrictions set on the google api key.
I can't since that API key has billing information on it. I had a key from that website stolen once and I don't want to pay thousands of dollars for someone else to use my key. The key needs to be secured.
As I mentioned, geocoding works, the map works, javascript works, so it looks to me like the problem is that the xy coordinates are not being saved properly. They are shown in the lat and long boxes on the website but for some reason they do not seem to make it to the actual map.
I checked again and this could be due to the google Maps API retired version, however i am seeing the fancybox plugin generating some errors in the console and this could be the source as well.
Could you disable this plugin and let me know ? Also the Retired API version is scheduled to be fixed in version 1.5