I'm having an issue editing content on my Prismic instance using the GeoPoint field.
Punching a Google Map link into the text field does correctly convert it to latitude/longitude points which my frontend app is able to use. However on the content entry side, the map is rendering blank - just a white box with Zoom In/Zoom Out slider and "Leaflet" text in the lower left. I've tested it in both Firefox 79.0 and Chrome 84.0 on OSX, and have disabled any adblockers or similar plugins.
What's interesting is that I can blindly click and drag the blank map to a new point and then back out of editing the document, and the [ Save to a new version / Discard my changes ] dialogue modal appears to correctly show a mini view of the streets for the location update preview.
Here are some interesting messages I found in the console output when loading a document containing a GeoPoint in the Prismic editing UI that may be of some help:
Yes, it appears to pull the correct latitude/longitude out of a pasted Google Map link, and I can even see that coordinates value changing if I blindly drag around the blank map.
The address works in our custom frontend implementation, but our content editors are not able to see the streets and map pin in the GeoPoint map preview to double check the address while creating/editing content.
I just had a client point out to me that the map in Prismic is not working, that's how I got on this thread.
It looks like part of the issue is that the map style is no longer supported by your map provider.
{
message: "Classic styles are no longer supported; see https://blog.mapbox.com/deprecating-studio-classic-styles-d8892ac38cb4 for more information"
}
Is there any indication when this issue will be resolved ?
Hello @spayne, we totally understand that this is, indeed, a bad user experience when using the writing room. We're trying to prioritise this as much as we can. When I get news about this I'll come back to this thread to inform everyone.
Hello everyone, and also, welcome to the forum @flexer !!
Just wanted to let everyone know that this is now a High priority task and we'll solve this as soon as we can. I'll keep everyone updated in this same thread when the fix is ready.
Hello everyone, we understand that this can become frustrating and bring you and uncomfortable user experience. We're working on releasing changes that include this fix.
Update: The fix is currently being progressively released.
Repositories that are not using GraphQL and Integration fields can request access to the fix right now, you just need to send over the URL of your repositories in a private message and we'll activate the fix for you.
For everyone else, you just need to wait a little longer until the fix is deployed for every single Repository cluster.
Thanks a lot
1 Like
system
(system)
closed as resolved, flag & select 'Something Else' to reopen.
22
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.