SOLVED: Google Map Markers and "async"-Warning

Bugs
1

Hey :slight_smile:

I’ve noticed that when using the Google Maps integration in Bricksbuilder, I get warnings regarding the deprecation of google.maps.Marker (see attached image). Google recommends using google.maps.marker.AdvancedMarkerElement instead.

The warnings state that google.maps.Marker will continue to work for now, but no further bug fixes will be provided, and support may be discontinued in the future.

I’d like to know:

  1. Is Bricksbuilder aware of this deprecation and planning to switch to AdvancedMarkerElement ?
  2. Can we still safely use the current markers in Bricksbuilder without risk of them suddenly breaking?

Would appreciate any insights from the Bricks team or other users who have encountered this issue.

Thanks!

2

Hi @Soluna ,

Yes, we are aware of the warning.

Already on our TODO list. You can use the marker as usual.

Regards,
Jenn

1 Like
3

Thanks a lot for the info! :blush:

I just noticed that I completely forgot to attach the image :sweat_smile:

4

We fixed this issue in Bricks 2.0 alpha, now available as a manual download in your account (see changelog).

Please let us know if you are still experiencing issues.

As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.

1 Like
5

Hey Timmse,
thanks for the info! I’ll have to wait with testing until Bricks 2.0 is released as a final version. I’d prefer not to upgrade the client’s site—where I got the marker warning—to the 2.0 alpha for now. Hope that’s understandable!

Cheers!

6

This is also not recommended, see my previous answer :wink: Nevertheless, it would be great if you could test it in a staging or local environment to make sure that the bug is actually fixed. We can’t reproduce every conceivable user setup/scenario in our tests, so problems can still occur in certain cases. The more input/feedback we get on alpha or beta releases, the better.

7

Hey @timmse,

just wanted to follow up now that I’ve had the chance to test this properly on a staging site.

At the time of my original post, the warning only showed up on a client’s live site – and since I wasn’t using any Google Maps on my own sites, I didn’t have a suitable staging environment to test with Bricks 2.0 alpha right away. Sorry for the confusion! :see_no_evil:

I’ve now set one up, and after creating a Map ID in the Google Cloud Console and adding it to the map settings in Bricks, the deprecation warning for google.maps.Marker is gone. Looks like it’s working great now with AdvancedMarkerElement! :white_check_mark:

Thanks again for the fix in 2.0 – and sorry it took a bit for me to get around to testing it properly!

1 Like