PlasmaWave

Click this link to see the main topic where comments can be left

I am opted-in only from a few days ago - I like many of the new zoomable map search features but issues noticed so far that definitely need to be changed: (1) "FILTERS" not available on the main (first) screen - also cache "LIST" moved to second screen Following introduction of the new map search, "FILTERS" is no longer available when you first call-up the map search feature. Almost ALWAYS "filters" are needed when using this search feature, so the "FILTERS" button SHOULD be displayed on the first screen as in the previous version. With the new version, the user needs to click "go" (box usually empty) and only then can "filters" be selected on the second screen. I almost never use the main search box, needing to select multiple filters. I preferred seeing included caches LISTED on the main (first) screen - the new version main screen looks like adverts rather than features and requires moving to the second screen before caches are listed. (2) Drop-down "Loading geocaches" message on map search is really annoying This drop-down message is really annoying, constantly appearing & disappearing - particularly annoying when the map is being used on a phone. Visually appears to be like a 'flashing' image. Would be better to have a small symbol in a corner that whirls whilst loading (like a mouse pointer in Windows). Hardware/Software: Desk-top PC running Windows 10 and iPhone 7 Plus running 12.1 with browsers Firefox Quantum (63.0.1 32-bit) and Google Chrome (70.0.3538.77 Official Build 64-bit)

Cannot log into geocaching.com here in UK ... 17:00 local time! Any news from HQ? Two minutes after posting ... seems to be back

GC45CC "Ye Ole Survey Monuments" was originally created as a VIRTUAL and grandfathered, i.e. allowed to remain by geocaching.com, after virtual's were withdrawn - Groundspeak knew then and therefore should still be aware that the task for this cache involves cachers visiting different locations throughout the UK, each visit involving collecting specific information and sending this to the CO before logging as 'found'. As this cache is grandfathered by Groundspeak and therefore ALREADY has "special case" status, it SHOULD be allowed to remain with it's inherent multiple-found-logging. It is a popular cache amongst the UK caching fraternity that are interested in getting more out of the hobby that finding a filmpot by leaning out of their vehicle at the roadside!! In general I wholeheartedly support the change to prevent/avoid multiple found logs going forward, which incidental has really only arisen to the extend now seen since logging via smartphones in the field was possible. This shouldn't and needn't mean that old well supported individual grandfathered caches cannot remain. There have been a lot of comments in support of keeping this cache 'as-is', but also some unnecessarily derogatory comments too - please let's keep a sensible factual thread going!

Still unavailable at 20th March 2017 ... a real shame as the site was very good

Me too and able to upload UK Ordinance Survey mapping to the Pro version

UK time now 09:30 (Seattle plus 8hrs) and cannot log into the site ... was ok an hour ago

Does anyone know what happened to the "GeoTribes" travel bug & geo-coin tracking website (http://geotribes.geotastic.com/index.php). Site is no longer found - it was great for keeping tabs on your own TBs/GCs, showing all of them on a single world map. It also offered lots of other features for monitoring status and past travel. The site blipped (for me) a few weeks ago but I managed to get it back, then a few days ago ... no luck with connecting. If the site has unfortunately folded, does anyone know of any similar tracking site? Project-GC took over some of the "TB Rescue" website's aims when they closed down, but that is not a tracking site as GeoTribes operated. Thanks for any info ...

Thanks to Admin for the clarification ... also thanks for the follow-up posts. Would have been really helpful had the time frame for distributing the code been mentioned originally, so great to hear it will be added to the blog now.

What is happening about the "Friend to Find (FTF)" submissions? No contact from geocaching.com after submitting a form two days ago, on the second day of the allowed period, after persuading my daughter to try caching. TBH we couldn't believe the faff involved: having to sign multiple forms, sending photos, sending log URLs and separate third party photo permission forms from both of us - daughter said "if this is what caching involves, can't see me finding many caches!". All this for a badge, not even a souvenir. Anyway, no acknowledgement received after submitting the forms and no badge code received. Has anyone received anything from geocaching.com after submitting an FTF form?

If you change the log DATE, then the log moves to the selected date but I believe is then placed "last" - seems the user cannot change the order within a specific date once logs are posted

This issue is also being discussed in another thread ... see http://forums.Groundspeak.com/GC/index.php?showtopic=341506&st=0&gopid=5611688entry5611688

I realised I probably should have posted this under "Reported Bugs", so added the issue there and gave more info including tests I carried out (with screen shots). I too understood how the order worked previously and managed with it, but the recent change has not only added more confusion to the "order issue", BUT worse we in UK are seeing logs submitted via the geocaching.com website for NEWLY published caches (i.e. quick FTFs) are shown BEFORE the reviewer's published log! Now that is plain crazy. I show one example in that post where I managed joint FTF with two other folks ... the two logs sent from a Mobile App (PlasmaWave and NottsWalker) appear in correct order after the reviewer's log, but the third (Baira) sent his on-line from the geo-website and it is displayed before the reviewer's log. This was evening (about 20:00) in UK, so around midday Seattle Time. I have now seen the first logs being displayed before the reviewer's log quite a few times, so the above example was not a freak case. Take a look at my other post: http://forums.Groundspeak.com/GC/index.php?showtopic=341239&st=0&gopid=5611332entry5611332

There appears to have been a recent change by geocaching.com, which has resulted in several "log order" issues: (1) In the United Kingdom (i.e. 8 hrs in advance of Seattle Time) for newly published caches, logs sent direct from the geocaching.com cache page soon after publication are sometimes displayed BEFORE the reviewer's publication log! I have seen this crazy situation for several new caches recently, where logs are sent a short time after the publication time (see image). (2) Logs submitted on-line in the UK (i.e. direct via the geocaching.com cache page) are now displayed earlier than those submitted from Mobile Apps & GSAK, presumably until Seattle Time 'passes' the original App log local time (see image). (3) Attached image shows test logs sent in the following order using: (1) "Looking4Cache" Mb App, (2) Official geocaching.com iPhone Mb App, (3) GSAK, (4) Direct from the geocaching.com cache page. Time actually sent is shown in the individual logs, but the last log sent direct from the geocaching.com cache page is displayed before the three earlier logs (see image). (4) Not a change but worth noting, as it adds more confusion to the above situation, is that Mobile Apps are tied to Seattle Time, so logs are displayed on the cache page in advance of local time (e.g. UK is 8 hours in advance of Seattle Time), so the logged DATE will be changed to the previous day if sent before midnight Seattle Time. Logs sent from a Mobile App for newly published caches will appear before the reviewer's publication log if local time is before midnight Seattle Time. This recent change is causing considerable confusion ... geocaching.com need to look at this situation again.

Until recently a logged visit for a cache submitted using an App was displayed on the cache page in advance of local time (e.g. -8 hours for UK), so the logged date would appear before the publication date if it were before midnight Seattle time. Recently that situation has changed, presumably to avoid the issue described, however this now means that on-line website logs submitted (for UK) up to 8 hours AFTER an App log are displayed before the App log. I have logged first-to-find logs for several newly published caches recently via an App, only to find much later in the day subsequent finders logs submitted on-line via the website are displayed before my much earlier log. I tested this a couple of times in the field by logging via the website instead of the App, which confirmed this change. You might say, "well log via the website if it matters to you" ... yes it's true, that would work and show the correct logging "order", BUT it is difficult logging on a phone at GZ via the website - much easier with an App. Geocaching.com appear to have made a change, which has created the same problem as before but in 'reverse' - in my mind, that is not a good solution. Could Groundspeak take another look at this issue and hopefully think of cachers who are NOT on Seattle time? Not sure why an App submitted log cannot be adjusted for the local time difference from Seattle and then be displayed correctly. Would be interested to hear from geocaching.com experts

Thanks for the update from Admin. I checked by adding a couple of Favourites and happy to see they did stay after refreshing the cache pages. I presume Fav Points added by cachers over past week are lost - unless they go back into each cache page (that's not going to happen in practice). Next question: this exact same issue happened 12 months ago, so is the latest fix genuinely permanent or just temporary again?

12 months or so later and exactly same fault is happening ... you award a Fav Point - it shows on the cache page ok, but when page is refreshed the Fav Point has disappeared! Time that Groundspeak looked at this recurring issue!!

Monday 9th May and same issue still there ... you add a Fav Point and it appears to have been awarded but when cache page is refreshed the point has disappeared. Clearly a geocaching.com programming/database problem, but will this fault affect exiting Fav points caches had accumulated?

Project-GC uses the API, and will get your logs unformatted. Project-GC will still read **FTF**. MyGeocachingProfile requires you to upload your "My Finds" PQ, which also contains unformatted logs. MyGeocachingProfile will still read **FTF**. Thanks thromfre - that is great news and thanks for quickly putting my mind at rest!! Phew!!

HAS CHANGE TO MARKDOWN DESTROYED TAGGED LOGS WHEN YOU ACHIEVE FIRST-TO-FIND? On the advice of Groundspeak's own stats website "MyGeocachingProfile" and the major stats site "Project-GC", I chose from years ago to tag my first-to-find caches with **FTF**, which now is showing as 'bolded' FTF (i.e. FTF). I will be furious if these two stats sites are no longer able to pick-up my FTFs - I have around 2730 FTFs and FTF hunting forms one of my main pleasures when caching. I appreciated Groundspeak do not acknowledge or care about this sidegame, but a lot of us paying members do enjoy this aspect and wish to have the ability to count them. So, although **FTF** is still showing when editing tagged logs, it is displayed on cache pages as FTF - is this another case of HQ implementing major changes without seeing through all the consequences for the paying membership!!! I am not amused!!!!

On the advice of Groundspeak's own stats website "MyGeocachingProfile" and the major stats site "Project-GC" I chose to mark my first-to-find caches with **FTF**, which now is showing as 'bolded' FTF (i.e. FTF). I will be furious if these two stats sites are no longer able to pick-up my FTFs - I have around 2730 FTFs and FTF hunting forms one of my main pleasures when caching. So, although **FTF** is still showing when you edit logs, it is displayed on geocaching.com cache pages as FTF - is this another case of HQ implementing major changes without seeing through all the consequences for the paying membership!!! I am not amused!!!!

Thought this had stopped a few weeks ago, but I had four new logs today in the UK from following fake cachers - I have deleted the logs: Benny5466 Cummings7634 Reuben1106 Schroeder3485

Two more fake "cachers" opened account 5th September and visited around 17 countries in one day, including one each of my caches: Glass4603 Marshall6053 Unfortunately I tried to see what the link in the log ("gcpro.co.uk") was about, before reading the Groundspeak Twitter advice not to click on it - the URL wouldn't open (error) on an iPad but have I inadvertently downloaded some malware anyway? Mmmmm, don't really know how to check on the iPad!

Went to my first Mega at w/e and happily took part in my first "Lab Cache" - which was bit of a farce TBH, as we just wandered around the showground looking at placed items (e.g. playing cards, skull, lock on a bridge railing full of locks, etc) and at each stage had to think of an associated password. Punched the PW into the "Lab Cache" app, but there was no logbook to sign - I unexpectedly ended up with an additional 10 finds on my profile!! Now I see some geocaching.com stats reflect these "10 Finds" but not other stats - then horrifyingly I found "Project-GC" doesn't show Lab Caches at all, because the data is not included in the API from Groundspeak!!! So now geocaching.com and Project-GC stats do not match by 10 finds. You can delete the Lab Cache "finds" in your geocaching.com profile, but I feel Lab Caches have not really been thought out properly by Groundspeak. Virtuals (which I enjoyed) were removed and illogical Lab Caches brought in instead. Not impressed TBH. Either Lab Caches should be sorted & supported properly and included in the API and MyFinds stats ... or be ditched!

Notifications via iCloud for me in UK, untill tonight, have be fine but three new caches came through g-mail at 21:40 local time but same caches via iCloud e-mails arrived between 22:40 and 23:00. Normally iCloud are quick as they are "push" and g-mail only "fetch". Definitely seems there are problems yet again between Apple and Groundspeak !!!!! Delays today but stopped again by tomorrow?