| QUOTE (j-w @ April 07, 2019 09:24 am) |
I found the following visual differences between 4.0.0.4 and 4.0.0.7, the "Total points" part is also not visible although it is in the HTML code.  |
| GSK |
MACROFLAG Type=Clear Range=ALl MACROFLAG Type=Set Range=100 GOTO Position=Top MFILTER WHERE=MACROFLAG |
| QUOTE (j-w @ April 06, 2019 04:48 pm) |
| Today I ran v4.0.0.7 for the first time and the Belt picture and the 'other banners' are now showing at the bottom of all Tabs instead of only on the Badges Tab. |
| QUOTE (sbeelis @ April 07, 2019 11:48 pm) | ||
I think that is due to a lot of mismatched html tags. I looked at the latest output of V4.0.0.7 thinking I might easily find the mismatched tag. However, after looking at the output, there are so many mismatching tags that my IDE is totally overwhelmed trying to match them. The first screenshot shows lines 1 - 300 (the collapsed block on the first line contains the badge output from line 1 to 228 which is correct). I found so many mismatches on lines 229 to 300 that I gave up going through the rest. I don't have time right now, but I'll try to look at the output of the V3 macro tonight to see how much of those mismatches were already in V3, but I am not surprised the tabbed output of FSG fails to properly place the BadgeGen output as it is now. |
| QUOTE (martijnc @ April 07, 2019 06:33 am) |
| There were also some caches with a strange code that come in using the old API: GC3913J A4 V2 had a code "GC3913J U A4" |
| QUOTE |
| %code %typ1 %name=2 |
| QUOTE |
| I fixed it in the database, |
| QUOTE |
| but any code not in the form ^GC[0-9A-Z]{1,6}$ will probably fail. |
| QUOTE (stigvi @ April 07, 2019 07:10 am) |
| I am currently on the 122 version. This is my Groundspeak api section. Is there anything wrong with it? [Groundspeak api] http://gsak.net/board/index.php?showtopic=...ndpost&p=188943 #OwnerRefreshDays=1 https://gsak.net/board/index.php?showtopic=...ndpost&p=250706 #ApiUrl=oldapi #ApiVersion=1 #ResetConnection=True http://gsak.net/board/index.php?showtopic=...ndpost&p=237519 #TokenExpireDays=5 http://gsak.net/board/index.php?showtopic=...ndpost&p=223955 #LogsPerCall=30 http://gsak.net/board/index.php?showtopic=...ndpost&p=222075 #LimitExceededRetries=5 http://gsak.net/board/index.php?showtopic=...ndpost&p=208271 #TimeOutSeconds=60 #AutomaticRetries=4 #RetryDelaySeconds=30 #EventTimeOutSeconds=120 [Custom Data] |
| QUOTE (Kai Team @ April 07, 2019 08:14 pm) | ||
No, it's fine. You could delete #ApiUrl=oldapi and #ApiVersion=1 but there's no need to delete them because they are commented out (#). Leaving #ApiUrl=oldapi in the file also makes it easier to switch between old and new API should the need arise. Are you having a problem that leads you to ask the question? |
| QUOTE (Seawind @ April 07, 2019 10:22 am) |
| Two days ago, my GSAK update ran perfectly, returning all 4,500 requested unfound caches in my area, and it ran fairly quickly. This morning, I ran the exact same request, and it ran very, very slowly, then "completed" at 2,000 of the expected 4,500 caches. Subsequent reruns returned 750 and then 300 caches. Are these issues related to the new API and still ongoing, or should I check anything on my end? |
