NickPick Posted January 18, 2008 Posted January 18, 2008 I received my Friday morning email from Groundspeak, and the nearest newly published cache is only 0.6 miles from my co-ordinates. I click to have a look at The Cache Page and get "Sorry, you cannot view this cache listing until it has been published. " What's going on here then? I would have thought it wouldn't send the list of caches if they haven't been published yet. Quote
+Jonovich Posted January 18, 2008 Posted January 18, 2008 I received my Friday morning email from Groundspeak, and the nearest newly published cache is only 0.6 miles from my co-ordinates. I click to have a look at The Cache Page and get "Sorry, you cannot view this cache listing until it has been published. " What's going on here then? I would have thought it wouldn't send the list of caches if they haven't been published yet. Sounds like it has been un-published... We had one like that near us. Was published, we downloaded details and headed out to find it. After a successful find we got home to log it and found it had been un-published due to permission issues with it's placement. J Quote
markandlynn Posted January 18, 2008 Posted January 18, 2008 Ive got a few of those in my database would love to know the history behind some of them as archiving is usually sufficient. What do you have to do wrong to get a cache unpublished ?? Quote
+Delta68 Posted January 18, 2008 Posted January 18, 2008 We set a series of four caches in a circular walk once and the first three were published but then unpublished when there was a problem with the fourth and it was obvious it was a series. Quote
+Jonovich Posted January 18, 2008 Posted January 18, 2008 What do you have to do wrong to get a cache unpublished ?? Put it on Forestry commission land without permission! Personally I would of thought it better for the cache placing permission to be confirmed PRIOR to it being published, rather than after and then un-publishing it if permission was not given. Saves a lot of confusion and indeed cache hunts that can then not be logged. J Quote
markandlynn Posted January 18, 2008 Posted January 18, 2008 What do you have to do wrong to get a cache unpublished ?? Put it on Forestry commission land without permission! J Those usually get archived rather than published and then unpublished. In fact our very first cache placement was on FC land without permision it got archived after one find it still shows in our profile. Quote
+Jonovich Posted January 18, 2008 Posted January 18, 2008 What do you have to do wrong to get a cache unpublished ?? Put it on Forestry commission land without permission! J Those usually get archived rather than published and then unpublished. Here's the link to the cache in question (GC16YRB), but of course, it's unpublished, so you can't see much.... I do have my original GPX download of it still though [] J Quote
markandlynn Posted January 18, 2008 Posted January 18, 2008 What do you have to do wrong to get a cache unpublished ?? Put it on Forestry commission land without permission! J Those usually get archived rather than published and then unpublished. Here's the link to the cache in question (GC16YRB), but of course, it's unpublished, so you can't see much.... I do have my original GPX download of it still though [] J Aha now that was quick off the mark ive got some gpx files like that in my db there was an interesting one in scotland where it was unpublished and the co ords changed. Quote
+jerryo Posted January 18, 2008 Posted January 18, 2008 <snippety snip>Personally I would of thought it better for the cache placing permission to be confirmed PRIOR to it being published, It already has/should have been: according to the submission guidelines, every cache must have that permission, saying: “By submitting a cache listing, you assure us that you have adequate permission to hide your cache in the selected location". Quote
+keehotee Posted January 18, 2008 Posted January 18, 2008 Perhaps somebody forgot to untick the "this cache is ready to publish" box while they were working on the page......and a friendly reviewer kindly unpublished it for them so that they could finish? Quote
+dino-irl Posted January 18, 2008 Posted January 18, 2008 I'd guess a slip of the mouse during the review process but as you say ask the owner or reviewer for a definitive answer Quote
Deceangi Posted January 18, 2008 Posted January 18, 2008 Retraction is an unusual action for a Reviewer to take, and is done to remove the details from public view for a several reasons. i: There are extreme issues with it, where the standard action of Archiving is not sufficient. ii: Immediately after publishing the Reviewer spots a issue, that was missed before hitting the publish button and which is sufficient to prevent publication. Retraction allows the Reviewer to request the owner to rectify the issue so that it can properly be published. iii: And the one I'm most guilty of , the owner has requested a delayed publication but the Reviewer trying to provide a fast service missed the Reviewer note requesting it. Hence the retraction, which is followed by publication on the requested date Sorry I'm not telling you what reason this one was retracted , you'll just have to wait and see if its re published in the future Quote
+JeremyR Posted January 18, 2008 Posted January 18, 2008 Ok just a quicky related question, I got an Instanotify the other day while I was sat at my computer. It was unpublished by the time I clicked the link but in the past, I've had details and then they've been retracted. Thing is, all my Notify subscriptions have the Retract listing box ticked so shouldn't I have got another notification to tell me that if I have the details and am about to head out on an FTF hunt, that I shouldn't? Quote
NickPick Posted January 20, 2008 Author Posted January 20, 2008 Here's the link to the cache in question (GC16YRB), but of course, it's unpublished, so you can't see much.... I do have my original GPX download of it still though [] J That must be a different unpublished cache. The one I linked to has been republished, and found 3 times already! Quote
fraggle69 Posted January 20, 2008 Posted January 20, 2008 I had a cache that wasn't meant to be published get published, the reviewer quickly retracted it but the notification email had already gone out. You see I'd asked for the caches to go live at my event, so wanted to have them pre-reviewed. Aii Quote
adrianjohn Posted January 20, 2008 Posted January 20, 2008 So the answer is simple, the caches were intended to be released in time for the nearby cache bash. Nothing mysterious or otherwise, but just a matter of the cache page being visible too soon. Thanks Eckington for your diligence in publishing them in good time, but be careful in future Oh by the way, sorry you were not there when I was, you missed the cake! Quote
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.