Next week I will release an update for GetFinds(). For geocaches where the owner have had their account deleted at Geocaching.com the owner-id is today set to 1 and name to [DELETED USER]. This is something Geocaching.com has added a while back. This thread makes us aware that not all scripts handles that, which is understandable. There are two approaches to go here. Either scripts has to handle the magic ID 1 and a special username, or we just replace those with invalid values. I have chosen to replace those values with NULL. The result is that some scripts might fail after the update. But then at least they won't give faulty results. The fix for the scripts will probably be to check that owner_id and/or placed_by isn't null in a loop. But fix will of course vary for each affected script. I feel this change is better than using the ID=1 which will be a magic number most new scripts will miss handling. There are currently 233 enabled scripts that has the word owner_id in them. That's 231 potentially affected scripts. Some of them are just using the value to check that the one running the checker isn't the owner of what he logged. These checks will probably still work. /forum/read.php?6,61592,61592#msg-61592 Fri, 17 Apr 2026 18:18:25 +0000 Phorum 5.2.23 /forum/read.php?6,61592,62531#msg-62531 /forum/read.php?6,61592,62531#msg-62531 magma1447 Checker news Mon, 30 May 2022 08:15:25 +0000 /forum/read.php?6,61592,62528#msg-62528 /forum/read.php?6,61592,62528#msg-62528
OLD: 613
NEW: 8665]]> Hügh Checker news Sun, 29 May 2022 20:09:13 +0000 /forum/read.php?6,61592,62526#msg-62526 /forum/read.php?6,61592,62526#msg-62526 magma1447 Checker news Sun, 29 May 2022 20:01:31 +0000 /forum/read.php?6,61592,62525#msg-62525 /forum/read.php?6,61592,62525#msg-62525 Hügh Checker news Sun, 29 May 2022 19:59:09 +0000 /forum/read.php?6,61592,62524#msg-62524 /forum/read.php?6,61592,62524#msg-62524 magma1447 Checker news Sun, 29 May 2022 19:56:39 +0000 /forum/read.php?6,61592,62523#msg-62523 /forum/read.php?6,61592,62523#msg-62523
It looks like GentlePurpleRain hasn't logged in recently. Can this still be fixed?]]> Hügh Checker news Sun, 29 May 2022 19:54:27 +0000 /forum/read.php?6,61592,61592#msg-61592 /forum/read.php?6,61592,61592#msg-61592
For geocaches where the owner have had their account deleted at Geocaching.com the owner-id is today set to 1 and name to [DELETED USER]. This is something Geocaching.com has added a while back.

This thread makes us aware that not all scripts handles that, which is understandable. There are two approaches to go here. Either scripts has to handle the magic ID 1 and a special username, or we just replace those with invalid values.

I have chosen to replace those values with NULL. The result is that some scripts might fail after the update. But then at least they won't give faulty results. The fix for the scripts will probably be to check that owner_id and/or placed_by isn't null in a loop. But fix will of course vary for each affected script.

I feel this change is better than using the ID=1 which will be a magic number most new scripts will miss handling.

There are currently 233 enabled scripts that has the word owner_id in them. That's 231 potentially affected scripts. Some of them are just using the value to check that the one running the checker isn't the owner of what he logged. These checks will probably still work.]]> magma1447 Checker news Fri, 29 Apr 2022 18:12:04 +0000