itscharttime

Yep, I felt like reporting a bug now that I’m no longer fixing em haha. Hope y’all are doing well!

Hi, I'm having an issue uploading images via the profile description edit WYSIWYG. The call to upload the image is 404ing and giving me a dialog with an error message, as seen in the screenshot below. I've tried multiple images in multiple formats to no success.

I ran the solution checker input through our internal geocoder service, which takes the following formats listed on the help center: https://www.geocaching.com/help/index.php?pg=kb.chapter&id=128&pgid=811. The underlying check is converting the input to DDM and checking that value against the final waypoint DDM coordinate.

The update is now live for the Submit for Review modal to detect pasting content. Please let me know if this doesn't fix your issue.

Thanks for reporting this. We'll get a fix out shortly to detect pasting content.

Hi caviar42, Are you entering text into the reviewer note text area? By design, the button will remain disabled until content is detected. This is because the reviewer note is required when submitting for review. I suspect this to be the issue since you've tried it on multiple browsers.

This statement is concerning. How is there any difference in code/functionality for the same component/function used in different areas? We've been told the main driver for all this change is correcting years of coding changes that slowed development and was error prone due to complexity and redundancy. The same enhancements and defects must still be addressed in multiple places. The way understand it may be... if the edit is more of a direct data modification, which isn't using the API (at least in the same way) as submitting a new log. Eventually, the edit function may be 'updated' to work with the same system the new log page uses, but right now, with the edit feature not in the same api space as the new log, even though the data ends up in the same storage, the filtering would be different for both (to aid with rolling out more modularly). And if they're rolling out page by page, desiring to leave the log Editing until the New log is acceptably sufficient, then the content filtering will be different until that point. Sort of like they have logging interface V1 (the old new & edit pages), V2 (the current edit page, which gained markup recently), and V3 (the New log page). Each took submitted data and saved it to the same final location, but each had different content filtering code. Presumably, the ideal to eventually move the current log editing page to the V3 interface, at which point both new and edit will apply the same tagging/filtering/notification functions. That's how I'm grasping their process anyway. This is pretty close to the reasoning for not adding mentions to the edit page. When we released the new log page, we overhauled (most of) the legacy systems that post logs to the DB and the edit log page hasn't been updated to leverage the new services yet. That project is not up to one person to decide so I don't have an answer for when that might be done at the moment. To clarify my answer about the use case for mentions: Tagging friends that you've found caches with was the original intent that spawned the idea of mentions. This is by no means the official use case of mentions. I anticipate the community to use this optional feature in any way they want.

The idea is to be able to tag friend(s) if you're geocaching in a group. Take this example: two people were geocaching together, but only one person could record which geocaches were found. The person recording could mention the other in all their logs. The person who was not recording can now easily see which caches they found together(and log em of course!).

Thanks for the feedback! Here's some information to answer some of your questions. We'll look into adding notification settings to disable mention notifications. We'll look into disabling mention notifications by default for non-cache owners and non-reviewers for unpublished caches. We only display 10 friends at a time. This is to avoid cluttering the page with a giant list of friends. In order to filter down the list, continue typing your friend's username and it will filter down. I've jotted down the idea to look into displaying most recently mentioned friends first. There are no current plans to add mentions to the edit log page. This may change in the future, but is not in high priority.

Thanks for the quick feedback! We're definitely looking into settings to turn off notifications for these emails. I can't promise a timeline, but we're hoping to update this relatively soon.

Hi vw bus, Could you elaborate on what isn't working? If the dropdown list isn't appearing, check if you have friends added here: https://www.geocaching.com/my/myfriends.aspx. The dropdown will only populate with your friends. If the dropdown is appearing, you'll need to explicitly select a user to mention by either clicking from the dropdown or navigating the dropdown with arrows keys and hitting enter on the selected user. You'll see a background color change on your log text to indicate that a mention is recognized.