You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I built a map with a few layers, some combinations of which I embed on a website. The way layers are named in the URL seems to have changed. That broke the website. For example, I am embedding this URL :
If the change/breakage was inevitable, some sort of notification to users would have been unavoidable.
Additional context
I believe this is related to a change from ID to UUID for layers. I found a related commit in 1b41ff0 but there is no explanation of why or whether there was an intention for this to be backwards compatible.
The text was updated successfully, but these errors were encountered:
Thanks for the report, and sorry for the inconvenience.
The datalayer id have indeed changed, and this use case seem to be missing from our test cases / radar, and I'm sorry for that.
We'll have a look now. Hopefully we'll have a fix on our side, I'll let you know!
Describe the bug
I built a map with a few layers, some combinations of which I embed on a website. The way layers are named in the URL seems to have changed. That broke the website. For example, I am embedding this URL :
https://umap.openstreetmap.fr/en/map/vol-libre-jura_980516?datalayers=3058582#11/47.2767/7.3087
That was working fine until a few days/weeks ago. Now it doesn't show the layer. The new correct URL seems to be this:
https://umap.openstreetmap.fr/en/map/vol-libre-jura_980516?datalayers=159d6396-daf5-48cf-a523-7b6c5c1be3d3#11/47.2767/7.3087
To Reproduce
See above.
Expected behavior
Valid URL should not change.
https://www.w3.org/Provider/Style/URI
If the change/breakage was inevitable, some sort of notification to users would have been unavoidable.
Additional context
I believe this is related to a change from ID to UUID for layers. I found a related commit in 1b41ff0 but there is no explanation of why or whether there was an intention for this to be backwards compatible.
The text was updated successfully, but these errors were encountered: