Jump to content

Geocaching.com site update October 6th 2011

OpinioNate

By OpinioNate,
in Geocaching HQ communications

Followers 8

Recommended Posts

OpinioNate

OpinioNate

Posted
Posted

Read the last update's Release Notes

 

Release Notes:

 

• Uploading an invalid .KML file to user routes no longer throws an exception

• Added missing navigation to the /login/default.aspx page

• If a user is on a mobile device viewing a cache page the logs now display a button to load more

• Fixed display error in "Finds per Month" statistics so the x-axis lines up properly

• Now properly resizing avatars for display on cache pages; quality and page load performance increased

• Fixed link in the main gallery (/seek/gallery.aspx) to correctly point to the "recent log images"

• Added Italian translation to the Intro to Geocaching brochure list

• Added gccake.cz to Geocoin Manufacturers/Resellers list

• Updated Geocaching brochures in several languages on geocaching.com/tools/

• Fixed inability to remove a friend in the friends tools

• Changed Challenges terminology "Flag" to "Needs Archived" for more clarity among non-English speakers

• Added "South Sudan" to the country dropdowns

• Archived Challenges may now be viewed and completed, but not accepted. Comments are also available

• Added coord.info links to Trackable pages

• Added a new setting to account settings that turns off avatar display on cache pages

• Added new Czech translation of Intro to Geocaching presentation at geocaching.com/tools/intro.aspx

• New GC Live partner Certitude has launched!

• Added more information to GC Live authorization email including name, producer, description and URL

• Created DiveCaching page with information and links, added DiveCaching to the list of partners on Groundspeak.com

• Added a larger and more useful map to Challenges

• Updated ratings display for Challenges

• Localized Basic and Premium registration pages so they can be translated in other languages

• Added ability to quickly log Trackables with coord.info/t/CODE URL

• Localized cache placement guidelines, translations will follow

 

KD0cp.png Geocaching Live API Beta

 

The beta launch of the Geocaching Live API continues! This time we're pleased to announce a web interface for puzzle cache owners.

 

6wPEg.png Certitude

 

Certitude is a web interface used to validate solutions for geocaching puzzles. Features include the ability to see the list of solvers of a puzzle, be notified of solved puzzles by RSS feed, create solutions as coordinates or keywords with a private hint only solvers will see, update the cache page note with the final coordinates and hint, and download solutions in several file formats.

 

 

Many thanks to all geocachers who have provided feedback on User Voice. Happy Geocaching!

Link to comment
Dr.MORO

+Dr.MORO

Posted
Posted

Domo!!!

 

 

• Now properly resizing avatars for display on cache pages; quality and page load performance increased

 

 

O-K-, can't wait to see how 'fast' it has become scrolling down to the FTF log... <_<

 

 

• Added a new setting to account settings that turns off avatar display on cache pages

 

 

Finally, GS did 'give in'! :anibad:

 

NOW, still NO "Show ALL Logs" feature coming back??? Come on... :unsure:

 

Anyways, seems like one step forward.

Thanks, GS!

Link to comment
Rhialto

Rhialto

Posted
Posted
6wPEg.png Certitude

Just visited the page and... well... it's pretty ugly if you ask me... have nothing to do with the presention of geocaching.com and you worked so hard lately to improve on this. Oh well.

 

Have you tried to get in touch with any websites already offering the service?

 

I only have one puzzle cache that require validation and I choose http://geocheck.org/ for it.

Link to comment
OpinioNate

OpinioNate

Posted
  • Author
Posted

And what about this one, scheduled for today's update? I don't see anything above about fixed PQs...

 

This actually received a partial fix. Google was caching the data and we put a stop to it, however there is still a slight delay in updating the map results (which can be fixed by a refresh). The full fix will be in the next release.

Link to comment
Dr.MORO

+Dr.MORO

Posted
Posted

Domo!!!

NOW, still NO "Show ALL Logs" feature coming back??? Come on... :unsure:

I guess you didn't see where they said that it wasn't gonna happen. They *may* be able to come up with a Search All Logs feature, but no promises.

 

Domo again!!!

 

Yep, I did see this being shot-down *Twice* by Moun10bike in the feedback site.

STILL, I want it back!!!

So, why not continue asking for it?

 

Show All Logs! Show All Logs! Show All Logs!

 

PLEASE?!

Link to comment
OpinioNate

OpinioNate

Posted
  • Author
Posted

Is the promised "public" API ever gonna be "public"? Or is it just gonna be a few applications here and there and that's it?

 

Our intention is to eventually make the API fully public, but there are many steps between here and there. We have accepted around 150 requests for access at this point, so although a "closed Beta" we are not putting up too many barriers to entry.

Link to comment
dfx

+dfx

Posted
Posted (edited)

• If a user is on a mobile device viewing a cache page the logs now display a button to load more

 

Got a chance to test this now and it's not what I'm seeing. It behaves the same way on my Android as on my desktop, with the exception of the "loading logs" spinny thing not being there. No button in sight. Not that I'm complaining, I think it's good as it is now, but just saying.

Edited by dfx
Link to comment
OpinioNate

OpinioNate

Posted
  • Author
Posted

Changed Challenges terminology "Flag" to "Needs Archived" for more clarity among non-English speakers.

 

I'm not seeing this. I have done a Ctrl/F5 refresh and still only see Flag.

 

Thanks. It was changed in one location (and then subsequently changed again to "take action"). Looks like the comment link was not, though. We'll get that fixed.

Link to comment
Raine

+Raine

Posted
Posted

• If a user is on a mobile device viewing a cache page the logs now display a button to load more

 

Got a chance to test this now and it's not what I'm seeing. It behaves the same way on my Android as on my desktop, with the exception of the "loading logs" spinny thing not being there. No button in sight. Not that I'm complaining, I think it's good as it is now, but just saying.

 

Can you try this again?

Link to comment
dfx

+dfx

Posted
Posted (edited)

• If a user is on a mobile device viewing a cache page the logs now display a button to load more

 

Got a chance to test this now and it's not what I'm seeing. It behaves the same way on my Android as on my desktop, with the exception of the "loading logs" spinny thing not being there. No button in sight. Not that I'm complaining, I think it's good as it is now, but just saying.

 

I guess that second update fixed that. Logs are now loaded on demand (and also ahead of time, which is new) on the desktop, and I get the button on the phone.

 

Edit: posted at the same time :P

Edited by dfx
Link to comment
t4e

+t4e

Posted
Posted (edited)

logs are loading fast now, so "page down" can be used effectively :D

 

i like the avatars next to the log, now if only there will be a prettier image, maybe Signal, for those that don't have one, in place of that grey expressionless face lol

Edited by t4e
Link to comment
knowschad

knowschad

Posted
Posted

logs are loading fast now, so "page down" can be used effectively :D

 

i like the avatars next to the log, now if only there will be a prettier image, maybe Signal, for those that don't have one, in place of that grey expressionless face lol

 

I agree... well done on fixing the speed that the logs load! It will still be a pain on some caches, but this is MUCH more useable!

Link to comment
Nezgar & Vana

+Nezgar & Vana

Posted
Posted

• Added ability to quickly log Trackables with coord.info/t/CODE URL

 

Can an example be provided for the correct syntax of this URL format? I have tried coord.info/t/tbxxxx and also using the actual trackable code after the /t/, not the TB#, and I just get a Server Error - 404 - File or directory not found.

 

This sounds like a great feature if it eliminates the need to double-enter the tracking #'s, once to search, once to log.

Link to comment
FrogMastr

+FrogMastr

Posted
Posted

• Added ability to quickly log Trackables with coord.info/t/CODE URL

 

Can an example be provided for the correct syntax of this URL format? I have tried coord.info/t/tbxxxx and also using the actual trackable code after the /t/, not the TB#, and I just get a Server Error - 404 - File or directory not found.

 

This sounds like a great feature if it eliminates the need to double-enter the tracking #'s, once to search, once to log.

 

Thanks for tha feature... now for the next update would be cool if teh "trackable" number also was working...

so we could use it on the field (at that moment we do not know teh TBxxxx number. So we could se if there is any specific instructions to decide if we pickup or not the TB ;)

Link to comment
robnzh

+robnzh

Posted
Posted

I don't see any mention in the list of the bug in notification emails for trackables where it is picking up the log entry number and changing it from a T to a G in the cache link instead of showing the correct cache number: example notification for log coord.info/TL260XZK shows the cache as coord.info/GL260XZK (should be GC19M64.)

This has been happening for some time, was reported in the appropriate forum, and the example I am quoting is very recent but pre-latest update. I can't test whether it has been fixed until I get the next notification so could you tell us please and if it hasn't, give it priority for the next update?

Link to comment
LightHouseSeekers

+LightHouseSeekers

Posted
Posted

logs are loading fast now, so "page down" can be used effectively :D

 

i like the avatars next to the log, now if only there will be a prettier image, maybe Signal, for those that don't have one, in place of that grey expressionless face lol

 

I agree... well done on fixing the speed that the logs load! It will still be a pain on some caches, but this is MUCH more useable!

So it seems to be faster, but is there a shortcut to get to the very bottom (1st log) of a cache page?

Link to comment
knowschad

knowschad

Posted
Posted

logs are loading fast now, so "page down" can be used effectively :D

 

i like the avatars next to the log, now if only there will be a prettier image, maybe Signal, for those that don't have one, in place of that grey expressionless face lol

 

I agree... well done on fixing the speed that the logs load! It will still be a pain on some caches, but this is MUCH more useable!

So it seems to be faster, but is there a shortcut to get to the very bottom (1st log) of a cache page?

 

No, I don't think there is. That's why I said that it will still be a pain on some [very popular] caches.

Link to comment
lemmykc

+lemmykc

Posted
Posted

I went to try out the alerting of your cache being too close to another one and it was terrible. I put in the exact coords of one of my caches and it didn't do anything! Do we have to wait for a few more hours until this update is complete?

Link to comment
t4e

+t4e

Posted
Posted

I went to try out the alerting of your cache being too close to another one and it was terrible. I put in the exact coords of one of my caches and it didn't do anything! Do we have to wait for a few more hours until this update is complete?

 

who told you its been implemented with this update, the list in the first post definitely doesn't have it

Link to comment
The Blorenges

+The Blorenges

Posted
Posted

logs are loading fast now, so "page down" can be used effectively :D

 

i like the avatars next to the log, now if only there will be a prettier image, maybe Signal, for those that don't have one, in place of that grey expressionless face lol

 

I agree... well done on fixing the speed that the logs load! It will still be a pain on some caches, but this is MUCH more useable!

So it seems to be faster, but is there a shortcut to get to the very bottom (1st log) of a cache page?

 

No, I don't think there is. That's why I said that it will still be a pain on some [very popular] caches.

 

Just click on the 'View Logbook' link, then click the highest numbered page. That seems pretty quick to me :)

 

MrsB

Link to comment
Frank Broughton

+Frank Broughton

Posted
Posted (edited)

logs are loading fast now, so "page down" can be used effectively :D

 

i like the avatars next to the log, now if only there will be a prettier image, maybe Signal, for those that don't have one, in place of that grey expressionless face lol

 

I agree... well done on fixing the speed that the logs load! It will still be a pain on some caches, but this is MUCH more useable!

So it seems to be faster, but is there a shortcut to get to the very bottom (1st log) of a cache page?

 

No, I don't think there is. That's why I said that it will still be a pain on some [very popular] caches.

 

Just click on the 'View Logbook' link, then click the highest numbered page. That seems pretty quick to me :)

 

MrsB

 

Me too...

 

Dev team - thanks for speeding up the loading of logs - nice update!

Edited by Frank Broughton
Link to comment
Gushoneybun

+Gushoneybun

Posted
Posted

Changed Challenges terminology "Flag" to "Needs Archived" for more clarity among non-English speakers.

 

I'm not seeing this. I have done a Ctrl/F5 refresh and still only see Flag.

 

Thanks. It was changed in one location (and then subsequently changed again to "take action"). Looks like the comment link was not, though. We'll get that fixed.

 

Needs Archived, is pretty poor English, is it acceptable in American? Surely it should say Needs Archiving?

 

Just my view, all elses seems to be fine, keep up the good work.

Link to comment
dfx

+dfx

Posted
Posted (edited)
Needs Archived, is pretty poor English, is it acceptable in American? Surely it should say Needs Archiving?

 

Or "needs to be archived", or "needs archival", or "should be archived" - yeah, I thought the same thing :ph34r:

Edited by dfx
Link to comment
lemmykc

+lemmykc

Posted
Posted

I went to try out the alerting of your cache being too close to another one and it was terrible. I put in the exact coords of one of my caches and it didn't do anything! Do we have to wait for a few more hours until this update is complete?

 

who told you its been implemented with this update, the list in the first post definitely doesn't have it

 

http://feedback.geocaching.com/forums/75775-geocaching-com/suggestions/1403237-is-this-area-free-function#{toggle_previous_statuses}

Link to comment
dfx

+dfx

Posted
Posted

I went to try out the alerting of your cache being too close to another one and it was terrible. I put in the exact coords of one of my caches and it didn't do anything! Do we have to wait for a few more hours until this update is complete?

 

who told you its been implemented with this update, the list in the first post definitely doesn't have it

 

http://feedback.geoc...vious_statuses}

 

Yeah, so? That doesn't say it would be included in today's update, now does it? It's not in the release notes (see first post here), so obviously it wasn't included.

Link to comment
lemmykc

+lemmykc

Posted
Posted

I went to try out the alerting of your cache being too close to another one and it was terrible. I put in the exact coords of one of my caches and it didn't do anything! Do we have to wait for a few more hours until this update is complete?

 

who told you its been implemented with this update, the list in the first post definitely doesn't have it

 

http://feedback.geoc...vious_statuses}

 

Yeah, so? That doesn't say it would be included in today's update, now does it? It's not in the release notes (see first post here), so obviously it wasn't included.

 

Ah, yes it does.

 

Our next release – currently scheduled for Oct. 6 – will implement the first features involved in this request. After pressing the “Report new listing” button on the Report a Cache page, the system will check to see if another cache is near the coordinates for the new listing. If so, it will warn the user that the cache is too close to an existing cache.
Link to comment
t4e

+t4e

Posted
Posted (edited)

I went to try out the alerting of your cache being too close to another one and it was terrible. I put in the exact coords of one of my caches and it didn't do anything! Do we have to wait for a few more hours until this update is complete?

 

who told you its been implemented with this update, the list in the first post definitely doesn't have it

 

http://feedback.geocaching.com/forums/75775-geocaching-com/suggestions/1403237-is-this-area-free-function#{toggle_previous_statuses}

 

started · OpinioNateAdminOpinioNate (Official Rep, Geocaching) responded · October 05, 2011

 

We are working on the initial features involved in this request.....

 

what part of that says they're done developing it and its been included in this update?

 

 

 

Ah, yes it does.

 

Our next release – currently scheduled for Oct. 6 – will implement the first features involved in this request. After pressing the “Report new listing” button on the Report a Cache page, the system will check to see if another cache is near the coordinates for the new listing. If so, it will warn the user that the cache is too close to an existing cache.

 

regardless its not in the first post outlining the updates for today

Edited by t4e
Link to comment
Don_J

+Don_J

Posted
Posted

I went to try out the alerting of your cache being too close to another one and it was terrible. I put in the exact coords of one of my caches and it didn't do anything! Do we have to wait for a few more hours until this update is complete?

 

who told you its been implemented with this update, the list in the first post definitely doesn't have it

 

http://feedback.geoc...vious_statuses}

 

Yeah, so? That doesn't say it would be included in today's update, now does it? It's not in the release notes (see first post here), so obviously it wasn't included.

 

Expand the Admin notes.

 

Moun10Bike (Admin, Geocaching) responded · September 27, 2011

 

Our next release – currently scheduled for Oct. 6 – will implement the first features involved in this request. After pressing the “Report new listing” button on the Report a Cache page, the system will check to see if another cache is near the coordinates for the new listing. If so, it will warn the user that the cache is too close to an existing cache.

CAPTCHA will be implemented for cache submission to reduce automated attempts at finding the final coords to nearby multis/mysteries. The feature will also include a link to search nearby geocaches using the coordinates provided. The user can still submit the cache listing after they see the warning. (4316)

 

The following notes do not explain that it will be delayed, so I was surprised not to see it in the Release Notes.

Link to comment
knowschad

knowschad

Posted
Posted

logs are loading fast now, so "page down" can be used effectively :D

 

i like the avatars next to the log, now if only there will be a prettier image, maybe Signal, for those that don't have one, in place of that grey expressionless face lol

 

I agree... well done on fixing the speed that the logs load! It will still be a pain on some caches, but this is MUCH more useable!

So it seems to be faster, but is there a shortcut to get to the very bottom (1st log) of a cache page?

 

No, I don't think there is. That's why I said that it will still be a pain on some [very popular] caches.

 

Just click on the 'View Logbook' link, then click the highest numbered page. That seems pretty quick to me :)

 

MrsB

 

Does that load all logs, or only the last page of logs (I suppose I can check for myself, huh?)

Link to comment
knowschad

knowschad

Posted
Posted (edited)

Changed Challenges terminology "Flag" to "Needs Archived" for more clarity among non-English speakers.

 

I'm not seeing this. I have done a Ctrl/F5 refresh and still only see Flag.

 

Thanks. It was changed in one location (and then subsequently changed again to "take action"). Looks like the comment link was not, though. We'll get that fixed.

 

Needs Archived, is pretty poor English, is it acceptable in American? Surely it should say Needs Archiving?

 

Just my view, all elses seems to be fine, keep up the good work.

 

"ALL ELSES SEEM TO BE FINE"? :lol: OK, glad to hear it.

 

That (sigh!) has been a complaint for as long as I've been reading these forums. I think that it has been recently accepted by Merriam-Webster, but I could be wrong.

 

I was just watching Jay Leno, and twice (so far) he asked someone, "Do you have anything that needs fixed?"

Edited by knowschad
Link to comment
Don_J

+Don_J

Posted
Posted

Changed Challenges terminology "Flag" to "Needs Archived" for more clarity among non-English speakers.

 

I'm not seeing this. I have done a Ctrl/F5 refresh and still only see Flag.

 

Thanks. It was changed in one location (and then subsequently changed again to "take action"). Looks like the comment link was not, though. We'll get that fixed.

 

Needs Archived, is pretty poor English, is it acceptable in American? Surely it should say Needs Archiving?

 

Just my view, all elses seems to be fine, keep up the good work.

 

"ALL ELSES SEEM TO BE FINE"? :lol: OK, glad to hear it.

 

That (sigh!) has been a complaint for as long as I've been reading these forums. I think that it has been recently accepted by Merriam-Webster, but I could be wrong.

 

I was just watching Jay Leno, and twice (so far) he asked someone, "Do you have anything that needs fixed?"

 

Pardon my OT.

In California, we ask "Do you have anything that needs to be fixed". When I visited my dad in Georgia, I heard, "Do you need anything that needs fixin'", and "I'm fixi'n on fixi'n that truck", but I've never heard it the Leno way.

 

Of course, most of us forum regulars know that "Needs Reviewer Attention" is proper grammar for "Needs Archived". In fact it's been "Prioritized" in the system for almost two years.

Link to comment
The HERB5

+The HERB5

Posted
Posted

Is the promised "public" API ever gonna be "public"? Or is it just gonna be a few applications here and there and that's it?

 

Our intention is to eventually make the API fully public, but there are many steps between here and there. We have accepted around 150 requests for access at this point, so although a "closed Beta" we are not putting up too many barriers to entry.

An update on the FEEDBACK site would be good, or is it only a one-way thing. :anibad:

An update once a month was deemed too much!! How about an update when it's affected by a site update. ANYTHING!!!!!

Link to comment
LightHouseSeekers

+LightHouseSeekers

Posted
Posted

logs are loading fast now, so "page down" can be used effectively :D

 

i like the avatars next to the log, now if only there will be a prettier image, maybe Signal, for those that don't have one, in place of that grey expressionless face lol

 

I agree... well done on fixing the speed that the logs load! It will still be a pain on some caches, but this is MUCH more useable!

So it seems to be faster, but is there a shortcut to get to the very bottom (1st log) of a cache page?

 

No, I don't think there is. That's why I said that it will still be a pain on some [very popular] caches.

 

Just click on the 'View Logbook' link, then click the highest numbered page. That seems pretty quick to me :)

 

MrsB

 

Does that load all logs, or only the last page of logs (I suppose I can check for myself, huh?)

I see that it allows you to go any page (group of 10 entries) in the logbook.

So it is a simple way to get to the 1st group of logs.

You may select any page (of 10) that you wish to see.

Although I would like to be able to jump to the bottom, then scroll up through the entries. Now you must select the page one by one.

Link to comment
dfx

+dfx

Posted
Posted
I see that it allows you to go any page (group of 10 entries) in the logbook.

So it is a simple way to get to the 1st group of logs.

You may select any page (of 10) that you wish to see.

Although I would like to be able to jump to the bottom, then scroll up through the entries. Now you must select the page one by one.

 

It sure is an easy way to get to the first log. On cache pages with a lot of logs it's probably even faster than the old way through "view all logs". The only thing that you can't do now is a text-based search through all the logs, when you're looking for something specific but don't know where it is.

Link to comment
Guest
This topic is now closed to further replies.
Followers 8
Go to topic listing
×
×
  • Create New...