Jump to content

fallingforstars

+Premium Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by fallingforstars

  1. Happens far too often. I'm on a Mac using the Safari browser and the cookies popup is minuscule. Example attached. It is so annoying to have to keep repeating my cookie choices.
  2. The issue with poor communication with Google Maps is longstanding, particularly on my experience working on a desktop Mac. When wanting to view the larger map from a cache page the Map Control icon allows the selection of different layer types of view. Unfortunately clicking on this icon invariably causes a crash resulting in a "ChunkLoadError". Sometimes it works but it is very unreliable.... and frustrating.
  3. Extremely poor response from map. Many times the map will not load and crashes when trying to access satellite view (returns following error) - "code": "CSS_CHUNK_LOAD_FAILED", "type": "error", "request": "https://www.geocaching.com/play/map/public/58.css" { "componentStack": "\nLazy\nSuspense\ndiv\ndiv\nt@https://www.geocaching.com/play/map/public/vendor.655a98c18a2c1e22585b.js:2:758857\nli\nul\ndiv\nMapControls@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:114251\ndiv\nMapControlWrapper@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:113541\ndiv\ndiv\ndiv\nAppComponent@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:98141\nConnect(AppComponent)@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:112496\nSearchProvider@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:86823\nT\nV3Provider@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:395175\nP\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:11705\nE\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:78136\nx\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:16844\nD\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:80282\nA\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:81444\nF\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:18599\nk\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:19109\nN\nMapSettingsProvider@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:85064\n_\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:82140\nI\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:86203\nG\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:83085\nj\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:29007\nU\nt@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:65937\nSuspense\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:630713\nn@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:549789\nt@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:68053\nt@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:62433\ns@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:355104\no@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:356558\nConnect(o)@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:112496\nf@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:110560\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:544773\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:516789\nb\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:542462\nw\nInitialUrlProvider@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:519085\nx\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:543185\nM\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:139054\nE\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:541673\nA\nUserLookupProvider@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:231418\nC\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:539786\nk\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:510675\nO\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:515241\nS\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:508603\n_\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:644771" } This problem is recurring and has existed for many months but is never sorted - does an IT team exist at Geocaching?
  4. This is an old thread but here we are in January 2022 and the site is still extremely poor in its response times - usually in regard to displaying map requests, so maybe a problem of how it interacts with Google maps. Makes no difference which browser you're using. Two different occurrences shown below - first when requesting the map and second selecting the type of map ie.satellite. { "message": "Loading chunk 41 failed.\n(error: https://www.geocaching.com/play/map/public/41.80831800cf56ef48f631.js)", "name": "ChunkLoadError", "type": "error", "request": "https://www.geocaching.com/play/map/public/41.80831800cf56ef48f631.js" } { "code": "CSS_CHUNK_LOAD_FAILED", "type": "error", "request": "https://www.geocaching.com/play/map/public/53.css" }
  5. Some respondents seem to take offence to my statement where none was intended and also assumed I had problems. The main thrust of my proposal was to allow the greatest number of people to join the game by limiting the number of caches any one individual can place - it's not an elite club for a few members to commandeer an area by placing multitudes of caches - be they excellent or not. OK so make it a limit of 50 or another number but at least limit it. More people means more diverse ideas. It doesn't guarantee the quality will rise or diminish but it throws open the game to more people who may wish to place a cache of their own which will naturally fall within an area relatively local to where they live. Cache maintenance will always be a problem for some, and particularly the farther afield they are placed from the CO's home, logic dictates they are potentially more likely to be not up to par the greater the number of caches an individual has to manage. I've seen it myself but it is not within my remit to work with a CO or message them, no matter how friendly the approach, that their caches may be substandard, and quite honestly it would not be welcomed. People can be very sensitive to criticism no matter how well intentioned (take this post for instance). We have all done our bit to help out CO's by replacing damp logs etc, it's just common courtesy and part of the game, but allowing unlimited placement of caches within an area by one individual really does shut out many others who may have wished to do so.
  6. To allow the greatest amount of people to place caches I think it would be advantageous to restrict a limit to say 10 caches per person. There are numerous members who are responsible for placing very large numbers of caches. This not only shuts out lots of other people within an area but they all have to be maintained which has a diminishing probability of proper maintenance the more caches an owner places.
  7. Hi. Yes, I have Cachly and the circles are helpful. Hadn’t noticed that the solved mystery caches stayed in their found position. That’s one up for Cachly. Thanks.
  8. Although I’ve been a cacher for just over a year now it seems absurd to me that having solved a series of mystery caches their positioning on the map reverts to their original position just for the sake of a design no doubt considered cool by the CO. I’ve done all the hard work, so what happens when I want to return to one of the caches to place a TB?.. I’ve now lost the reference to which one it is when for instance there are say 50 caches in the series. At least allow me the option to keep the icon on its discovered position. It is also important for strategic planning to know where there is available space to place caches of my own in the vicinity (not good practice to keep enquiring to a volunteer for a co-ordinates check). Apart from a pretty graphic element on the cache map it serves a very limited purpose and no purpose at all once solved.
  9. Is there any way to have the map on my Garmin Oregon 700 only display caches I haven’t yet found?
×
×
  • Create New...