Re: Report GCA Site issues here
Posted: 27 November 12 11:00 am
Worked fine for me.mtrax wrote:Only a small issue Google map link doesn't work when there is a brackets in the cache name
Eg http://geocaching.com.au/cache/gcad
Free and Open Geocaching
https://forum.geocaching.com.au/
Worked fine for me.mtrax wrote:Only a small issue Google map link doesn't work when there is a brackets in the cache name
Eg http://geocaching.com.au/cache/gcad
not if you use the "Native G map" linkWanderingAus wrote:Worked fine for me.mtrax wrote:Only a small issue Google map link doesn't work when there is a brackets in the cache name
Eg http://geocaching.com.au/cache/gcad
When I used that I got to with the followingmtrax wrote:not if you use the "Native G map" linkWanderingAus wrote:Worked fine for me.mtrax wrote:Only a small issue Google map link doesn't work when there is a brackets in the cache name
Eg http://geocaching.com.au/cache/gcad
yes the "(New Location) should be changed to just New locationWanderingAus wrote:When I used that I got to with the followingmtrax wrote:not if you use the "Native G map" linkWanderingAus wrote:Worked fine for me.mtrax wrote:Only a small issue Google map link doesn't work when there is a brackets in the cache name
Eg http://geocaching.com.au/cache/gcad
-38.278117 145.101917 (Devil Bend (NEW LOCATION))
and a list of "Did you mean".
When I deleted (Devil Bend (NEW LOCATION)) and left only -38.278117 145.101917 and hit [Enter] I found a perfect map centred on 159 Graydens Rd. No problem.
Your log has been fixed.Chwiliwr wrote:The problem of the original coordinates not there happened on GA5103 so my move doesn't appear on the bingo game as it doesn't have any distance.
In this case the original coordinates were S32° 09.221 E115° 51.603
Can this be fixed please.
BTW I did query for the moveables last night and looking at it you could have more than 70 caches that may do the same as there are no coordinates on the publish logs for them.
eg GA4887 - move doesn't show a distance for Bronnie_1990
There is nothing in the system that I can see that would do that.Toriaz wrote:When I wrote the cache pages for my 4 bingo moveables, I put my home coords in as the cache coordinates. Then as I hid each of them, I edited the notes & put in the actual coords. They were all correct this morning when they all published.
Three of them now have logs - 2 x found it & 1 x DNF. And all 3 of them are showing my home coords as their location.
What has happened? Why have the coords reverted to the pre-edited ones just because they were logged?
Hopefully no one will turn up at my house looking for caches that aren't here.
I had a similar problem... when we set up the cache pages we just put in random (close to home) *co-ords and then altered them when we actually hid them. They published with the right *co-ords but when they were found they reverted to the pretend *co-ords and so when they were moved the person that moved them didnt get credit for the move as it was less than 1 km from the pretend *co-ords. He contacted me and I altered the *co-ords so all was good. I then checked our others and 3 of them had done the same. It was ones where we had put the future publish logs in before changing to the real co-ords. The others that we hid and then changed before doing the Future Publish log were ok ...Toriaz wrote:When I wrote the cache pages for my 4 bingo moveables, I put my home coords in as the cache coordinates. Then as I hid each of them, I edited the notes & put in the actual coords. They were all correct this morning when they all published.
Three of them now have logs - 2 x found it & 1 x DNF. And all 3 of them are showing my home coords as their location.
What has happened? Why have the coords reverted to the pre-edited ones just because they were logged?
Hopefully no one will turn up at my house looking for caches that aren't here.
Cool, thanks for confirming what I suspected. We'll *try* to remember for next year lol!!!caughtatwork wrote:You have nailed it.
Once the cache is published, changes to the cache co-ords are done via log entries, not via editing the cache page. That's how the cache gets updates as moveable caches move. From the logs.
Next time (and I'll try and remember to highlight this) ...
DO NOT publish your cache UNTIL the FINAL co-ordinates are entered.
We have a number of caches with no starting co-ords at all as they were published BEFORE the cache had been given co-ords.
Updating the co-ords does NOT reset them in the publish log, so the first "move" has no distance as there are no co-ords.
Thanks for your investigations.