Report GCA Site issues here [closed]

[caughtatwork]

Sorry, I didn't know that about not editing coordinates after posting a published log. But at least I gave mine starting coords, and the first finders got the credits for their bingo cards.

My remaining moveable will be the same, but again, it at least had some starting coords & the first to find moved it a long way, so he will still get credit for the move.

Don't take any blame. I don't think it's ever come up or been mentioned before. We've all learnt something.

[Richary]

When I created mine I left the coords as default 0's so I could get the GA number to put in the log. Once I knew where I put them I filled in more data, and I think I updated the coords in the listing. Then I published them but also with the real coords in the Publish log. That may have been a duplication of what was needed but it seemed to work OK.

Question for future reference - would putting the correct coords in the Publish log then stay as the starting point for the next move? So I wouldn't have needed to update the coords in the listing prior to publishing?

[Chwiliwr]

When I created mine I left the coords as default 0's so I could get the GA number to put in the log. Once I knew where I put them I filled in more data, and I think I updated the coords in the listing. Then I published them but also with the real coords in the Publish log. That may have been a duplication of what was needed but it seemed to work OK.

Question for future reference - would putting the correct coords in the Publish log then stay as the starting point for the next move? So I wouldn't have needed to update the coords in the listing prior to publishing?

If you put different coordinates in a publish log than those in the listing itself they are changed to match the listing. Happened on one of my moveable caches when I forgot to edit them first before publishing it. It ended up staying in the temporary place that I had put when it was in draft mode.

[Chwiliwr]

As I got a GPX for all the moveable caches for Australia not long after they were initially published I can see that there were a number that had no coordinates in the publish listing. Some of them have already been corrected so I compared the list to the current system and the following caches will probably have to be corrected to show a distance for the first move.

Hope this helps.

GA # - Original coordinates
-----------------------------------------------
4685 - will have to ask mover or owner as it had already moved before I got the GPX.
5077 - S33° 58.421 E137° 44.884
4869 - S33° 49.215 E151° 05.262
4883 - S33° 58.903 E150° 59.861
5069 - S37° 48.343 E144° 48.566
5029 - S37° 55.523 E144° 59.209
4879 - S33° 58.903 E150° 59.861
4880 - S33° 58.903 E150° 59.861 <<=== This one is currently shown as WA without any moves visible so may need more than fixing of the publish log.
4881 - S33° 58.903 E150° 59.861
4882 - S33° 58.903 E150° 59.861
4883 - S33° 58.903 E150° 59.861
5151 - S33° 58.903 E150° 59.861
5152 - S36° 51.093 E144° 13.689
4695 - S36° 50.973 E144° 13.749
4704 - S36° 47.253 E144° 13.823
4703 - S36° 47.268 E144° 14.424

[caughtatwork]

As I got a GPX for all the moveable caches for Australia not long after they were initially published I can see that there were a number that had no coordinates in the publish listing. Some of them have already been corrected so I compared the list to the current system and the following caches will probably have to be corrected to show a distance for the first move.

Hope this helps.

GA # - Original coordinates
-----------------------------------------------
4685 - will have to ask mover or owner as it had already moved before I got the GPX.
5077 - S33° 58.421 E137° 44.884
4869 - S33° 49.215 E151° 05.262
4883 - S33° 58.903 E150° 59.861
5069 - S37° 48.343 E144° 48.566
5029 - S37° 55.523 E144° 59.209
4879 - S33° 58.903 E150° 59.861
4880 - S33° 58.903 E150° 59.861 <<=== This one is currently shown as WA without any moves visible so may need more than fixing of the publish log.
4881 - S33° 58.903 E150° 59.861
4882 - S33° 58.903 E150° 59.861
4883 - S33° 58.903 E150° 59.861
5151 - S33° 58.903 E150° 59.861
5152 - S36° 51.093 E144° 13.689
4695 - S36° 50.973 E144° 13.749
4704 - S36° 47.253 E144° 13.823
4703 - S36° 47.268 E144° 14.424

Thanks for that. They've been updated.

[Chwiliwr]

I did some recently published bingo caches and noticed they didn't get to my card so found they got the publish coordinates problem. In this case I believe that they were published as traditional caches and then changed to a moveable after the publish log.

Can they have the coordinates put in the publish log please. They were all only a few metres apart from each other so can have the coordinates of the one moveable that wasn't affected as I don't have the exact original coordinates for them now.

GA5323, GA5324, GA5332 & GA5331 to original coordinates of S32° 4.167' E116° 0.117'

[caughtatwork]

I did some recently published bingo caches and noticed they didn't get to my card so found they got the publish coordinates problem. In this case I believe that they were published as traditional caches and then changed to a moveable after the publish log.

Can they have the coordinates put in the publish log please. They were all only a few metres apart from each other so can have the coordinates of the one moveable that wasn't affected as I don't have the exact original coordinates for them now.

GA5323, GA5324, GA5332 & GA5331 to original coordinates of S32° 4.167' E116° 0.117'

Self service.
Go to the publish log for each cache.
Click on the icon that looks like a page (note) for each publish log.
Add the co-ords to the log.
Save.
Ta da

[Chwiliwr]

I did some recently published bingo caches and noticed they didn't get to my card so found they got the publish coordinates problem. In this case I believe that they were published as traditional caches and then changed to a moveable after the publish log.

Can they have the coordinates put in the publish log please. They were all only a few metres apart from each other so can have the coordinates of the one moveable that wasn't affected as I don't have the exact original coordinates for them now.

GA5323, GA5324, GA5332 & GA5331 to original coordinates of S32° 4.167' E116° 0.117'

Self service.
Go to the publish log for each cache.
Click on the icon that looks like a page (note) for each publish log.
Add the co-ords to the log.
Save.
Ta da

I'm not the owner of the caches and do not see the note icon when I just checked.

[caughtatwork]

I did some recently published bingo caches and noticed they didn't get to my card so found they got the publish coordinates problem. In this case I believe that they were published as traditional caches and then changed to a moveable after the publish log.

Can they have the coordinates put in the publish log please. They were all only a few metres apart from each other so can have the coordinates of the one moveable that wasn't affected as I don't have the exact original coordinates for them now.

GA5323, GA5324, GA5332 & GA5331 to original coordinates of S32° 4.167' E116° 0.117'

Self service.
Go to the publish log for each cache.
Click on the icon that looks like a page (note) for each publish log.
Add the co-ords to the log.
Save.
Ta da

I'm not the owner of the caches and do not see the note icon when I just checked.

Sorry, I read that you owned them.
OK, I'll fix them up.

[Yurt]

The forum stars won't update for me now. Stuck at 2350.
Not crisis stuff but I just noticed it not change when I clicked the update function.

[pwags]

The forum stars won't update for me now. Stuck at 2350.
Not crisis stuff but I just noticed it not change when I clicked the update function.

The wiki says that your next increment for an update is 2,500 finds, Yurt.

[spatialriq]

I've had this problem before, but it appears my publish notification is not working again. There were a couple of bingo caches published yesterday and another 4 today well within my radius but no emails

[caughtatwork]

I've had this problem before, but it appears my publish notification is not working again. There were a couple of bingo caches published yesterday and another 4 today well within my radius but no emails

http://forum.geocaching.com.au/viewtopi ... =2&t=17747
Yes. It looks like the same problem. I recommend the same solution. I really don't know why this is happening. It seems to be only your account. I hate these sort of bugs.

[Yurt]

The forum stars won't update for me now. Stuck at 2350.
Not crisis stuff but I just noticed it not change when I clicked the update function.

The wiki says that your next increment for an update is 2,500 finds, Yurt.

Hmm, that's odd, why 2350 then? 2250 I'd understand.

[caughtatwork]

The stars were built rather haphazardly in the early days of the site. When we automated (make stars update self service), we never "filled in the gaps". It's kind of like a surprise now (not necessarily a good surprise) to find out when your next stars update will occur. The wiki does tell all.