githu issue
It happened when I used api PUT /folder/:id to modify the parent_id of the directory
What I want to know the most is how to restore my data, because Joplin can't be opened (as shown above)
Environment
Joplin version: 1.0.199.2381
Platform: Windows
OS specifics: Windows 10
Steps to reproduce
- Use
PUT /folder/:id and pass the parameter {id:'', parent_id:''}, where parent_id is the child of id
- The entire program is stuck, and exiting and re-entering will not help, it looks like it has encountered a fatal logic error (I guess Joplin did not deal with this edge situation)
Describe what you expected to happen
- When I call the API
PUT /folder/:id for this illegal operation, an exception should be thrown for prompting!
- If possible, please package the beta version, one for daily use, and the other beta can be developed and tested, otherwise it is quite dangerous, such as the current situation
Logfile
log.txt
Hello @rxliuli
I don’t know what your screen shot is showing.
The best solution would be to wipe your Joplin installation and restore from backup!
However, if you don’t have a backup, your data might be recoverable in your Joplin database.
Note, the following is just a guess because I haven’t tried to recreate the problem, so I haven’t seen how the database is corrupted, or even if it is corrupted.
So assuming the folder id was actually set to empty string, you would need to fix the id for the folder in the folder table. If you don’t know what the id was, you might be able to find it by looking at the parent id of a note that was in the folder. Otherwise you could try entering a new random id, but then you would need to update the parent_id of all the children notes to match. Be careful about syncing after doing this. I wouldn’t sync with any other installations, instead remove them and set them all up again.
Also, if you are sure this happened as you describe, it is a bug, and it would be good to create an issue in github so it is fixed.
It exploded and it was synchronized several times. . .
In the end, I solved this problem by directly editing the sqllite database, but to be honest, the synchronization feature did a terrible job (the first time I synced a large number of files…)