Jump to content

capoaira

+Premium Members
  • Posts

    729
  • Joined

  • Last visited

Everything posted by capoaira

  1. Ok, I research a bit and now I remember what the problem was. My email was not verified but could @Moun10Bike soved it: Sine I delete my 2nd email address (few days ago) it appears again, so may my first is again not verified? (I receive mails for logs, notifications, PQs, etc anyways). So I would assume that the bug is in the email verification.
  2. This bug appear since serval years and it was reported multiple times. I thought a while that it has been fixed, but it hasn't. Since I remove my second email address, the bug appears again. So I would assume, that the error is caused by the broken email input on PQs and notifications. (If you only has one email address) It is a really annoying bug, but i gave up to hope that it will be fixed : ( Error 500 normally means "Internal Server Error", so the clients system doesn't matter. It is an error on server side whitch should never happen in a production release.
  3. Oh no, that is definitely a step in the wrong direction. We all wish to see more (=all) caches not less : ( I thought For me that is major functionality update (or more a downgrade)
  4. I cannot confirm that. It is only summarized, if the cacher has a lot of finds on that day. If the friend has only a few caches found on that day, it shows each log.
  5. Sometimes there is a delay between the lab page and geocaching.com. So hopefully you just have to wait a day or so.
  6. I understand, that people who living in an area with not so much other cachers, are disappointed, that they haven't a real chance to attend a block party. But in the end, it is just the icon, like a mega or giga icon - or a tradi, multi or unknown. Its just a thing for the statistics. You can celebrate 25 year's of geocaching also with smaller events. There are no difference between an event and block party except the icon and the number of visitors.
  7. Maybe, Maybe not. It depends on the bug. If you can explain a bit more, someone here can may help you to avoid the problems with android.
  8. Für mich hört es sich so an, als wäre die App abgestürzt, bevor der "Fund" markiert wurde, jetzt ist es nicht richtig synchronisiert. Ich würde Folgendes empfehlen: Ab- und wieder anmelden Wenn das nicht funktioniert: Die Daten der App in den Telefon-Einstellungen löschen und dann wieder anmelden. Das sollte den Fehler beheben, da die Daten online richtig sind und so erneut geladen werden. Wenn du bei den Abstürzen ein Muster erkennst, solltest du dieses mit deinen Telefondaten (Modellname, Betriebssystem, -version) im englischen Teil des Forums melden, damit der Fehler gefixt werden kann.
  9. You have to put the message into the input logic.
  10. You can activate the https only mode in your browser, then I think the behaviour is like the TO describe. If you don't have that mode activated, your browser will check both, https and https
  11. Von beiden Problemen habe ich im englischen Teil des Forums gelesen, und Groundspeak weiß um die Bugs. Problem 1 gibt es schon eine ganze Zeit, Problem 2 gibt es seit dem neuen Logging flow. Vielleicht einfach nochmal melden damit das in der Priorisierung weiter hoch rutscht? Leider hat alles, wo es workarounds gibt, keine hohe Priorität bei GS :-(
  12. Yes, it's annoying for me too, and I complained about it right when the new map was introduced. As a workaround, you can use the GClh (https://github.com/2Abendsegler/GClh#readme) which is a really useful and powerful extension. It runs in Tampermonkey (is like Greasemonkey) One of its many features is the possibility to show found (and own) caches by default. It's sometimes a bit buggy, and you have to zoom a bit out and in, so that the changes by GClh made are applied. You can enable/disable all feature in a config menu, which you can reach over the dashboard, once you install Tampermonkey and the GClh
  13. Ich habe mich seit meinem erstem Post hier zurück gehalten. Denn keiner hier kann mehr tun, als dir zu empfehlen das HQ anzuschreiben. Die Art wie mit dir hier umgegangen finde ich nicht richtig, wie du aber auf deinem Standpunkt beharrst aber auch nicht. Wenn es dir wirklich so wichtig wäre, hättest du schon längst das HQ angeschrieben und nicht nur diskutiert. Den Wunsch das Thema hier zu schließen unterstützen ich. Wenn eine Diskussion zu nichts führt, weil keine Partei bereit ist, die Argumente des Anderen richtig anzuhören, sollte man aufhören oder zumindest eine Pause machen.
  14. Is the task easy, or is there none? Please don't place a Wherigo just to have one in your hide statistic. If you want to create a Wherigo, use the possibilities of it, like zones, massages/dialogs, inputs. Otherwise, hide a puzzle or a traditional. WIGs have so much potential, but the value of the type decreases simply because of all the reverse caches, which are basically just a different coordinate format. I don't need another random "Oh I want a WIG in my statistic"-Wherigo.
  15. I hope I misunderstood the question. Did you really want to just give the koords in the WIG without any task, puzzel or story?
  16. Du könntest dich ans Helpcenter wenden. Die Menschen in der Ukraine haben aber mit Sicherheit andere Probleme als ein paar Plastikdosen.
  17. There is a bug, also in the search, that some found caches are marked as draft. It looks like it is random.
  18. When your log was deleted without a real reason, you can contact the help center. They can also see deleted logs and can restore them. (Images goes lost on this process, I think that is a bug)
  19. Als ich vor einigen Jahren PGC Premium hatte konnte ich mich über Event mit einer gewissen Anzahl an Logs benachrichtigen lassen. Eine entsprechende Suchfunktion konnte ich jedoch auch nicht finden.
  20. Ich würde noch ergänzen, dass ich keinen Behälter finden möchte, der mit Watte beklebt ist. Draußen kann es ja auch mal Regen und dann ist das schon unangenehm.
  21. I usually use Drafts for logging, so the logtype is mostly correct. So when I log directly from the logform, than I log a note. For example, if I don't have time for an event. If I log this on the same day as the event, I often forgot to change the log type. Yes I can change that when I recognise the mistake. But that was more difficult when I logged accidentally an attend instead of a note for an event in which my TB was lost. I got a Region Souvenir because I haven't visit the Region before. So I had to write the Help Center to remove the it. I'm caching since 9 years so it is not only to prevent newbies from posting the wrong log. Also cacher like me, who usually use Drafts where the logtype is set correctly. A simple workaround for all cacher who's annoyed from choosing the logtype: Use Drafts. You can use it from every app and also from Garmins.
  22. Since the new design of some pages (Map, Bookmark, Search, ...) these actions (Found, NM, Owner maintenance) have a delay. I wonder that the modern code has a delay and the older not. In Germany, we say "verschlimmbessern" (make something worse, when improve it)
  23. But less annoying mails for Owners. Many Cachers (my experience as cache owner) had forgotten to check the "Report a Problem" button and therfore logging their found and after that, a Note with the NM. I'm happy that it is now possible again to log an OAR (aka NM) as standalone, where the description of the problem is actually in the log.
  24. Wir sind dran :-) Da man mit dem richtigen Link das neue Design schon nutzten kann, auch wenn man nicht auserwählt wurde, können wir so gut wie alle Funktionen einbauen, außer die, die die Drafts berücksichtigen. Wenn uns jemand sagen kann, wie der Link aussieht, wenn man von den Drafts kommt, wäre das sehr hilfreich. Dann haben wir die Möglichkeit, auch daran schon zu arbeiten.
×
×
  • Create New...