+teleco1883 Posted February 25, 2006 Share Posted February 25, 2006 I've successfully logged a tracking bug when I found it, however, I'm confused on how to upload the information to the new spot it's at. The FAQ aren't helpful. Any suggestion would be appreciated. thanks much Quote Link to comment
+Markwell Posted February 25, 2006 Share Posted February 25, 2006 I've successfully logged a tracking bug when I found it, however, I'm confused on how to upload the information to the new spot it's at. The FAQ aren't helpful. Any suggestion would be appreciated. thanks much That's because you're reading the wrong FAQ. Here's my version - images are a little out of date, but the process is the same. Quote Link to comment
+Markwell Posted February 25, 2006 Share Posted February 25, 2006 Moving this to the Travel Bug forum from Getting Started... Quote Link to comment
+BlueDeuce Posted February 25, 2006 Share Posted February 25, 2006 The How to log a travel bug topic pinned at the top of this forum does pretty good too. Quote Link to comment
+Likopelli Posted March 3, 2006 Share Posted March 3, 2006 The How to log a travel bug topic pinned at the top of this forum does pretty good too. There appears to be a fly in the ointment!!! I dropped off a TB in a cache, but before I could log my drop, someone else grabbed it and logged the grab. The TB was no longer in my virtual bug bag to drop- which on a simplistic level, made sense since if I now dropped it in the cache, it would appear there but not be there. Smart software would account for the fact that I merely logged the drop after someone picked it up and it's not actually there. The ramification of all this was that I could only post a note in the TBs log that I dropped it off. My drop off does not appear in the TBs mileage or map. Sorry Funky M! If anyone knows a way around this glitch, post away!! Quote Link to comment
+BlueDeuce Posted March 3, 2006 Share Posted March 3, 2006 (I hope HD doesn't hear about this!) Are you saying that someone grabbed the bug away from you before you could log the drop? Yes, there is a way to 'backlog' the drop. Could you tell me which bug it is so I can check a couple things? Thanks Quote Link to comment
+Likopelli Posted March 3, 2006 Share Posted March 3, 2006 (I hope HD doesn't hear about this!) Are you saying that someone grabbed the bug away from you before you could log the drop? Yes, there is a way to 'backlog' the drop. Could you tell me which bug it is so I can check a couple things? Thanks Funky Monkey, TB364F, in the hands of Jeo. I physically dropped it in Rocky Trinity, GCBB32. Quote Link to comment
+BlueDeuce Posted March 3, 2006 Share Posted March 3, 2006 Funky Monkey, TB364F, in the hands of Jeo. I physically dropped it in Rocky Trinity, GCBB32. Ok, this is easiest when the bug is sitting in a cache, otherwise you'll have to coordinate with the current holder to grab it back from you. I suggest just waiting until it's dropped into a cache and sitting there. 1. On the bug page, retrieve the bug from the current cache. 2. On the Rocky cache post a note POST DATED and drop the bug. ( you can just say "logging bug") 3. On the bug page, retrieve the bug from the Rocky cache POST DATED. 4. On the current cache, post a note and drop the bug. 5. On the current cache Delete the note that you dropped the bug 6. On the bug page Delete both the logs showing that you retrieved and dropped the bug in the current cache When all is said and done the bug will have the Rocky cache added to the history, the grab and the subsequent drops by others will be accurate. If this isn't clear or you have questions feel free to PM or email me. Shorter version: Retrieve the bug drop and retrieve it from the first cache, post dated drop it back into the current cache delete the your drop note on the current cache page and on the bug page delete the retrieve and drop for the current cache Quote Link to comment
+Likopelli Posted March 3, 2006 Share Posted March 3, 2006 Funky Monkey, TB364F, in the hands of Jeo. I physically dropped it in Rocky Trinity, GCBB32. Ok, this is easiest when the bug is sitting in a cache, otherwise you'll have to coordinate with the current holder to grab it back from you. I suggest just waiting until it's dropped into a cache and sitting there. 1. On the bug page, retrieve the bug from the current cache. 2. On the Rocky cache post a note POST DATED and drop the bug. ( you can just say "logging bug") 3. On the bug page, retrieve the bug from the Rocky cache POST DATED. 4. On the current cache, post a note and drop the bug. 5. On the current cache Delete the note that you dropped the bug 6. On the bug page Delete both the logs showing that you retrieved and dropped the bug in the current cache When all is said and done the bug will have the Rocky cache added to the history, the grab and the subsequent drops by others will be accurate. If this isn't clear or you have questions feel free to PM or email me. Shorter version: Retrieve the bug drop and retrieve it from the first cache, post dated drop it back into the current cache delete the your drop note on the current cache page and on the bug page delete the retrieve and drop for the current cache Thanks. I had penned (but not sent) an E-M to jeo. But Im East, hes west- could take a while to coord my- Grab from jeo, drop RT, his grab back form RT. Tomorrows Sat- he could likely drop it somewhere. I'll EM him anyway but different msg. Quote Link to comment
+BlueDeuce Posted March 3, 2006 Share Posted March 3, 2006 (edited) Thanks. I had penned (but not sent) an E-M to jeo. But Im East, hes west- could take a while to coord my- Grab from jeo, drop RT, his grab back form RT. Tomorrows Sat- he could likely drop it somewhere. I'll EM him anyway but different msg. Yes, if you coordinate it with Jeo you would just grab, post date a drop and retrieve, then have him grab it back. Good Luck. Edited March 3, 2006 by BlueDeuce Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.