Lt617

On a recent trip I placed a TB in a cache site. Someone found the bug and logged it as found before I was able to get to a computer to show that I had placed it in that site. Now the bug shows as going from the cache that I originally found it in to the new one in which it was placed without showing the site I had placed it in. I tried to insert a comment but without the ID number I was unable to post a note. Does anyone know of a way to show that I placed the bug in a cache site "after" it was logged as found by another person before I could log it into the site from which it was found? I realize it isn't that big of an issue as it isn't MIA it just lacks a stop over point. Thanks

I am not sure if this has been previously discussed. It would be of great help to be able to access a cache page via at least alphabetical order (within zip code area) or at most by name of cache site. This would be especially helpful with the locationless caches but also would be helpful for a regular cache site. You would not have to scroll page by page to log in a cache. You could go right to it via a search. I know a search engine exists for travel bugs via name. The same system could be used for searching a cache site by name or a listing by an alphabetic letter or both. If necessary a unique ID number could be given to each cache site if the names are not unique enough. The unique ID number could start with a zip code (ie 96001-XXXXXX) to make the search easier and relating it to a zip code if necessary. The locationless caches could have a number like (99999-XXXXXXX). Just a suggestion. I know it would be helpful and my thoughts are shared by others as well. Thanks