Page 1 of 1

Duplicate Logs

Posted: 31 January 21 4:17 pm
by traineediplomat
Hi tech faeries. I've tried searching for an answer but without much success.

I've got something like 30+ duplicate logs showing up in GCA. They are only duplicated on the llogs/caches here not on GC (and I've only found GC caches).

How do I go through and clear the duplicates?

Re: Duplicate Logs

Posted: 01 February 21 9:25 am
by caughtatwork
Example please.

Re: Duplicate Logs

Posted: 01 February 21 9:32 pm
by traineediplomat
For example

Denman Rocks - GC86J25 - https://geocaching.com.au/cache/gc86j25 - has two entries for me on 07 October 2019
As does Denman Prospect Table Tennis - GC858CY - https://geocaching.com.au/cache/gc858cy

Random older ones - https://geocaching.com.au/cache/gc1zfv3 - has a double log from 15 December 2013!

Re: Duplicate Logs

Posted: 02 February 21 8:57 am
by caughtatwork
Hmmm. These are all sequential and were manually imported.
https://geocaching.com.au/logs/cacher/t ... duplicates

I'll have a look and remove the duplicates for all of these later today.

Re: Duplicate Logs

Posted: 02 February 21 10:16 pm
by traineediplomat
Huh weird!

Re: Duplicate Logs

Posted: 03 February 22 9:40 am
by sirius Tas
I have a duplicate log on
https://geocaching.com.au/cache/gc4zzp8#top

which keeps re-appearing having been deleted before.

It was found on 11/4/2017

Much appreciated if one of the logs can be removed permanently.....

Many thanks

Re: Duplicate Logs

Posted: 27 April 22 3:50 pm
by sirius Tas
Once again I have a duplicate log on
https://geocaching.com.au/cache/gc70d4y#top

Found on 11/4/2017

Could the 2nd log(briefest one) be deleted please.

These duplicates seem to keep occurring despite only a single log on GC.

Many thanks

Re: Duplicate Logs

Posted: 28 April 22 9:37 am
by caughtatwork
They only occur because there is more than one log when the file is imported. As they're different descriptions they're not a duplicate, they are two separate logs. I'd guess you made a log, then possibly deleted it and relogged it. Someone still had that log so it appears to be a legitimate log when it's imported. I'll remove the briefest log.