-
-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accepted Visits are not remembered #848
Comments
Seeing this on my install as well. Docker, version 0.24.0. |
I have the same with version 0.24.1 |
I can confirm this behaviour: all of my 941 confirmed visits reappeared the next day, which is rather annoying as there is apparently no way to confirm all visits for a location in a hurry (also on version 0.24.1, docker install). |
Is this issue still persists on 0.25.1? |
Hm … as I was still on 0.24.1 and - triggered by your post - just pulled the latest image, I received the following what made me reset my container to latest backup Therefore: I cannot confirm if the behaviour still resists the same as mentioned! :-( Update 2025-03-18, 09.57.22: After now considering the advise in the 0.25.0's release note to perform "Visit.suggested.destroy_all" in console, I receive also the following screen after LogIn similar to the ongoing discussion on Discord Will now stop here and join the discussion over there if an issue is opened by someone (as I'm not experienced in driving any topics on GitHub) |
OS & Hardware
Docker
Version
0.23.6
Describe the bug
When I "Confirm" a visit, it shows up in confirmed. Next day (?), (not after logout and login), they are no longer in Confirmed but in "Suggested"
To Reproduce
Just go to Suggested visits and press confirm. Wait for next day.
Expected behavior
Once confirmed visits should be kept unless manually deleted/Declined.
The text was updated successfully, but these errors were encountered: