This is a difficult bug to describe. This bug has been around since I started using the module.

If you create a map context with only google baselayers this bug will occur, if you create a map context with :
google-physical,google,osm,oam,yahoo

this bug will not occur.

If you use only google layers, and you move the orange placement marker, it will at some random threshold, disappear.
If you add the non google layers to the context this does not happen.
John if you cannot reproduce the bug, let me know and I will make screen movies of this bug for you.

Comments

spydmobile’s picture

spydmobile commented

Just let me know how I can help debug this one John.
F

jpulles’s picture

jpulles commented
Status: Active » Postponed (maintainer needs more info)

Some more info on the exact map context will help: title, width, height, projection, extent(s), layers.

Note that including osm,oam means that the internal projection will be EPSG:900913; the display projection will in both cases be EPSG:4326 (lon/lat).

spydmobile’s picture

spydmobile commented

ok, a default map context that uses google maps (From the demos built at config time) I modified it to only show google base layers,

xml schema = ViewContext
Title = FMD Base Context
Abstract = This is a map context with several base layers. It can be used as a map context to set user and node locations.
width = 512
height = 256
srs= EPSG:4326
max extent: 
minx=-180
miny=-90
maxx=180
maxy=90
default extent:
minx=-136
miny=58
maxx=-90
maxy=70
baselayers= google-physical,google

thats it: this context will lose the marker. if I change the baselayers to be:

google-physical,google,osm,oam,yahoo

the marker will not be lost

spydmobile’s picture

spydmobile commented

bump

jpulles’s picture

jpulles commented
Assigned: Unassigned » jpulles
Status: Postponed (maintainer needs more info) » Active

Reproducing it.

jpulles’s picture

jpulles commented

Please let me know if it is solved for you in the current (july) dev release.

Regards,
John