I left Evernote because (1) local mode was no longer supported which in turn (2) left unresolved an issue which made notes disappear and hoped that Joplin would be safe in this respect...
I'm only using one single installation of Joplin in local mode, synchronising only to file system for backup purposes with encryption (because I wanted to eventually synchronise to the Joplin server).
While using a backup utility to back up files (FreeFileSync) I became aware that Joplin had unwarranted deleted a lot of files. I went through my notes and noticed that several embedded pictures/attachments were deleted (that's exactly the deleted files flagged by the backup utility). Tags were also removed from notes and I cannot rule out that some notes have been deleted.
Now, is this a known problem? Because if it is, I'm going to quit Joplin for good.
I often use the Tools>Note attachments function to manually remove attachments but, of course, I never deleted the attachments I wanted to keep. Is there possibly a bug in the "Note attachments" option that corrupts the attachments database?
I don't seem to find scenarios like this one in previous posts.
Thank you for reporting this! I don't think that this is a known issue.
Joplin should keep a log with information about why items are deleted. To find this:
Copy the ID of a deleted resource.
For example, if the Markdown for an incorrectly deleted image was ![test](:/43556aa4aa5142fb9b7295e35f673233), then the resource ID is 43556aa4aa5142fb9b7295e35f673233.
Open Joplin's log file.
"Help" > "Open profile directory" should open the folder containing the log file.
If you use just one profile, the log can be found at C:\Users\UserNameHere\.config\joplin-desktop\log.
If you use multiple profiles and the profile with the issue isn't the default, the log can be found at C:\Users\UserNameHere\.config\joplin-desktop\profile-id-here\log.
Search for the resource ID.
Screen recording
Lines corresponding to the resource deletion should contain the resource ID, title, and reason for deletion. For example, if I manually delete a resource's metadata from the sync folder, the logs look like this: