I'm experiencing an issue with the Field Google Maps custom field in Gridbox.
I have a custom app with a Google Maps field configured in the Single Item layout. The Google Maps API key is configured through the global Gridbox Google Maps integration.
The problem is that the map does not load on the frontend and shows:
"Oops! Something went wrong. This page didn't load Google Maps correctly."
The browser console shows the following:
Google Maps JavaScript API error: InvalidKeyMapError
More importantly, when checking the request in the browser/network console, I can see that Gridbox is actually loading the Google Maps API with:
So it appears that the API key is not being passed from the Gridbox configuration to the frontend JavaScript, even though Gridbox indicates that the Google Maps integration is configured.
What I have already checked
The Google Maps API key is filled in under Gridbox → Extensions → Integrations → Google Maps.
The API key has been saved.
The integration has been published.
In the Field Google Maps configuration, the API key status shows "CONFIGURED".
The Google Maps field itself is correctly configured and used within a custom app.
I have checked the browser console and confirmed that the request contains key=undefined, rather than an actual API key.
The issue therefore does not appear to be caused by an incorrect Google API key, because the key is not being sent to Google at all.
I have also checked the page after clearing the relevant caches / doing a hard refresh.
google.maps.Marker is deprecated.
Please use google.maps.marker.AdvancedMarkerElement instead.
I assume this is unrelated to the InvalidKeyMapError, but I mention it in case it is relevant to the Gridbox implementation.
Could you please advise why the Field Google Maps component is receiving an undefined API key, while the global Google Maps integration is configured, saved and published?
Is there perhaps another setting, cache, generated configuration file, or publishing step required specifically for Google Maps custom fields in custom apps?
Or could this be a bug/regression in the current Gridbox version?
I can provide screenshots of the Google Maps integration settings, the Field Google Maps configuration and the browser console/network request if needed.
Thanks in advance for your help!
Replies are visible only to logged in members with an active subscription.