Skip to main content

Google Maps Marker Deprecation Warning in RP ProMap and RP ProFind

When reviewing the browser developer console on a page you may see warnings from Google Maps

Google Maps Marker Deprecation Warning in RP ProMap and RP ProFind

Overview

When reviewing the browser developer console on a page using RP ProMap Store Locator or RP ProFind Product Locator, you may see the following Google Maps message:

As of February 21st, 2024, google.maps.Marker is deprecated. Please use google.maps.marker.AdvancedMarkerElement instead.

This is a Google Maps deprecation warning, not an application error. It does not mean that your locator is broken, and it does not affect customers using your map.

Do I need to take any action?

No. Merchants do not need to make any changes to their Rose Perl settings or Google Maps configuration.

The existing google.maps.Marker functionality:

  • Continues to be supported by Google

  • Continues to display locations correctly

  • Works with existing map styles and custom configurations

  • Supports current marker labels, icons and animations

  • Remains compatible with Rose Perl’s current map and clustering implementation

The warning is normally visible only to developers or support staff who open the browser console. Regular visitors will not see it.

Why does Rose Perl still use the classic Google Maps marker?

Rose Perl previously evaluated Google’s newer AdvancedMarkerElement. However, moving entirely to Advanced Markers currently introduces compatibility and display risks for existing merchant configurations.

These include:

  • Custom map styling: Advanced Markers generally require a Google Map ID. Enabling a Map ID can override locally configured JSON map styles, including dark, silver, retro, night, aubergine and merchant-created styles.

  • Marker animations: Existing animations, including the drop animation, are not supported in the same way.

  • Custom marker displays: Lettered markers, custom uploaded marker images and certain icon or label configurations would need to be rebuilt.

  • Marker clustering: Older locator installations may still use a previous clustering implementation that is not compatible with Advanced Markers and could prevent the map from loading.

For now, maintaining the classic marker provides the most reliable experience and protects existing merchant map designs and configurations.

Is google.maps.Marker being discontinued?

Google has deprecated the classic marker in favor of Advanced Markers, but it has not announced a discontinuation date.

Google currently states that the classic marker is not scheduled to be discontinued and that at least 12 months’ notice will be provided before support ends.

You can review Google’s documentation here:

Rose Perl’s current direction

Rose Perl will keep the existing marker implementation in place at this time. The console warning is considered expected behavior and can safely be ignored.

We will continue monitoring Google’s announcements. If Google publishes an official end-of-support date, Rose Perl will provide an appropriate migration path.

The planned direction is a compatibility-based approach:

  • Locators using the default map appearance may be migrated to Advanced Markers.

  • Locators using custom JSON map styling may continue using classic markers while supported.

  • Existing marker labels, custom icons, clustering and other display features will be tested before any broad migration is released.

Our priority is to preserve merchant functionality and branding while preparing for Google’s future requirements.

What if the map is not working?

This warning by itself does not indicate a map failure. If your locator is blank, does not load locations or displays a visible error, the problem is likely unrelated.

Before contacting support, please check:

  1. Your Google Maps API key is active.

  2. Billing is enabled in the associated Google Cloud account.

  3. The required Google Maps APIs are enabled.

  4. Your API-key domain restrictions include your current storefront domain.

  5. Your browser console does not show another error, such as an invalid API key, billing, authorization or quota error.

If the problem continues, contact Rose Perl Support and include:

  • Your storefront URL

  • A link to the affected locator page

  • A screenshot of the visible issue

  • Any additional browser-console errors

  • The approximate time the issue occurred

Did this answer your question?