So, the mail with the asked information is on the way to you, thanks a lot.
Greetings
M.
Greetings
M.
↧
Corrected Coordinates by schlemrk - 2019-04-12
↧
BadgeGen_V4.0 feed back by RNKBerlin - 2019-04-12
| QUOTE (taybee @ April 12, 2019 12:41 am) |
| BadgeGen is update to V4.0.0.9 how |
Sterling stuff. Diamond on top and all that. Wonderful.
I just noticed that the Republic of China (aka Taiwan) is currently missing. The last of the 40 countries we've visited so far. If you're ever bored...
Any road, thanks a lot, Geoff. That macro is better than ever!
↧
↧
Fehler beim Statusabruf by stoeckheim - 2019-04-12
Hallo noch mal,
mit der alten API und bis Version 8.7.1.117 hat der Status-Check niemals die in der Datenbank als gefunden markierten und gelockten Caches verändert. Im Protokoll stand, dass diese Caches aufgrund des Locks nicht verändert wurden.
Beim Status-Check mit *.121 waren jedoch plötzlich alle meine in GSAK gelockten und als gefunden markierten Caches plötzlich nicht mehr gefunden.
Also hat sich das Verhalten dahingehend geändert.
Ich habe einige Caches noch nicht online geloggt, sondern nur in den Drafts, diese allerdings in GSAK entsprechend markiert und gelockt.
Viele Grüße
Thomas
mit der alten API und bis Version 8.7.1.117 hat der Status-Check niemals die in der Datenbank als gefunden markierten und gelockten Caches verändert. Im Protokoll stand, dass diese Caches aufgrund des Locks nicht verändert wurden.
Beim Status-Check mit *.121 waren jedoch plötzlich alle meine in GSAK gelockten und als gefunden markierten Caches plötzlich nicht mehr gefunden.
Also hat sich das Verhalten dahingehend geändert.
Ich habe einige Caches noch nicht online geloggt, sondern nur in den Drafts, diese allerdings in GSAK entsprechend markiert und gelockt.
Viele Grüße
Thomas
↧
Downloading Pocket Queries via GSAK API by Giz - 2019-04-12
I downloaded the update and checked and I am running the most up to date version of GSAK
Using the "New" Groundspeak dropdown menu, I requested a new access token.
Clicked on "Agree" and saw the quick screen that indicated the API call was successful.
Clicked on the menu and requested pocket queries and received the following messages:
The Groundspeak API has returned the error "Unauthorized" . The most common reason is an expired or corrupt token. Would you like us to try again?
I selected Yes and received the following message:
There was a problem communicating with the Groundspeak API. At that point I clicked on "show error" and obtained the following error log:
ChilkatLog:
QuickGetStr(796ms):
DllDate: Dec 27 2016
ChilkatVersion: 9.5.0.65
UnlockPrefix: GSAKNEHttp
Architecture: Little Endian; 32-bit
Language: ActiveX
VerboseLogging: 1
url: https://api.groundspeak.com/v1.0/users/me/?...d,ReferenceCode
httpRequestStr(796ms):
getHttpConnectionByUrl:
findAddHttpConn:
GetIEProxySetting:
RegistryQueryError: The system cannot find the file specified.
ValueName: ProxyServer
Failed to get key value
valueName: ProxyServer
Failed to read registry: CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Internet Settings/ProxyServer
--GetIEProxySetting
--findAddHttpConn
--getHttpConnectionByUrl
a_quickReq(796ms):
quickHttpRequest(796ms):
httpVerb: GET
url: https://api.groundspeak.com/v1.0/users/me/?...d,ReferenceCode
openHttpConnection(16ms):
Using existing connection.
--openHttpConnection
buildQuickRequest(47ms):
genStartLine:
Adding params to the start line...
startLine: GET /v1.0/users/me/?fields=membershiplevelId,ReferenceCode HTTP/1.1
--genStartLine
getMimeHeaderHttp:
headerField: Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
headerField: Connection: keep-alive
headerField: User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
headerField: Accept-Language: en-us,en;q=0.5
headerField: Authorization: Bearer
--getMimeHeaderHttp
addCookies(47ms):
Auto-adding any accumulated cookies.
CookieDir: C:\Users\rbarnhart\AppData\Roaming\gsak\cookies
CookieDomain: api.groundspeak.com
CookiePath: /v1.0/users/me/
loadCookieJar:
Path: /v1.0/users/me/
GetDomainCookiesXml:
CookieDir: C:\Users\rbarnhart\AppData\Roaming\gsak\cookies
Domain: api.groundspeak.com
--GetDomainCookiesXml
--loadCookieJar
AddingCookie: ASP.NET_SessionId=ml3svaws2fsepm0svn2wdn4p; _sm_au_d=1
--addCookies
--buildQuickRequest
quickRequestHeader:
requestHeader: GET /v1.0/users/me/?fields=membershiplevelId,ReferenceCode HTTP/1.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Accept-Language: en-us,en;q=0.5
Authorization: Bearer
Accept-Encoding: gzip
Cookie: ASP.NET_SessionId=ml3svaws2fsepm0svn2wdn4p; _sm_au_d=1
Host: api.groundspeak.com
--quickRequestHeader
sendRequestHeader(125ms):
sendHeaderElapsedMs: 125
--sendRequestHeader
readResponseHeader(62ms):
responseHeader: HTTP/1.1 401 Unauthorized
CorrelationGuid: 84d8c5ef-e124-46fc-b449-3ace39cbe9e5
Date: Fri, 12 Apr 2019 19:45:12 GMT
Content-Length: 0
--readResponseHeader
statusCode: 401
statusText: Unauthorized
readResponseBody(62ms):
bDiscard: 0
contentLength: 0
No response body to receive...
--readResponseBody
--quickHttpRequest
computeAuthorization:
Password is empty.
--computeAuthorization
computeAuthorization failed (3).
--a_quickReq
Returning failed status because of HTTP response code.
--httpRequestStr
Failed.
--QuickGetStr
--ChilkatLog
After this series of events, I tried to obtain a new token using Token Option #2 with no luck.
Note: I accessed my geocaching.com account and GSAK is listed as being authorized in my account to share data, etc.
Thanks for your help,
Randy
Using the "New" Groundspeak dropdown menu, I requested a new access token.
Clicked on "Agree" and saw the quick screen that indicated the API call was successful.
Clicked on the menu and requested pocket queries and received the following messages:
The Groundspeak API has returned the error "Unauthorized" . The most common reason is an expired or corrupt token. Would you like us to try again?
I selected Yes and received the following message:
There was a problem communicating with the Groundspeak API. At that point I clicked on "show error" and obtained the following error log:
ChilkatLog:
QuickGetStr(796ms):
DllDate: Dec 27 2016
ChilkatVersion: 9.5.0.65
UnlockPrefix: GSAKNEHttp
Architecture: Little Endian; 32-bit
Language: ActiveX
VerboseLogging: 1
url: https://api.groundspeak.com/v1.0/users/me/?...d,ReferenceCode
httpRequestStr(796ms):
getHttpConnectionByUrl:
findAddHttpConn:
GetIEProxySetting:
RegistryQueryError: The system cannot find the file specified.
ValueName: ProxyServer
Failed to get key value
valueName: ProxyServer
Failed to read registry: CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Internet Settings/ProxyServer
--GetIEProxySetting
--findAddHttpConn
--getHttpConnectionByUrl
a_quickReq(796ms):
quickHttpRequest(796ms):
httpVerb: GET
url: https://api.groundspeak.com/v1.0/users/me/?...d,ReferenceCode
openHttpConnection(16ms):
Using existing connection.
--openHttpConnection
buildQuickRequest(47ms):
genStartLine:
Adding params to the start line...
startLine: GET /v1.0/users/me/?fields=membershiplevelId,ReferenceCode HTTP/1.1
--genStartLine
getMimeHeaderHttp:
headerField: Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
headerField: Connection: keep-alive
headerField: User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
headerField: Accept-Language: en-us,en;q=0.5
headerField: Authorization: Bearer
--getMimeHeaderHttp
addCookies(47ms):
Auto-adding any accumulated cookies.
CookieDir: C:\Users\rbarnhart\AppData\Roaming\gsak\cookies
CookieDomain: api.groundspeak.com
CookiePath: /v1.0/users/me/
loadCookieJar:
Path: /v1.0/users/me/
GetDomainCookiesXml:
CookieDir: C:\Users\rbarnhart\AppData\Roaming\gsak\cookies
Domain: api.groundspeak.com
--GetDomainCookiesXml
--loadCookieJar
AddingCookie: ASP.NET_SessionId=ml3svaws2fsepm0svn2wdn4p; _sm_au_d=1
--addCookies
--buildQuickRequest
quickRequestHeader:
requestHeader: GET /v1.0/users/me/?fields=membershiplevelId,ReferenceCode HTTP/1.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Accept-Language: en-us,en;q=0.5
Authorization: Bearer
Accept-Encoding: gzip
Cookie: ASP.NET_SessionId=ml3svaws2fsepm0svn2wdn4p; _sm_au_d=1
Host: api.groundspeak.com
--quickRequestHeader
sendRequestHeader(125ms):
sendHeaderElapsedMs: 125
--sendRequestHeader
readResponseHeader(62ms):
responseHeader: HTTP/1.1 401 Unauthorized
CorrelationGuid: 84d8c5ef-e124-46fc-b449-3ace39cbe9e5
Date: Fri, 12 Apr 2019 19:45:12 GMT
Content-Length: 0
--readResponseHeader
statusCode: 401
statusText: Unauthorized
readResponseBody(62ms):
bDiscard: 0
contentLength: 0
No response body to receive...
--readResponseBody
--quickHttpRequest
computeAuthorization:
Password is empty.
--computeAuthorization
computeAuthorization failed (3).
--a_quickReq
Returning failed status because of HTTP response code.
--httpRequestStr
Failed.
--QuickGetStr
--ChilkatLog
After this series of events, I tried to obtain a new token using Token Option #2 with no luck.
Note: I accessed my geocaching.com account and GSAK is listed as being authorized in my account to share data, etc.
Thanks for your help,
Randy
↧
Fehler beim Statusabruf by stoeckheim - 2019-04-12
Quote kai team:
Please see this thread.
Sorry, this thread meets not exact my problem.
In my database are just my own caches.
Until 8.7.1.117 the statuscheck never overwrote my foundstatus, when the cache was locked.
But *121 did exact this. All of my as found marked caches were unfound now. It took some hours to get them back.
Kind regards
Please see this thread.
Sorry, this thread meets not exact my problem.
In my database are just my own caches.
Until 8.7.1.117 the statuscheck never overwrote my foundstatus, when the cache was locked.
But *121 did exact this. All of my as found marked caches were unfound now. It took some hours to get them back.
Kind regards
↧
↧
FavCacheCounter.gsk by The CEO - 2019-04-12
The macro used the old API GetUsersWhoFavoritedCache method.
There is no direct replacement for that method.
The basic goal of the macro is to update the favorite points.
The most simple way to do that is a "refresh cache data" with the light method.
So in its most basic form, you get a one file macro:
For 1 cache:
For all caches in filter:
There is no direct replacement for that method.
The basic goal of the macro is to update the favorite points.
The most simple way to do that is a "refresh cache data" with the light method.
So in its most basic form, you get a one file macro:
For 1 cache:
| GSK |
GcRefresh Scope=Current LoadSettings="* Use GSAK defaults *" Format=Light |
For all caches in filter:
| GSK |
GcRefresh Scope=Filter LoadSettings="* Use GSAK defaults *" Format=Light |
↧
Corrected Coordinates by Kai Team - 2019-04-12
Thanks - I got the information. The API Log shows that Geoaching.com is replying with "statusCode: 401" - "Unauthorized". I'll have to figure out why the macro is not trapping and correctly reporting that error, but in the meantime you should try going to Geocaching.com Access>Get Another Access Token. Log into Geocaching.com (if needed) and click the "Authorize" button to allow GSAK to use your Geocaching.com account to get data. Hopefully that will fix the problem for you.
↧
Publish Logs opens offscreen by Pprime (P`) - 2019-04-12
I have a weird problem, usually my laptop is connected to multiple monitors, and Publish Logs is set to open on a different monitor to the rest of gsak. It does so happily.
I am on holidays now and just have my laptop screen. No other screen is connected (not even ghost connected in Windows), but opening Publish Logs .... it disappears off the laptop's screen (I presume to wherever it feels the previous settings should put it). It is still somehow active - because I can't do anything on the main gsak until I alt-F4 to close the log screen.
I cannot Windows-left-arrow move it, nor have I found any other way to rescue this rogue window. I can't see anywhere a config file setting or similar that hard codes it to open on a different monitor.
Any ideas? I'd like to log some caches before I forget what they were all about.
P`
I am on holidays now and just have my laptop screen. No other screen is connected (not even ghost connected in Windows), but opening Publish Logs .... it disappears off the laptop's screen (I presume to wherever it feels the previous settings should put it). It is still somehow active - because I can't do anything on the main gsak until I alt-F4 to close the log screen.
I cannot Windows-left-arrow move it, nor have I found any other way to rescue this rogue window. I can't see anywhere a config file setting or similar that hard codes it to open on a different monitor.
Any ideas? I'd like to log some caches before I forget what they were all about.
P`
↧
Fehler beim Statusabruf by HHL - 2019-04-12
| QUOTE (stoeckheim @ April 12, 2019 08:56 pm) |
| [...] Ich habe einige Caches noch nicht online geloggt, sondern nur in den Drafts, diese allerdings in GSAK entsprechend markiert und gelockt. [...] |
Lies bitte den letzten Satz meines vorhergehenden Postings noch einmal. Ohne dein Fundlog setzt GSAK den Cache auf ungefunden. Und die Logs sind ausweislich des Hilfe-Eintrags eben nicht gelockt.
Hans
↧
↧
Publish Logs opens offscreen by Pprime (P`) - 2019-04-12
OK, advice from elsewhere (I learn something new everyday)...
Alt-Space then select move and use the keyboard arrows - rescued my rogue window.
Probably worthwhile checking gsak behaviour on windowing next time that code is being looked at.
Alt-Space then select move and use the keyboard arrows - rescued my rogue window.
Probably worthwhile checking gsak behaviour on windowing next time that code is being looked at.
↧
BadgeGen_V4.0 feed back by taybee - 2019-04-12
| QUOTE (RNKBerlin @ April 13, 2019 08:56 am) | ||
Sterling stuff. Diamond on top and all that. Wonderful. I just noticed that the Republic of China (aka Taiwan) is currently missing. The last of the 40 countries we've visited so far. If you're ever bored... Any road, thanks a lot, Geoff. That macro is better than ever! |
update state list and set the state number to 8 online only
offline will be update in V4.0.1.0
@ RNKBerlin reun Badgegen Flags should be here
↧
New geocaching api by sloth96 - 2019-04-12
| QUOTE (rcorfman @ April 12, 2019 12:05 pm) |
| Also, it shouldn't matter whether the access token has expired or not when attempting to refresh it. That is, the refresh token may be used immediately after receiving it or months later. |
Are you saying the behavior I am seeing is a bug?
The situation I think I am seeing is that the access token has expired, GSAK attempts to use it, and declares an error. Tthere is no attempt to perform a refresh even when the access token has expired.
↧
BadgeGen_V4.0 feed back by taybee - 2019-04-12
| QUOTE (Gill & Tony @ April 10, 2019 01:36 pm) |
| One thought for the future. There are some countries (e.g. Singapore or Hong Kong) which have no states. Others, like Croatia, have no states, but do have counties. At the moment we have to invent a state name so the macro can award the country badge. My suggestion is that if a country is defined as having only one state then any find should award the diamond (100%) badge without reference to the state names. Similarly, if all states for a particular country are blank, the macro could use the counties instead of the states. Thanks Tony |
hi all
will be looking at this for V4.0.1.x
looking for Caches that have the following Courty's that have
1, NO state name and NO County name
2 No State name and County name
Please post the GC number so i can download it to testing
↧
↧
BadgeGen_V4.0 feed back by RNKBerlin - 2019-04-12
| QUOTE (taybee @ April 12, 2019 10:48 pm) |
| @ RNKBerlin reun Badgegen Flags should be here |
And it was. But also this error.
I cannot reproduce the error. It occurred after I'd selected Taiwan from the country list.
↧
BadgeGen_V4.0 feed back by Gill & Tony - 2019-04-12
| QUOTE (taybee @ April 13, 2019 07:01 am) | ||
hi all will be looking at this for V4.0.1.x looking for Caches that have the following Courty's that have 1, NO state name and NO County name 2 No State name and County name Please post the GC number so i can download it to testing |
I think a better approach would be to modify your country list. Just looking at caches in someone's database could be using invalid data. At the moment you have something like country name and number of states.
Maybe change this to country name, number of states and number of counties. If states is 1 award diamond. If states is zero count counties and if both states and counties are zero award diamond.
↧
Fehler beim Statusabruf by HHL - 2019-04-12
Erstelle Load-Settings mit den speziellen Lock-Flags und verwende diese Settings beim Refresh*. Bei einem Test mit der neuen API gingen weder Fundstatus noch Funddatum verloren. ![smile.gif]()
![user posted image]()
![user posted image]()
Hans
* ein Status-Check respektiert leider die Extra-Lock-Felder nicht. Da der Status-Check mit der API2 eigentlich ein Refresh ist und vermutlich die GSAK Default Load-Settings verwendet, ist das auch kein Wunder.
Hans
* ein Status-Check respektiert leider die Extra-Lock-Felder nicht. Da der Status-Check mit der API2 eigentlich ein Refresh ist und vermutlich die GSAK Default Load-Settings verwendet, ist das auch kein Wunder.
↧
New geocaching api by rcorfman - 2019-04-12
| QUOTE (sloth96 @ April 12, 2019 01:50 pm) | ||
Are you saying the behavior I am seeing is a bug? The situation I think I am seeing is that the access token has expired, GSAK attempts to use it, and declares an error. Tthere is no attempt to perform a refresh even when the access token has expired. |
The behavior you are seeing seems suspicious, so yes, I presume it is a bug or a deficiency that could use improvement. You had some misstatements in your description so I only meant to clarify how the token refresh works.
↧
↧
BadgeGen_V4.0 feed back by taybee - 2019-04-12
| QUOTE (RNKBerlin @ April 13, 2019 10:40 am) | ||
And it was. But also this error. I cannot reproduce the error. It occurred after I'd selected Taiwan from the country list. |
looking into error
thanks for the info
@RNKBerlin can you please reload you profile on your server. button may not be working on the server
↧
Grid index out of range by clyde - 2019-04-12
This bug is truly weird! ![wacko.gif]()
![wacko.gif]()
I still don't fully understand the problem but I have now made some tweaks in the code that *seems* to fix the problem (and fixes the crash)
So please upgrade to build 125, cross your fingers, see what happens.![ph34r.gif]()
I still don't fully understand the problem but I have now made some tweaks in the code that *seems* to fix the problem (and fixes the crash)
So please upgrade to build 125, cross your fingers, see what happens.
↧
8.7.1 Updates by clyde - 2019-04-12
Build 125 (patch) Note: You must have installed 8.7.0 Build 0 (V8.7 final from here) at least once before installing this update.
New api - Tentative fix for a problem with trackables (more info)
Download here https://gsak.net/GSAK871B125.exe
New api - Tentative fix for a problem with trackables (more info)
Download here https://gsak.net/GSAK871B125.exe
↧