Jump to content

RCH65

+Premium Members
  • Posts

    92
  • Joined

  • Last visited

Posts posted by RCH65

  1. On 6/24/2023 at 8:13 PM, kunarion said:

    As an example, here's one of several of my caches where the background disappeared.  There doesn't seem to be anything in common with the vanishings.  Some caches were active, most were previously archived, some old, some new, and a bunch from each category were unaffected.

     

     

    The link http://img.geocaching.com/user/21ca6899-ba86-4ba8-a4a1-68bcc8cfbd95.jpg to the background image s still part of the HTML code... but the image itself is gone (Error 404).
    I can't remember that I've ever seen an URL having img.geocaching.com/user/something... they usually contain img.geocaching.com/cache/something...

    Maybe they have removed some conversion/forwarding of old style URLs...

  2. 10 minutes ago, albertpang said:

    Now I have a question... how can I remove the "Needs Owner's Attention" filter on my Cache Owner Dashboard? In my case, I once disabled the cache; fixed the issue and now re-enabled the cache on business again. The filter is still there. Should I delete the NM log? 

     

    Deleting the NM log won't help.

    Just write an additional "owner maintenance" log.

    • Helpful 2
  3. 22 hours ago, Die C-SAU Bande said:

    But the most cachers I know, use this feature for cheating: not other player is able to view their logged caches but they like to boast about how many caches they've found.

     

    There are two easy ways to go around this:

    Official way

    • Go to the search form -> 'Filters'
    • Remove your own name from 'Not found by'
    • Enter the player's name in 'Found by'
    • Enter the period in 'Find Date' (Between)

    Inofficial way

  4. On 12/9/2022 at 9:17 AM, timdevaneynz said:

    So I have a gpsmap 66sr . Its geocaching reg fails . 

     

  5. On 12/9/2022 at 11:42 AM, HHL said:

    @timdevaneynz

    Why don't you just keep going like this? Garmin pretty much screwed up in Geocaching. I use my Garmin Montana 600 for emergencies only, when far away from civilization.

     

    On 12/9/2022 at 7:57 PM, Viajero Perdido said:

    If it's not too late to get your money back...

     

    Can we please stop giving useless answers?
    Reminds me of "Use Apple" advices in Windows forums (and vice-versa)

     

     

    • Helpful 1
  6. On 11/6/2022 at 2:00 AM, Bl4ckH4wkGER said:

    This is one of several cache type related changes and is intentional. Some Event types also got updated to newer more accurate names.

    Overall, the names now more closely align with what you see on your Profile, Statistics, etc.

     

    Wherigo type changed from

    <type>Geocache|Wherigo Cache</type>

    to

    <type>Geocache|Wherigo Caches</type>

     

    Looks like a typo...(?)

     

  7. 3 hours ago, Jayeffel said:

    If the ads were not there we would be charged more to keep the website and all associated items running. 

     

    That's why I'm asking (it wasn't sarcasm).
    How much Do I have to pay to get rid of this stuff?

    Ad revenues won't be more than a few cents per registered user.

    Premium subscription without this annoying ads/cookie/tracking stuff for a few dollars more? DEAL!

     

  8. On 5/16/2022 at 8:39 PM, RuideAlmeida said:

    Maybe the problem is not the website, but some other software you have running, I guess... and some providers used to block geocaching.com in Germany, by instance... who knows also in Belgium?!

     

    • There were no scripts running on my side... I even deactivated Tampermonkey to be sure...
    • The problem comes... the problem goes... (and comes back again) without any changes (on my side). 
    • If European providers block geocaching.com traffic, you couldn't just switch between browsers - and the problems would occur all over the site
    • I have the strong feeling that this is caused by some faulty data caching somewhere between 'you' and 'me' - and that the problem is somehow related to performance issues. This is why it comes and goes...
  9. On 5/13/2022 at 5:18 PM, RCH65 said:

    Can't recreate the problem right now. Everything is fine.
     


    Here we go again... 😨
    Now even one step earlier after clicking on 'view map' 

    {
      "code": "CSS_CHUNK_LOAD_FAILED",
      "type": "error",
      "request": "https://www.geocaching.com/play/map/public/ActionBar.css"
    }
    
    {
      "componentStack": "\n    at Lazy\n    at Suspense\n    at div\n    at div\n    at div\n    at x (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:112440)\n    at div\n    at div\n    at oe (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:91214)\n    at C (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:195093)\n    at s (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:81490)\n    at O\n    at u (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:402215)\n    at L\n    at t.SidebarProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:10943)\n    at M\n    at t.ActiveCacheProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:75249)\n    at T\n    at t.MobileListProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:15962)\n    at P\n    at t.ActiveListProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:77235)\n    at D\n    at t.ViewProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:17699)\n    at E\n    at t.ApiProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:18210)\n    at A\n    at s (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:80360)\n    at x\n    at t.MapProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:78380)\n    at F\n    at t.BrowserProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:28034)\n    at k\n    at t (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:112036)\n    at Suspense\n    at t.TranslationProvider (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:784804)\n    at n (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:422991)\n    at t (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:114152)\n    at t (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:108533)\n    at l (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:353073)\n    at o (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:354528)\n    at C (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:195093)\n    at f (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:193158)\n    at C (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:735806)\n    at div\n    at i (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:1089861)\n    at C (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:714332)\n    at h\n    at t.LimitSearchProvider (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:227307)\n    at p\n    at v (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:319697)\n    at v\n    at t.FiltersProvider (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:707983)\n    at g\n    at t.ExperienceProvider (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:706378)\n    at m\n    at t.UserProvider (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:798898)"
    }

    Chrome 101.0.4951.67 (WIN 10)
    No scripts active.
    Works on Edge (same machine)

     

  10. 18 minutes ago, Bl4ckH4wkGER said:

    I am not able to reproduce what is shown in your screenshots. Both maps work fine on my machine with Chrome (Version 101.0.4951.67 (Official Build) (64-bit)).

     

    Strange... everything back to normal right now...

    Maybe it depends on to which server (instance) I am/was connecting to (?)
    Can't recreate the problem right now. Everything is fine.
     

  11. 16 hours ago, Zop said:

    When uploading field notes from GPS using the older and better logging page, it would upload the 'drafts' found since the previous upload.
    Trying today, we are unable to upload our field notes with the error "Cannot Upload More Than 1000 Caches at a Time"

     

    From time to time you have to empty the geocache_visits.txt file on your GPS device.

    The error occurs as soon as there are more than 1000 records in the text file.

     

    It looks like the process is uploading only new drafts (since the last upload) but this is not true.
    It's always uploading the entire file and the webservice throws away duplicate entries.

    • Helpful 2
  12. Ten years later... and we're still on GPX 1.0.1 without...

    - links to images

    - personal notes

    - "changed coordinates" indicator

     

    I know... the online API (available to handpicked developers) is sexy, cool and strategic... and downloading data (for undefined purpose to everyone!) is quite evil.

     

    It's still ridicoulously hard to perform a simple task like 'marking solved caches' on an offline GPSr without API access and 3rd party software.
    Believe me... there *are* reasons to use an offline GPS receiver.

     

    Why don't you give us the ability to write our own scripts by simply processing a GPX file?

     

    BTW: It's not *your* data... it's *our* data... 

     

    • Upvote 1
    • Funny 1
    • Helpful 1
  13. On 10/3/2021 at 1:00 AM, rassilon256 said:

    Once you've solved a mystery cache the pin on the map moves to the real location. I've looked around both on the website and the iOS app and can't see any way to look at the posted location after solving. What am I missing?

     

    This is easy on the website:
    Just click on the 'pencil' (next to the solved coordinates in italic) and it will show the original coordinates.

×
×
  • Create New...