the problem with those zoom levels is: you can only specify a max. number
of zoom levels for the OpenLayers API per map.
Unfortunately, the maximum zoom layer for the hill shading layer is smaller
than the one for OSM and Google maps.
I could build an option so you can specify the number of zoom level in the
plugin configuration, but the users of your site can turn the hill shading
layer off interactively, and in that case you would set a limit that could
"do better" with hill shading switched off...
I'm not sure how to solve this *completely*, but that new parameter could
at least avoid the pink map problem - any better ideas??
I do not like one thing. When I zoom in the map to its extreme value I get a pink background and broken picture symbols (you can check on this site homepage as well). I think this should be solved somehow otherwise it gives the user the feeling that something is wrong/there is an error.
I propose that after reaching the maximum zoom simply you should not let to go further.
The problem appears only when hill shading is on.
Better later than never, you shall find attached the hungarian translation for version 1.2.3beta.
The plugin works without any errors but I have one remark: in case the distance units used are set to e.g. metric it would be nice if - when using template no. 6 or any other template - only data calculated for metric units would be displayed. The same for speed diagramm: if I set not to show speed diagramm the layout no. 6 should not show an empty speed diagramm with the header.
I can modify now the layout html file as I wish but this should be handled automatically.
I tested it with custom waypoint symbols and their positioning relative to the coordinates of the waypoint.
Also tested the BCC code in the waypoint popups.
Everything works fine.
GPXTrackMap was a great extension up to now, but with the new features it really becomes an outstanding extension!
Thanks a lot.