toz/MediLog
9
51
Fork
You've already forked MediLog
3

No more prompting for backup #533

Closed
opened 2025年06月23日 11:38:59 +02:00 by Hermann · 4 comments

Hi,
yesterday I realized that it has been some time when MediLog would prompt for a backup. The last backup was in mid-May 2025.
The interval for reminders ("Sicherungs Warnung") is set to 7 days. Using version 3.2.7

Hi, yesterday I realized that it has been some time when MediLog would prompt for a backup. The last backup was in mid-May 2025. The interval for reminders ("Sicherungs Warnung") is set to 7 days. Using version 3.2.7
toz added this to the 3.2.8 milestone 2025年06月23日 16:48:03 +02:00
Owner
Copy link

Looks like this check went missing for some reason. Can you let me know what you got in /Settings/Backup/Automatic Backup, if anything?

Looks like this check went missing for some reason. Can you let me know what you got in /Settings/Backup/Automatic Backup, if anything?
Author
Copy link

This setting is unset/empty

This setting is unset/empty
Owner
Copy link

Ok, as expected, thanks.
Fixed at my end, I'll publish a beta in the next couple of days.

Ok, as expected, thanks. Fixed at my end, I'll publish a beta in the next couple of days.
Author
Copy link

Thanks for the quick response and correction. Great piece of software!

Thanks for the quick response and correction. Great piece of software!
toz modified the milestone from 3.2.8 to v3.3.0 2025年06月30日 12:47:15 +02:00
toz 2025年07月17日 19:52:28 +02:00
Sign in to join this conversation.
No Branch/Tag specified
main
3.6.0
3.3.8
master
v3.3.2
v3.2.7
v3.2.5
v3.2.1
v3.2.0
v3.1.2
v3.1.0
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v2.7.4
v3.0.3
v3.0.1
v3.0.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.3
v2.6.2
v2.6.0
v2.5.11
v2.5.10
v2.5.9
v2.5.8
v2.5.7
v2.5.6
v2.5.5
v2.5.4
v2.5.3
v2.5.2
v2.5.1
v2.5.0
v2.4.8
v2.4.7
v2.4.6
v2.4.5
v2.4.4
v2.4.3
v2.4.2
v2.4.0
v2.3.5
v2.3.4
v2.3.3
v2.3.2
v2.3.1
v3.7.1
v3.6.5
v3.6.4
v3.6.3
v3.6.2
v3.6.0
v3.5.1
v3.5.0
v3.4.1
v3.4.0
v3.3.11
v3.3.10
v3.3.9
v3.3.8
v3.3.7
v3.3.6
v3.3.5
v3.3.4
v3.3.3
v3.3.2
v3.2.7
v3.2.6
v3.2.5
v3.2.4
v3.2.3
v3.2.1
v3.2.0
v3.1.2
v3.1.1
v3.1.0
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v3.0.3
v3.0.2
v3.0.1
v3.0.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.3
v2.6.2
v2.6.1
v2.6.0
v2.5.11
v2.5.10
v2.5.9
v2.5.8
v2.5.7
v2.5.6
v2.5.5
v2.5.4
v2.5.3
v2.5.2
v2.5.1
v2.5.0
v2.4.8
v2.4.7
v2.4.6
v2.4.5
v2.4.3
v2.4.2
v2.4.1
v2.4.0
v2.3.5
v2.3.4
v2.3.3
v2.3.2
v2.3.1
v2.3.0
v2.2.5
v2.2.4
v2.2.3
v2.2.1
v2.2.2
v2.2.0
v2.1.2
v2.1.1
v2.1.0
v2.0.6
v2.0.5
v2.0.1
v3.7.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
toz/MediLog#533
Reference in a new issue
toz/MediLog
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?