As explained in this post, my cloud seems to have damaged my project. I tried by removing the temporary files project.tpy-journal and project.tpy-wal while Tropy was closed, but it did not work. Would you be able to restore it for me? Thanks in advance!
If you post the tpy file here we can take a look.
In general though, it’s best if you can restore a previous version of the file from your cloud/sync-history, because even when restoring the database succeeds, it’s not easy to be sure that no data was lost.
Hi inukshuk. Thank you very much for your quick answer. I worked yesterday on this project, and as far as I can see, this is the current version. I downloaded from my cloud. I hope it will work. If you need something else, please let me know. Thanks again for your support.
project_1(2).tpy (4.2 MB)
Here is a copy of the recovered project file. Please make a backup copy of the original and then replace the file with the recovered one. I noticed that this is a standard project in a .tropy folder and that you renamed the project file to project_1.tpy but I would recommend keeping the original name project.tpy instead (if Tropy sees only the project folder, it will assume that name so it’s best to keep this consistent). Once placed in the project folder, double click the recovered file to open it and carefully check if everything was recovered correctly.
It worked perfectly! Thanks a lot for the quick and efficient support. Saludos!
Hello!
Although I stopped the synchronisation after my Tropy project was damaged, the cloud seems to have restarted it after an update. I am now experiencing the same “SQLITE_CORRUPT” problem again. Would you be able to restore the project?
I apologise for the inconvenience and thank you in advance!
Agus
Here is the file. While working on the project, I had an issue when I tried to move a document to a different list, after which I could not find it again. I hope I have just misplaced it.
project.tpy (160 KB)
I’m afraid this file can’t be reasonably restored. Is it supposed to be the same project? Because this file is only 160kb while the previous one was over 4MB which might explain why it can’t be restored.
Hi! I thought I had already answered your comment. Yes, there are somehow two project files. I’m sending you both here.
Hopefully this works! Thanks a lot!
project.tpy (160 KB)
Here is a recovered version of the file. Please note, however, that it would be better to recover the version from before the conflict happened from Dropbox. The conflicted version is a file created by Dropbox if it notices that a file could not be synced because the remote and local versions were both modified. This typically happens if you use the file from multiple devices at the same time or if you keep the file open in Tropy while Dropbox syncs it.
Dear Inukshuk,
Thank you very much for fixing the project once again. Unfortunately, I was unable to download it in time, and the link has expired.
I would greatly appreciate it if you could send me a new link.
Please forgive me for asking for your help again.
Thanks in advance!
Agustina
Sure, here is a new link (though, like I said, it would be better to restore the original version from your Dropbox).
Thank you very much! I was able to download, open and save the file in an unsynced folder. The ‘original’ version on my cloud is only 160 KB (I have my own cloud and use Nextcloud). So it wouldn’t work.
The problem I am experiencing now (which actually happened before my database became corrupted for the second time) is that when I try to put a document in a subfolder, it sometimes disappears. I cannot trace it back. They are not in the trash. I have only found some JPGs in the assets folder.
Could you help me with that too?
Thanks,
Agustina
Please be more specific, otherwise it’s difficult to tell what’s going on: when you put a document in a subfolder it disappears – do you mean you put an item in Tropy into a nested list? Or that you put a file into a subfolder in your file manager? I can’t really comment on the latter, but if you mean that the item disappears in Tropy it could be that you have a tag selected or a search query entered – in both cases items that don’t match wouldn’t show.