Legacy maps need api key

This support ticket is created 5 years, 11 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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Asia/Karachi (GMT+05:00)

Tagged: Toolset Maps, Views plugin

This topic contains 3 replies, has 2 voices.

Last updated by Waqar 5 years, 11 months ago.

Assisted by: Waqar.

Author

Posts

November 27, 2018 at 9:26 pm #1154094

Kristin

I am trying to:
Add an API key to my legacy map.

Link to a page where the issue can be seen:
hidden link

I expected to see:
A place to put the api Key here: hidden link

Instead, I got:
An understanding that I need to upgrade to the new maps plugin. However, I cannot find any documentation on how to easily convert the old may to the new maps plugin. The client's budget is EXTREMELY LIMITED, and I don't want to have to rebuild the map. So ideally, I could just add the API key for use with the legacy map. Can you help? If not, can you point me to an article about converting to use the maps plugin as easily as possible?

November 28, 2018 at 12:56 pm #1154688

Waqar

Hi Kristin,

Thank you for contacting us and I'll be happy to assist.

Your understanding is correct and when you'll activate the Toolset Maps plugin, you'll need to update the maps and marker shortcodes, along with the address fields that were used for the legacy plugin.

Good news is that adding these items with the newer plugin is fairly simple and intuitive and the detailed documentation is available at:
https://toolset.com/documentation/user-guides/maps/

If you'd like to programmatically update your custom fields for addresses, you'll find some useful suggestions in the following reply:
https://toolset.com/forums/topic/maps-custom-fields/#post-365805

For a more personalized assistance around custom programming, you can also consider hiring a professional from our list of recommended contractors at:
https://toolset.com/contractors/

I hope this helps!

regards,
Waqar

November 28, 2018 at 1:11 pm #1154708

Kristin

I was really hoping to be able to just add an API key to the Legacy map. Is that not possible? The map is still displaying, it just needs an API key.

November 30, 2018 at 8:27 am #1156052

Waqar

Hi Kristin,

Thank you for waiting and I apologize for not able to follow up on this sooner.

I've noticed that you've now enabled the Toolset Maps plugin and entered the Google Maps API key, which has fixed the map added through the legacy Maps plugin.

I stand corrected as I didn't know that the two plugins can be used together. Your old map is showing without any error or warnings and looks like no further action is needed.

Thank you for bringing this forward and sorry about the confusion earlier.

regards,
Waqar