Team Paula

Die Schweiz hat wohl noch keines... http://blog.geocaching.com/2010/11/geocaching-com-souvenirs/#

Indeed we changed (during logging) from logging the trackables with the App to logging the caches with App only and then adding the logs for TB with PC, because the App is always updating the TB-inventory when you want to add the TB-log to a cache-log. Anyway we are wondering why the log overview for the TB is correct, while map overview is confused. Does it mean that log overview is not in temporal order?

We were on the road and took some trackable with us. They were logged in the chronological order of visiting the caches and it is displayed correctly in the log overview for a trackable, e.g. for trackable TB44RCW http://www.geocaching.com/track/details.aspx?guid=df0b2d08-f0b1-4cb5-8f86-1e22ff752a05 1. Rangiertunnel 2. Smoke Pipe 3. Insterburg&Co 4. Dortmunder Stadt-Hafen IV 5. Dortmunder Stadt-Hafen II 6. Hafenbahn 7. Nachtverladung - LP 8. Altes Hafenamt 9. Dortmunder Stadt-Hafen I 10. TB-Hotel Unna/Dortmund 11. A7 Rastplatz Staufenberg (Norden) 12. [GeoGames] 176km bis Leipzig 13. A38 Leinetal Süd 14. A38 Galgenberg When now viewing on the map, the way is not correctly displayed (http://www.geocaching.com/track/map_gm.aspx?ID=3425591). Now the order is: 2. Smoke Pipe 3. Insterburg&Co 4. Dortmunder Stadt-Hafen IV 5. Dortmunder Stadt-Hafen II 6. Hafenbahn 8. Altes Hafenamt 9. Dortmunder Stadt-Hafen I 10. TB-Hotel Unna/Dortmund 1. Rangiertunnel 7. Nachtverladung - LP 11. A7 Rastplatz Staufenberg (Norden) 12. [GeoGames] 176km bis Leipzig 13. A38 Leinetal Süd 14. A38 Galgenberg What the hell is wrong with the map?

Hmmm having the same and for me it seems to be related to latest Google Chrome Update. I was facing the problem for first time at friday at a PC with Chrome... on MAC still working. Today chrome@MAC updated and now caches are not clickable on the map, too.. :-/