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

Backup file for new installation has to be restored, can't be imported #549

Closed
opened 2025年08月10日 20:54:50 +02:00 by hj.beckers · 3 comments

I have uploaded two png files showing the difference.

In Medilog_import_error_2025年08月10日_20-34-26_2076.png the backup file is not selectable (not highlighted).
In Medilog_Restore_Working_2025年08月10日_20-36-33_2240.png the file can be selected and is correctly imported.
For me it looks like zip files are not allowed in the import call.

Do You use internal read/write functions or do You relay on system routines? Maybe the error is on my side using an alternate file manager? I'm using the latest beta version.

Thread forked from #542

I have uploaded two png files showing the difference. In Medilog_import_error_2025年08月10日_20-34-26_2076.png the backup file is not selectable (not highlighted). In Medilog_Restore_Working_2025年08月10日_20-36-33_2240.png the file can be selected and is correctly imported. For me it looks like zip files are not allowed in the import call. Do You use internal read/write functions or do You relay on system routines? Maybe the error is on my side using an alternate file manager? I'm using the latest beta version. Thread forked from https://codeberg.org/toz/MediLog/issues/542
hj.beckers changed title from (削除) Backup file for new installation has to be restored, can't be impored (削除ここまで) to Backup file for new installation has to be restored, can't be imported 2025年08月10日 20:56:34 +02:00
Owner
Copy link

Can't download the images just yet because I am behind a very slow internet connection, but from what you wrote this may just be a misunderstanding?

  • "Restore" is for restoring a backup file created by MediLog, and it should work between versions. Restore is expecting a ZIP file.
  • "Import" is for third party imports, cases where you prepared a CSV file from e.g. a different app. Import will only accept CSV text files.
    Which means that if you want to try the beta with your live data you create a "backup" in your production version and "restore" in the beta version.
Can't download the images just yet because I am behind a very slow internet connection, but from what you wrote this may just be a misunderstanding? - "Restore" is for restoring a backup file created by MediLog, and it should work between versions. Restore is expecting a ZIP file. - "Import" is for third party imports, cases where you prepared a CSV file from e.g. a different app. Import will only accept CSV text files. Which means that if you want to try the beta with your live data you create a "backup" in your production version and "restore" in the beta version.

Well, then its just a misunderstanding. But you should change the wording on the beta-donwload site:

Start the the beta
Import your backup
-->
Start the beta
Restore your backup

You can close both issues.

Well, then its just a misunderstanding. But you should change the wording on the beta-donwload site: Start the the beta Import your backup --> Start the beta Restore your backup You can close both issues.
Owner
Copy link

Indeed! Just did.
Thanks for bringing it up.

Indeed! Just did. Thanks for bringing it up.
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#549
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?