Free and Premium WordPress Plugins & Themes Forums WordPress Plugins Stratum – Elementor Widgets Advanced Google Maps Outdated
- This topic has 2 replies, 3 voices, and was last updated 21 hours, 17 minutes ago by
Alberto.
- AuthorPosts
- September 4, 2024 at 1:09 am #1663345
Cian de Staic
ParticipantHello,
Is there any plans to update the google maps widget in response to Google’s migration?
As of February 21st, 2024, google.maps.Marker is deprecated. Please use google.maps.marker.AdvancedMarkerElement instead. At this time, google.maps.Marker is not scheduled to be discontinued, but google.maps.marker.AdvancedMarkerElement is recommended over google.maps.Marker. While google.maps.Marker will continue to receive bug fixes for any major regressions, existing bugs in google.maps.Marker will not be addressed. At least 12 months notice will be given before support is discontinued. Please see https://developers.google.com/maps/deprecations for additional details and https://developers.google.com/maps/documentation/javascript/advanced-markers/migration for the migration guide.
September 6, 2024 at 7:44 am #1664342J. Davis
KeymasterThanks for your feedback. I’ve forwarded this question to our developers. We will notify you if we have any news or questions.
May 15, 2025 at 4:00 pm #1765325Alberto
ParticipantDavis,
It’s been 5 months.
Have you heard anything? Is there an actual roadmap?
Meanwhile, your updated Advanced Google Maps Stratum
is still throwing warnings in the console:As of February 21st, 2024, google.maps.Marker is deprecated. Please use google.maps.marker.AdvancedMarkerElement instead. At this time, google.maps.Marker is not scheduled to be discontinued, but google.maps.marker.AdvancedMarkerElement is recommended over google.maps.Marker. While google.maps.Marker will continue to receive bug fixes for any major regressions, existing bugs in google.maps.Marker will not be addressed. At least 12 months notice will be given before support is discontinued.
And now, this NEW WARNING message as well:
Google Maps JavaScript API has been loaded directly without loading=async. This can result in suboptimal performance. For best-practice loading patterns please see https://goo.gle/js-api-loading
So on top of the deprecation warning, we’re also getting performance best-practice issues.
As of today, there’s been no feedback. No update. No timeline.
I sincerely hope this time there will be a real response, not just “we’ve forwarded it to the devs.”
For Other Users: This thread may not receive the visibility it deserves, as it tends to get lost in general support discussions rather than a dedicated section for feature improvements. To help bring more attention to this request, please leave a “+1” below.
Thank you for your attention , I hope there will be a dedication to improving MotoPress products and listen to its clients.
- AuthorPosts
- You must be logged in to reply to this topic.