Is there a way ?

[+The Sandpipers]

When logging our finds last night - I stupidly entered a TB - Walnut Man into the wrong cache . I placed the TB into the final cache of a 6 cache series yet I somehow managed to log it as being in cache # 3 of the series.

I looked for a way of retrieving it but as I no longer have the tracking number I wasnt able to. I wrote a note on both Cache #3 and Cache # 6 and e-mailed to the owner asking for the tracking number. As yet no reply, though I appreciate it is early days.

Thinking ahead - should I not hear back from the owner is there a way of being able to log a removal and logging it into the correct cache without the tracking no ?

Thanks for any help

[+pklong]

When logging our finds last night - I stupidly entered a TB - Walnut Man into the wrong cache . I placed the TB into the final cache of a 6 cache series yet I somehow managed to log it as being in cache # 3 of the series.

I looked for a way of retrieving it but as I no longer have the tracking number I wasnt able to. I wrote a note on both Cache #3 and Cache # 6 and e-mailed to the owner asking for the tracking number. As yet no reply, though I appreciate it is early days.

Thinking ahead - should I not hear back from the owner is there a way of being able to log a removal and logging it into the correct cache without the tracking no ?

Thanks for any help

 

You need the TB owners help. I would imagine they would be very keen to give you the TB number, after all they will want the TB listed in the right cache.

 

Placing a TB in the wrong cache is mistake we all make at some time and feel guilty about it.

 

Philip

[NickPick]

Call me Alan (ar an anagram of it), but I keep a database of all the tag numbers, tracking numbers and details of (almost) all the TBs I log. It's useful for just this eventuality.

 

If you don't hear from the bug owner soon, you could try asking the previous loggers of the bug if they've still got the code.

[+MartyBartfast]

I think you've made a reasonable effort to right the wrong, if you get no response from the TB owner then just forget about it. Soon enough someone will find the TB, they'll probably automatically retrieve it from the wrong cache and stick it in another cache - what's the worst that could happen? the TB will be a couple of miles out on it's mileage.

[+Glyn Morris]

Just a thought - if you go to the cache listing from where you retrieved said TB and wave your cursor over the box where you typed the code, do the cookie things not remember it as in detail boxes in general? Hope I made that clearer to you than it sounds to me!

[+Glyn Morris]

I just went to my own profile and clicked on the travel bugs found thingy and clicked on a random old TB - it's code was still there.

[+The Sandpipers]

Call me Alan (ar an anagram of it), but I keep a database of all the tag numbers, tracking numbers and details of (almost) all the TBs I log. It's useful for just this eventuality.

 

If you don't hear from the bug owner soon, you could try asking the previous loggers of the bug if they've still got the code.

 

Yes I decided after I made the mix-up last night that I would make a note of them all from now on....whether its 'alan' or not it would help to stop the ' what an idiot I am ' feeling I have right now.

[+jerryo]

I just went to my own profile and clicked on the travel bugs found thingy and clicked on a random old TB - it's code was still there.

But not the code on the bug itself that you need to create logs that move the bug around.

[+Bear and Ragged]

It could be...

Depends on when your cache (webpage cache!) was cleared!

[+jerryo]

It could be...

Depends on when your cache (webpage cache!) was cleared!

It won't be there, though, when you just click on "the travel bugs found thingy and click on a random old TB", which is what I said. It may still be there after you've entered it whilst making a log, although it's extremely unlikely to persist for very long.

[+Bear and Ragged]

Depending on when the TB was first logged as retrieved or grabbed, going back to the logging page and clicking the curser into the trackable number may bring up the tracking number in the box... Helps if you can rember the first number/letter.

 

(Works in Firefox)

 

[+Team Sieni]

Call me Alan (ar an anagram of it), but I keep a database of all the tag numbers, tracking numbers and details of (almost) all the TBs I log. It's useful for just this eventuality.

That's very laan of you. I do the same, but my database is a scrap of paper in my caching goodie bag. I had to do one repeat visit to a cache due to forgetting the code before I started doing this, so it's a useful precaution.

 

Edited to add ... but not much use to you in your present predicament I'm afraid.

Edited September 29, 2008 by Team Sieni

[+Simply Paul]

Can I just warn people against the use of anagrams? You never know who's watching...

[+The Sandpipers]

I just went to my own profile and clicked on the travel bugs found thingy and clicked on a random old TB - it's code was still there.

 

Thanks Skull Duggery it worked like a dream !

I was worried that I might have cleared the saved form details etc when I last cleared my cookies and what have you, but luckily they were still there... I had to keep going through the alphabet and checking each of the entries that came up but eventually when I got to the entries for the letter V, I found one that matched..brilliant idea. Thanks again

[+jerryo]

Depending on when the TB was first logged as retrieved or grabbed, going back to the logging page and clicking the curser into the trackable number may bring up the tracking number in the box... Helps if you can rember the first number/letter.

 

(Works in Firefox)

 

I apologise. I was entirely wrong.

[+Bear and Ragged]

Depending on when the TB was first logged as retrieved or grabbed, going back to the logging page and clicking the curser into the trackable number may bring up the tracking number in the box... Helps if you can rember the first number/letter.

 

(Works in Firefox)

 

I apologise. I was entirely wrong.

 

Depends on how your browser is set up, and when the TB was logged as retrieved.

Might not have worked. Then you wouldn't have been wrong.

[+Glyn Morris]

I just went to my own profile and clicked on the travel bugs found thingy and clicked on a random old TB - it's code was still there.

 

Thanks Skull Duggery it worked like a dream !

I was worried that I might have cleared the saved form details etc when I last cleared my cookies and what have you, but luckily they were still there... I had to keep going through the alphabet and checking each of the entries that came up but eventually when I got to the entries for the letter V, I found one that matched..brilliant idea. Thanks again

 

My absolute pleasure.

[+SidAndBob]

A tip for the future. Always take a digit photo of the tag when you pick it up (and check you can read it). I usually take another one of the TB with the cache when I leave it, so I can remember where I left it too.

TB details can be recorded in Cachemate too.