LivingInNarnia

Thank you for reporting and sharing details - we're working on resolving this and will provide updates as soon as we have them. Thanks!

Thanks for letting us know - we pushed out a fix that should solve this very unwelcome issue. (Refreshing the page and/or clearing the cache in your browser should also help.) We're keeping an eye on this problem, please let us know if you continue to have trouble! Thanks!

Thanks for sharing the information TeamBikeFast. We tested with the files you shared. We were able to see the comments on the caches on the new logging page (the older page does not display a preview of the log) - have you tried this with a new field note with text? Noticed that the comment in your text file “Tidal Bore. Burnt Cove Head” is on the event cache GC72QAE and not the Earthcache GC3XEHV (if that was intentional or not, I’m unsure). We’re not able to reproduce an issue with uploads: Uploaded the text file with only the dates from July on the old field notes page - as if we were uploading ‘last week’. To test, only 1 cache was logged. Logged the cache from July 19th from the old field notes page in the new logging page. Uploaded the entire file - all July and August dates (including the July 19th text file) - as if we were uploading ‘this week’: Uploaded to the new drafts page. The logged cache (July 19th) was not uploaded and does not appear on the new drafts page or the old field notes page. Uploaded to the old field notes page with the “ignore logs before 8/4/2017” checked. The logged cache (July 19th) was not uploaded and does not appear on the new drafts page or the old field notes page. Uploaded to the old field notes page WITHOUT the “ignore logs before 8/4/2017” checked. The logged cache (July 19th) DOES appear, because the checkbox is essentially giving permission to upload everything, despite any past uploads. Perhaps you are using the old field notes page without checking the “ignore logs”? If you are using the new drafts page, any previously logged caches will not be uploaded. Without more information and more detailed steps I’m afraid I can’t provide you with more assistance.

Thanks for the feedback. Could you provide a little more information to help the team understand the potential issue? Would you mind sharing the field note files you uploaded - the file used last week and the file used this week. What is the exact Garmin device you are using? Were any files modified at some point? Did you use the old field notes page at any point in your process? Or only the new Drafts page? Thank you!

Thanks for the feedback - it's not something we're looking into right now, but I will make sure that we explore this when we do!

We have no plans to remove any existing content in the current "Name" section - for now, we'll be making minor tweaks based on feedback from the new photo description updates.

Thanks for clarifying - It sounds like you’re suggesting we change where we have added photo descriptions from the “Notes” section to the “Name” section. We decided descriptions will appear in the “Notes” section for a couple reasons including because as you noted there is a longer character limit here. With the addition of photo descriptions to the new logging page, a player would ideally only need to visit this old editing page for edits (!) when needed (nor would the old upload image page be needed to add photo info as was the case in the past, and which required players to choose from 1 of 2 text entries, or both). We have made updates to the cache details page so that the old “Notes” section (the new photo description section) will display if there is no “Name” so players can see any content associated with a photo on the C/D logs. And we will look into how content could appear in the galleries moving forward. It's pretty clear as I mentioned earlier that our old photo editing process is a little dated we're working on trying to make it a consistent and clear experience with the new additions we're making to the site!

Thanks for the tip! Still adapting to the new forums

Thanks for the feedback, replies inline above!

That was unintentional Thanks for letting us know, this should be resolved now. However, photos that were uploaded in the past couple hours will continue to have the fuzzy image. To correct the issue, the photo will need to be re-uploaded.

It does not currently apply to photos submitted through the API but we're looking into it - thanks for asking!

It depends on how you define "invalid". I've seen the behaviour you described when I've done a silly thing like putting a " in a field note comment on my Garmin, which understandably causes the parsing to fail. However, I know I still have some non-GC codes and "Unattempted" records in my geocache_visits.txt file, and the old parser was and still is happy with simply ignoring those records and continuing on. This isn't how it worked for me on Sunday. I'll double-check when I get home, but I'm pretty confident the first record in my file is valid, and the site still didn't accept my file. Was there an issue that has since been fixed? re the new system handling failing/invalid records: Correct, we made an update earlier this week to make this fix!

To clarify some of the complexity, and hopefully answer some questions, around uploading and deleting with the new and old drafts system, I’m attempting to provide an overview below Please let us know if there are any additional questions. How the old system detects duplicates: Keeps track of the greatest visit date (typically, the most recent; could be a future date) of any upload drafts on the account; gives the user the option to only upload logs with a visit date greater than that date. (If user unchecks “ignore logs” then you can upload those.) How the old system handles failing / invalid records : Any bad records in the file will cause the erroneous record as well as any following ones to be ignored. How the old system handles deleting records: The option to “clear all drafts” completely removes all drafts from the system for the user and clears the “greatest visit date” resulting in all drafts to be uploadable again whether or not they were “deleted” or “converted to a log”. “Bulk Delete” and single delete, will delete the records however they could be uploaded again if the “ignore logs” is unchecked. How the new system detects duplicates: The “Upload drafts” functionality from the new page detects duplicates based on the combined values of the Geocache Reference Code (GC Code), the date/time of the visit as well as the log type. Any drafts previously uploaded to the system (via the legacy drafts page or the new drafts page) will be ignored if the draft was subsequently deleted or promoted to a log. The only exception to this rule is if records were deleted via “clear all drafts” on the old page as we then no longer have any records of those drafts having ever existed. How the new system handles failing/invalid records: If the first record in the file is valid, then any following invalid records in that file will be skipped (bad GC code, bad format, etc). If the first record in the file is invalid, then the user will receive an incorrect file warning with the name of the file. How the new system handles deleting records: Users have the option to “Delete All” or delete individual records. These files cannot be uploaded again on the new logging page. Why we moved to a new system: Now that we are handling drafts from mobile and web, this new way of handling duplicates is more robust. It allows us to not just rely on date to determine duplicate logs but also GC code and log type. TL;DR we can identify duplicates more accurately.

Thank you very much for the thoughtful and thorough feedback. We are continuing to make improvements based feedback from the community, stay tuned for updates!

This should be resolved now, please let me know if you continue to have issues. Thank you for sharing!

Sorry for the late reply, but here we go ... I uploaded the field notes file to my private webspace, link is http://www.parsch-online.de/temp/geocache_visits.txt. But as I said in my original posting, the culprit is the two lines starting with "OC". As soon as I remove these two lines, the file is loaded without problems. I assume, the new parser expects the waypoint to start with GC and nothing else. The old parser behaved better (from a user's point of view) by simply ignoring such lines. Thank you! We've received a few comments about uploads having issues; we're looking into it and will let you know when resolved. This should be resolved now, please let me know if you continue to have issues.

Sorry for the late reply, but here we go ... I uploaded the field notes file to my private webspace, link is http://www.parsch-online.de/temp/geocache_visits.txt. But as I said in my original posting, the culprit is the two lines starting with "OC". As soon as I remove these two lines, the file is loaded without problems. I assume, the new parser expects the waypoint to start with GC and nothing else. The old parser behaved better (from a user's point of view) by simply ignoring such lines. Thank you! We've received a few comments about uploads having issues; we're looking into it and will let you know when resolved.

Hi baer2006 - Thanks for sharing this feedback about the upload failing. Would you mind sharing the text file that was having the issue? (If you have more than one example even better, it will help the devs figure out the issue faster) thank you!

Thank you for the thorough and helpful feedback! Our team is reading and discussing every response. We’re looking into the reported bugs first and we will get back to you as soon as we have updates.

Hi thomfre, Awhile back we discovered an unfortunate bug with the markdown converter. Rather than to fix and continue to support the markdown converter, we have indeed removed it from the site. There are a few tools available online that could be of help should you want to convert logs moving forward.

Thank you for sharing the problem. We worked quickly to resolve the issue and this should be fixed now. Please let us know if you continue seeing the wrong date, thank you!

You did. BUG: Accidentally Select Drop, Change to Visit, TB still gets Dropped Yes, that was me that posted that there as well. I wanted to cover all my bases. This has been fixed! Thanks for reporting Sherminator18.

This has been fixed! Thanks for reporting Sherminator18.

We're aware that this issue is happening for a subset of our users and we're looking into resolving it, thank you!

In case you missed it, we outlined a few reasons why we created a new logging page in the blog post. Below is an excerpt, you can read the entire post here. Thank you for continuing to share your feedback! “We know that change has been prevalent here at HQ lately, and that it is not always easy. Now in our 17th year, we are addressing some growing pains that only come with being a game nearly two decades old. Namely, old code. Much of the website is unable to support the features today’s geocachers want and need, such as adding a favorite point and photo to a draft on Geocaching.com. Building a new logging page allows us to incorporate more robust features, respond faster to your feedback and any problems, localize our content to reach more geocachers, fix timezone issues, and make Geocaching.com mobile responsive. “