Jump to content

Newly Published Cache Not Published


NickPick

Recommended Posts

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.

Link to comment

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

Link to comment

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

Link to comment

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.

Link to comment

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 [:lol:]

 

J

Link to comment

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 [:lol:]

 

J

 

Aha B) 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.

Link to comment

<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". :lol:

Link to comment

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 :lol: , 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 B)B)

 

Sorry I'm not telling you what reason this one was retracted :lol: , you'll just have to wait and see if its re published in the future :huh:

Link to comment

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?

Link to comment

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!

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...