I’m just moving to a different system. Support is going down the tubes here. There is a work around though. Go to ‘Engine’ at the top of the page and choose a different one and then return. It comes back.
Workaround doesn’t work for me. Maps are now showing nothing. Any news regarding update?
-
This reply was modified 2 years, 6 months ago by
redbikini.
@redbikini
Hello.
Please make sure that you have specified your personal API Key for the selected Engine.
APIs are right. Doesn’t show any map in frontend. Cookies allowed. Can’t change from Stamen light to another map theme.
-
This reply was modified 2 years, 6 months ago by redbikini.
Hello,
thanks for the workaround. It works for now. But it’s not a permanent solution to our problem. We are using this plugin on 100+ websites and as you can imagine with this number of installations, we are asking ourselves if bugs are still being fixed or do we have to look for another plugin because this plugin is abandoned?
Thanks!
The plugin is not abandoned and is still under active development. There have been temporary delays in releasing new versions due to increased load after PHP and WP updates. Also in the plugin directly updated JS libraries as required by the map provider. It became a requirement to provide API keys.
Hello @trsupsys,
since you marked this thread as resolved weeks ago we just checked if the bug described in our thread starter posting really has been fixed. Unfortunately we have to see that it doesn’t. So we re-set this thread to “not resolved” again.
The bug still persists, so I can re-post the exact same sentence: “When the plugin is freshly installed, maps cannot be created because they cannot be saved.”
You can easily reproduce this by installing your plugin in a fresh WordPress test website (let’s say here: https://wpsandbox.net/) and just try to save. It doesn’t work. You still have to take the workaround of toggling to another engine and toggling back to the original one. After this you can save, not before.
Since this is a clear bug, we ask ourselves if you intend to fix this?
Greetings and thank you for your work,
-doffine
This is because it is now mandatory to specify the API. We will make a fix so that in the next version MapBox will be the default instead of Leaflet.
Hi @trsupsys,
oh ok, thanks for letting us know. Would you give us a hint where the Leaflet API key can be specified and where we can get an API key for Leaflet at all?
And the second question would be: When there is an API key mandatory, why can we save the map when we toggle to another engine, toggle then back to Leaflet and just click on “save” then? We haven’t specified an API key anywhere, but just toggled the engine forth and back one time and then it works (saving the map and displaying it on the frontend, too).
Greetings,
-doffine
@doffine
That’s what we’re going to have to deal with. I’ll keep you posted.
Fix released.
Please update plugin to 1.2.17 version.
Hey @supsysticcom,
thank you for letting us know. We just updated and can confirm that this bug is fixed now and everything works fine. Great! 🙂
Thank you a lot for your work,
-doffine
