donweb

Definitely! I have a bookmark list with all solved and not yet found mystery caches, at the moment round about 900 positions. After i found one or some of them were stupidly archived, i delete them from the list. In the past i could use a user script to automatically mark all found, archived or disabled caches in a list and bulk delete them afterwards. With the new list i have to go throgh the complete list and mark the found or archived caches manually. That's a lot of mindless work! Some kind of filter function, just about the cache status (found, unfound archived or disabled) would be really helpful or, to say in other words, without this the new list feature is mostly useless.

Maybe for some trackable owners the traveled miles are not the primary target. This is why i think it would be good to control with a Parameter whether visited logs are posible or not. With such a parameter you can keep your GSAK settings as they are.

Looks like it works. I was able to save my listing now too.

Yes it seems to be fixed. Thank you very much! Edit: no it isn't! Now the endless loadign problem starts at teh end of step 4, size & ratings.

I'd prefer it anyway if it would be possible for experienced cachers to use the classic way to create a listing without any wizzards. It's for example totally nonsense that you have to write a reviewer note before you can save an unfinished listing. At the moment i klick through the wizzard (provided that it works), enter some dummy data and fill out the reviewer note with "bla", just to get to the classic edit page. Afterwards i delete the useless reviewer note and start to design my listing.

i try to set up a new listing. After klicking on the continue-button on the page where i can add optional waypoints, the site starts to load for several minutes before my browser says the site does not respond. I tried it with different browsers, for example Firefox 41.0.2 and Chrome 46.0.2490.80, same effect.

I think nobody would log dropping and retreiving trackables in every cache, even when using GSAK. And btw i don't want my trackables to visit thousands of caches by sleeping in the back pack of somebody but to be placed by one and retrieved by another cacher. In the end i am no longer interested in some kind of took-blocking frature because as i checked yesterday it looks like evey single trackable i ever submitted to travel is lost in the meantime and i definitely do not plan to let one travel anymore.

Hello, some geocachers pick up trackables anywhere and keep them for months. Meanwhile they "took" it in every cache they find by logging it "visited". Some user scripts and smartphone apps have the possibility to automatically log all trackables in the inventory as "visited". This makes the trackable history quite confusing. But it is a great expense for the trackable owner to delete all this logs manually. It would be really nice if the owner has the possibility to block single log types for a trackable, especially "visited" or maybe "discovered" too (for example if the tracking code has appeared on any list on the internet). Visited-logs are useful for trackables in my collection i bring to events to show them or for my personal cache counter coin or the trackable sticker on my car, but for normal travelling TBs or coins i would prefer to be able to prevent people from letting my TB visit every single cache they find. Is it possible to add such a feature to the trackable properties?