Closed pfbreton-perso closed 1 month ago
@pfbreton-perso I think the same happened to me adding a layer accidentally as "overlay" and switching to "basemap" and again back to "overlay". The orphaned layer stays in the list of "Basemaps" and can't be removed.
I am also on latest Chrome on MacOs.
Thank you for reporting this, and providing steps to reproduce the issue. There were indeed issues when updating an existing custom layers, which I think I fixed now. If you still have those "orphaned" layers in your browser, I think creating new custom layers will overwrite them (or you can simply clear IndexedDB data from the website but you will lose all your settings).
@vcoppe I will test today. Wondering if you got my Email?
I ended up with a reference to a custom overlay that no longer exists.
Even after deleting all custom layers and refreshing the webpage I still have that orphaned entry.
I tried to reproduce the issue from scrath in a google chrome guest account but I am unable to nail it down.