Deleting logs

[+jellis]

With all the issues with deleting logs and COs not telling why they are, I suggest there is a change so when a CO deletes a log a box opens up that requires the CO to put the reason why the log is being deleted so the other cacher doesn't get upset wondering why gets deleted when the CO doesn't send a message. It would be so much easier for both parties involved.

Edited July 29, 2013 by jellis

[+Cissy PSP]

With all the issues with deleting logs and COs not telling why they are, I suggest there is a change so when a CO deletes a log a box opens up that requires the CO to put the reason why the log is being deleted so the other cacher doesn't get upset wondering why gets deleted when the CO doesn't send a message. It would be so much easier for both parties involved.

 

Excellent idea! I like it, I like it a lot!

[+NanCycle]

With all the issues with deleting logs and COs not telling why they are, I suggest there is a change so when a CO deletes a log a box opens up that requires the CO to put the reason why the log is being deleted so the other cacher doesn't get upset wondering why gets deleted when the CO doesn't send a message. It would be so much easier for both parties involved.

 

This has been suggested before, but I agree that it is still a good idea.

[+GeoGrins]

With all the issues with deleting logs and COs not telling why they are, I suggest there is a change so when a CO deletes a log a box opens up that requires the CO to put the reason why the log is being deleted so the other cacher doesn't get upset wondering why gets deleted when the CO doesn't send a message. It would be so much easier for both parties involved.

 

+1! This would be incredibly helpful and kind! :-) Great idea jellis!

[+jellis]

With all the issues with deleting logs and COs not telling why they are, I suggest there is a change so when a CO deletes a log a box opens up that requires the CO to put the reason why the log is being deleted so the other cacher doesn't get upset wondering why gets deleted when the CO doesn't send a message. It would be so much easier for both parties involved.

 

This has been suggested before, but I agree that it is still a good idea.

It may have been me too. I remember suggesting it a long time ago but they never did anything. Now when I get a deletion notice I have no idea for what cache and I have to research which one and why.

I believe this suggestion would really relieve a lot of stress when someone not only has to delete a log but for the cacher receiving it.

[+Zop]

It may have been me too. I remember suggesting it a long time ago but they never did anything. Now when I get a deletion notice I have no idea for what cache and I have to research which one and why.

I believe this suggestion would really relieve a lot of stress when someone not only has to delete a log but for the cacher receiving it.

 

When you receive the log deletion notice, it includes a link to the deleted log. I just copy it and paste it back into a new log with the same date with a note to the CO as to why I am reposting it.

[+Zop]

With all the issues with deleting logs and COs not telling why they are, I suggest there is a change so when a CO deletes a log a box opens up that requires the CO to put the reason why the log is being deleted so the other cacher doesn't get upset wondering why gets deleted when the CO doesn't send a message. It would be so much easier for both parties involved.

 

I like this idea. C-MNM and I both had our logs deleted recently merely because we mentioned that we had to be careful of the syringes and a homeless encampment at GZ. Personally, I would want to know that kind of stuff before I started my search for a cache.

 

As a CO of several caches unless a log gives away the solution to a puzzle or the hide, I'll always send a message to the logger and ask for a change before I delete a log. Unless it's a blank one anyway.

[+jellis]

It may have been me too. I remember suggesting it a long time ago but they never did anything. Now when I get a deletion notice I have no idea for what cache and I have to research which one and why.

I believe this suggestion would really relieve a lot of stress when someone not only has to delete a log but for the cacher receiving it.

 

When you receive the log deletion notice, it includes a link to the deleted log. I just copy it and paste it back into a new log with the same date with a note to the CO as to why I am reposting it.

Sometimes I've gotten logs deleted from a long time ago and I don't always remember the cache. So I want to know why. My suggestion may cut out having to contact the CO and having to wait for a response.

[+The_Incredibles_]

Great idea. In fact, it's been asked for before, but they still haven't implemented it. Another no-brainer.

 

http://forums.Groundspeak.com/GC/index.php?showtopic=299737&st=0&p=5098769&hl=send%20email&fromsearch=1entry5098769

[team tisri]

Great idea. In fact, it's been asked for before, but they still haven't implemented it. Another no-brainer.

 

http://forums.Groundspeak.com/GC/index.php?showtopic=299737&st=0&p=5098769&hl=send%20email&fromsearch=1entry5098769

 

Ask for a souvenir when your log is deleted and they might do that one...

[+Chief301]

Good idea, but just because you get a text box that "must" be filled out, doesn't mean you'll get an explanation. After all, you "must" type something in the text box when logging a cache. So we get "TFTC", "Found It", or the even more annoying "."

 

LDBO = Log Deleted By Owner. See what I'm saying? You wouldn't really have to give a reason at all.

Edited July 29, 2013 by Chief301

[AZcachemeister]

It's pretty rare for me to delete a log.

When I feel something minor needs to be changed or the logger didn't post a photo or send verification (for my virtual), I usually send a message asking them to correct the situation and then delete the log if they fail to comply...so I wouldn't want or need to send a reason when deleting the log.

If someone posts a blatant spoiler or uses profanity, I'm going to make them ask me why I deleted the log.

[+Harry Dolphin]

I deleted a photo yesterday. I was asked why? (It gave too much information.) So, it is there for deleting photos, and should be there for deleting logs.

For people who log my webcam cache without the required webcam photo, I send an e-mail notifying them that the photo is required. Then I give them a week to correct their error. (So, they are aware of the problem.) But deleting the log does not allow a field to explain why.

[+The Rat]

I like this idea. C-MNM and I both had our logs deleted recently merely because we mentioned that we had to be careful of the syringes and a homeless encampment at GZ. Personally, I would want to know that kind of stuff before I started my search for a cache.

I agree completely that this kind of information is important to convey to others who might look for a cache. I've only had one log deleted -- and that was on a find -- because I said something similar, of a negative nature that I thought was important for the safety of future cachers. The CO did send me an explanation by email (after several days) basically saying caching should be fun and my log was a downer so he deleted my find, and told me to write something nice. I didn't think it it deserved something nice, so instead I put the cache on a bookmark list with a nasty title and re-logged my find pointing out that I have done so and that the owner can't delete the bookmark list. I also posted on local forums that I've done so. He left my log and could do nothing about the bookmark list. The log fell off the cache page quickly with future finders, but the bookmark list didn't. So you can fight fire with fire and make it a lot worse for the CO than if he'd left your log. I recommend it.

Edited July 30, 2013 by The Rat

[+Don_J]

I believe that Miss Jenn herself said that this would be coming in a future site update. I believe that that was about three years ago.

 

The idea was two fold. If your log gets deleted, you, as well as any reviewer or lackey that cares to look, gets an explanation as to why. If people are forced to write an explanation, they may not be so casual about deleting logs.

[cezanne]

I deleted a photo yesterday. I was asked why? (It gave too much information.) So, it is there for deleting photos, and should be there for deleting logs.

 

Yes, the field is there if one deletes a photo. Right now I would not recommend you or other cache owners to use the option to delete a photo, however. Delete the complete log and invite the logger to submit the text again.

 

The issue with deleted photos is that a message is sent out to all watchers (and all who have the cache on their bookmark lists) that allows them to view the photo after its deletion. If you delete the whole log quickly, only a few cachers might have had a look at the photo. The way Groundspeak implements some features is quite inconsistent and often new problems come up when they change something.

 

It is the wrong way to use reviewer notes for such situations as reviewer notes for published caches are viewable to the public.

I do not wish that they implement the same approach for deleting logs as they are using for deleting photos only. They first would need to correct the bug mentioned above.

 

With the current system deleting logs and explaining the reason by personal mail is the best approach in my opinion.

 

Cezanne

Edited July 30, 2013 by cezanne

[team tisri]

I believe that Miss Jenn herself said that this would be coming in a future site update. I believe that that was about three years ago.

 

The idea was two fold. If your log gets deleted, you, as well as any reviewer or lackey that cares to look, gets an explanation as to why. If people are forced to write an explanation, they may not be so casual about deleting logs.

 

This is a good point, even though someone could just write "." or "deleted" in an obligatory field to specify a reason for deletion if anyone did complain a reviewer/lackey could easily see that "." isn't a good reason to delete a log and reinstate it without even having to consider the merits or otherwise of the reason given.

[AZcachemeister]

 

Yes, the field is there if one deletes a photo. Right now I would not recommend you or other cache owners to use the option to delete a photo, however. Delete the complete log and invite the logger to submit the text again.

 

The issue with deleted photos is that a message is sent out to all watchers (and all who have the cache on their bookmark lists) that allows them to view the photo after its deletion. If you delete the whole log quickly, only a few cachers might have had a look at the photo. The way Groundspeak implements some features is quite inconsistent and often new problems come up when they change something.

 

 

Duly noted, thanks for the heads-up!

[jholly]

I deleted a photo yesterday. I was asked why? (It gave too much information.) So, it is there for deleting photos, and should be there for deleting logs.

 

Yes, the field is there if one deletes a photo. Right now I would not recommend you or other cache owners to use the option to delete a photo, however. Delete the complete log and invite the logger to submit the text again.

 

The issue with deleted photos is that a message is sent out to all watchers (and all who have the cache on their bookmark lists) that allows them to view the photo after its deletion. If you delete the whole log quickly, only a few cachers might have had a look at the photo. The way Groundspeak implements some features is quite inconsistent and often new problems come up when they change something.

 

It is the wrong way to use reviewer notes for such situations as reviewer notes for published caches are viewable to the public.

I do not wish that they implement the same approach for deleting logs as they are using for deleting photos only. They first would need to correct the bug mentioned above.

 

With the current system deleting logs and explaining the reason by personal mail is the best approach in my opinion.

 

Cezanne

Didn't that get fixed a while ago? I know Don_J brought it up frequently.

[cezanne]

Didn't that get fixed a while ago? I know Don_J brought it up frequently.

 

Could be. The instances I'm aware of date a while back.

Maybe I will test this with a friend on an archived cache.

 

 

Cezanne

[+AnnaMoritz]

Didn't that get fixed a while ago? I know Don_J brought it up frequently.

 

Now the link to the deleted picture isn't included in the Reviewer Note that is posted on the cache page if you delete a picture from a log, only the reason of deletion is included. Watchers still get an email about the Reviewer Note but without link to the picture this doesn't give too much information to them.

[+Don_J]

I deleted a photo yesterday. I was asked why? (It gave too much information.) So, it is there for deleting photos, and should be there for deleting logs.

 

Yes, the field is there if one deletes a photo. Right now I would not recommend you or other cache owners to use the option to delete a photo, however. Delete the complete log and invite the logger to submit the text again.

 

The issue with deleted photos is that a message is sent out to all watchers (and all who have the cache on their bookmark lists) that allows them to view the photo after its deletion. If you delete the whole log quickly, only a few cachers might have had a look at the photo. The way Groundspeak implements some features is quite inconsistent and often new problems come up when they change something.

 

It is the wrong way to use reviewer notes for such situations as reviewer notes for published caches are viewable to the public.

I do not wish that they implement the same approach for deleting logs as they are using for deleting photos only. They first would need to correct the bug mentioned above.

 

With the current system deleting logs and explaining the reason by personal mail is the best approach in my opinion.

 

Cezanne

 

I thought that they fixed that issue? I never had a chance to test it though. Maybe this afternoon.

[cezanne]

I thought that they fixed that issue? I never had a chance to test it though. Maybe this afternoon.

 

We tested it an hour ago and as AnnaMoritz wrote above it has indeed been fixed. Thanks for making me aware of this fix.

However, the provided reason for deleting the photo is still sent to everyone who watches the cache, something I would not appreciate in the case they used the same system for deleting logs. In my opinion, the provided reason should be viewable only to the logger and to Groundspeak. Otherwise, one needs to write a more explicit mail anyway. Sometimes I explain in detail to a logger why I consider his log as a massive spoiler. Of course this type of information is not directed to the public.

 

I'm unhappy with the way some information that should only be visible to the cache owner and Groundspeak is viewable to all cachers. A similar issue arises if the final coordinates of an already published cache are changed and the reviewer mentions the fact of a distance collision arose in a reviewer note which is visible to everyone.

 

Cezanne

[AZcachemeister]

I wouldn't want to broadcast the fact that I deleted a photo or log to the general population.

It is none of their business.

In fact, it is only between me and the cacher posting the log/photo.

 

Someone may have such a spoiler log or photo already downloaded to their system that they may be unaware was a spoiler until the deletion notice went through.

 

'Oh, look...a spoiler photo was deleted! Yes, I have that one here in my system.'

[+jukis&prusak]

We never had this problem before ... so don't really know what to do ... maybe anyone here can help us with some advice.

We recently found a cache (http://coord.info/GC4F58K) but we are unable to log it properly because as soon as we put our "Found it" log the owner deletes it without any explanation.

He has deleted our "Found it" log already 3 times.

We also have received some communication from him where he prohibits us from logging his cache.

Is there any way how we could log our find and our log couldn't get deleted?

[team tisri]

We never had this problem before ... so don't really know what to do ... maybe anyone here can help us with some advice.

We recently found a cache (http://coord.info/GC4F58K) but we are unable to log it properly because as soon as we put our "Found it" log the owner deletes it without any explanation.

He has deleted our "Found it" log already 3 times.

We also have received some communication from him where he prohibits us from logging his cache.

Is there any way how we could log our find and our log couldn't get deleted?

 

That's a traditional cache so if you found it and signed the log you get to claim a find.

 

If the owner keeps deleting your logs when you have actually found the cache I'd log Needs Archived on it, explain in the log that the owner has deleted your Found logs three times without explanation and so you can only assume there's a hidden agenda. They might delete the NA log but by it will automatically be sent to the reviewer. If that still doesn't work talk directly to Groundspeak.

 

ETA: The only time I ever had a log deleted was when I'd logged a find against an earthcache but forgotten to upload the picture. It was annoying that the owner didn't delete the log for nearly two years (by which time I couldn't find the required information and had to fish around in my photo archives for the picture) but it was still ultimately my fault for not uploading the picture. As it happens in that situation the CO accepted my description of when I found it and a more generic picture of the area in question.

Edited August 13, 2013 by team tisri

[+Don_J]

We never had this problem before ... so don't really know what to do ... maybe anyone here can help us with some advice.

We recently found a cache (http://coord.info/GC4F58K) but we are unable to log it properly because as soon as we put our "Found it" log the owner deletes it without any explanation.

He has deleted our "Found it" log already 3 times.

We also have received some communication from him where he prohibits us from logging his cache.

Is there any way how we could log our find and our log couldn't get deleted?

 

You have a found log on that cache dated Aug 8, 2013. If you are logging it again, the CO probably thinks that your cell phone is double logging and he is deleting the extras. This has been an issue in the last week.

[team tisri]

We never had this problem before ... so don't really know what to do ... maybe anyone here can help us with some advice.

We recently found a cache (http://coord.info/GC4F58K) but we are unable to log it properly because as soon as we put our "Found it" log the owner deletes it without any explanation.

He has deleted our "Found it" log already 3 times.

We also have received some communication from him where he prohibits us from logging his cache.

Is there any way how we could log our find and our log couldn't get deleted?

 

You have a found log on that cache dated Aug 8, 2013. If you are logging it again, the CO probably thinks that your cell phone is double logging and he is deleting the extras. This has been an issue in the last week.

 

In the light of the found log on 8 August it's also possible the CO thinks you're just creating multiple found it logs to get all the August souvenirs.

[+jukis&prusak]

You have a found log on that cache dated Aug 8, 2013. If you are logging it again, the CO probably thinks that your cell phone is double logging and he is deleting the extras. This has been an issue in the last week.

 

I'm pretty sure that that's not the case ...

I logged my find only once only after it was deleted I re-logged it for the second, third and just recently for the fourth time. For now the CO has stopped deleting my logs after I sent him an e-mail asking for a valid explanation.

I also posted "Needs Archived" log explaining all the things that are wrong with this cache and also mentioned that our "Found it" logs have been deleted four times, but naturally our NA log was also deleted.

I suspect it is some sort of personal vendetta and I really don't know what is the best way to handle this ... I never had any problems like this before.

[+Harry Dolphin]

I've had a few logs deleted. "Parking lot of a porn store with people having sex in the parking lot is not family friendly." (Or some such log.)

Seek help at contact@geocaching.com Or is it support@geocaching.com? They will ask you to try to work it out with the CO. In this case, I relogged as "Found it." And the problem was resolved. If you cannot work it out with the CO, and you have signed the log, they can, and will, reinstate your log, and lock it so that it cannot be deleted. Had that happen with a friend's log. CO took offense with the logger (long story). It could not be worked out with the CO, so Groundspeak reinstated, and locked the log. Of course,, then the CO archived the cache. (Control issues...) That sounds like your best approach. http://support.Groundspeak.com/index.php?pg=request

[+Don_J]

You have a found log on that cache dated Aug 8, 2013. If you are logging it again, the CO probably thinks that your cell phone is double logging and he is deleting the extras. This has been an issue in the last week.

 

I'm pretty sure that that's not the case ...

I logged my find only once only after it was deleted I re-logged it for the second, third and just recently for the fourth time. For now the CO has stopped deleting my logs after I sent him an e-mail asking for a valid explanation.

I also posted "Needs Archived" log explaining all the things that are wrong with this cache and also mentioned that our "Found it" logs have been deleted four times, but naturally our NA log was also deleted.

I suspect it is some sort of personal vendetta and I really don't know what is the best way to handle this ... I never had any problems like this before.

 

Well, it looks like he may be letting your log stand. The best way to handle it going forward is to take the high road and not bother looking for any more of his caches. It's probably not worth the trouble.

[+jellis]

After the Block Party, as a group of cachers, we went to explore the lower state and the Columbia Gorge. We did a bunch of Earthcaches, Trads, Multis, Puzzles and Virtuals. One Virtual was recently archived while we were still logging our caches. With 4 separate accounts two of us the logs were fine and two the logs were deleted with no reason (yet) on why. According to the archive note, he archived the cache because of too many armchair cachers not sending proof. One of us sent the answers for the group. All our logs named the cachers in our group. I sent a message to the CO to explain we were all together. So we are still waiting on why part of our group logs were deleted.

Another reason having the CO having to explain why they deleted a log at the time they sent the deletion notice instead of waiting for a message they may or may not send.