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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Don't know why they've stopped working. Can someone investigate?
I'd say this is URGENT actually. There may be a lot of websites using mlat mlon URL params in their links. I know wikipedia does. Currently all missing their markers.
...anyway hopefully it's just a little bug somewhere.
The text was updated successfully, but these errors were encountered:
Author: tom[at]compton.nu [Added to the original trac issue at 9.15am, Sunday, 1st June 2008]
They haven't really - your cookie is turning the marker layer off. If you clear your osm cookies it should work again. I need to work out why the change I made to the layer parsing isn't quite working...
Author: grand.edgemaster[at]gmail.com [Added to the original trac issue at 12.26pm, Monday, 2nd June 2008]
Cookies are not the issue here, I've cleared mine and the issue is still occuring.
I believe the issue to be caused by setMapLayers being triggered when mlat/mlon is passed and no layers param.
This issue has only just become apparent as a result of Tom's changes in r7872. If you call setMapLayers("B00T"), the markers layer will become hidden although it should remain as the default.
Reporter: Harry Wood
[Submitted to the original trac issue database at 11.29pm, Friday, 30th May 2008]
mlat, mlon URL parameters have stopped working
This is the marker functionality as described at http://wiki.openstreetmap.org/index.php/Browsing#Adding_a_Marker
example URL: http://www.openstreetmap.org/?mlat=51.57&mlon=-0.21&zoom=6
Don't know why they've stopped working. Can someone investigate?
I'd say this is URGENT actually. There may be a lot of websites using mlat mlon URL params in their links. I know wikipedia does. Currently all missing their markers.
...anyway hopefully it's just a little bug somewhere.
The text was updated successfully, but these errors were encountered: