James Arama

Hi @paulbarrett1952,
Thank you for your review and feedback. The google maps API is used to make it easier for searching location coordinates that are auto-populated in the map widget to add the markers. I’m all ears for a better workaround to obtain location coordinates.

@shikyo – There shouldn’t be any cap on how many markers you can have. Could you please try again with the latest plugin and let me know if you’re still experiencing the same issue with having more markers?

@daviddejoy – My apologies for the delay in response. I wanted to note that the latest plugin contains the ability to set different zoom levels for mobile, tablet and desktop environments.

@ajc31 – This should be resolved in the latest plugin update. Thanks again for raising this issue.

@hiddan @xusje – Thanks for the feedback. Wanted to let you know that latest update to plugin contains scroll zoom toggle to disable zoom on scroll.

@ralphgl – Thank you for your feedback. My apologies for the delay in response. Would you mind letting me know what browser you’re using.

Also, using your browser’s inspector tools, please share with me the errors you’re seeing in the console.

I’ve also pushed a few bugfixes in the latest plugin update (version: 1.0.6). Let me know if that version still has issues.

Thanks,

@samoreen – Thank you so much for your feedback. My apologies for the delay in response. The intention of using the google maps API is solely for auto-population of the coordinates. This way they can be saved and used within the OSM map widget. I do see your point, in that there’s no need of trying to query the google maps API if there’s no API key saved.

I’ve pushed an update to remove the use of the google maps API when no Key is added.

Cheers,
James

@xusje – Thank you for your feedback. Sorry for the late response. Wanted to let you know that the latest version of the plugin contains a scroll zoom toggle in settings.

@fcrisafi – Thank you for your feedback. I wanted to note that this is a known issue affecting the OSM map in safari. I use the Leaflet library for the map widget. Look here for more details: https://github.com/Leaflet/Leaflet/issues/7255#issuecomment-720375938

Currently monitoring the thread and will update the widget once a fix is pushed.

@cathylesliebell – Thank you for your feedback. The latest plugin update should contain the tooltip hover behavior.

@ralphgl – Thank you for your review. I’m sorry to hear that the plugin didn’t work. Using your browser’s inspector tools, are there any errors you’re seeing in the console that can help us resolve the issue you’re facing?

Mark,

One last thing to help debug what you’re seeing. Would you mind sharing any console errors you’re seeing if any in your browser’s inspector tools?

Also have you tried regenerating a new Geoapify key and Mapbox Access Token to see if anything changes on your end?

As for fontawesome; what are you seeing happen? Do you have a theme / plugin loading another font awesome library to cause a conflict? If so, there’s a toggle to not queue the library from the widget in the settings page.

Thanks,
James

@labski48 – Hi Mark, are you able to render the default map tile (OSM Carto)?

Also what version of the plugin are you running?

Thanks for reporting this. Latest update will have this resolved.