From c0dd5b0152b2fc71b6257377dc9607fe1e63c312 Mon Sep 17 00:00:00 2001 From: zadam Date: Fri, 5 Jun 2020 09:21:52 +0200 Subject: [PATCH] Updated Troubleshooting (markdown) --- Troubleshooting.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index 5aaa538..ee855c8 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -36,12 +36,10 @@ Trilium logs important events and errors into `logs` directory (inside [[data di In some cases it's necessary to see the database structure to be able to debug the problem. Of course we can't ask you to send us your [[document|Document]] file with your notes. -For this Trilium supports anonymization of the database - you can trigger this in Settings -> Advanced tab. +For this Trilium supports anonymization of the database - you can trigger this in Options -> Advanced tab. This will create a copy of your document and remove all sensitive data (currently note titles, contents, revisions, history and some of the options) while leaving all structure and metadata (e.g. date of last change). After this is done, database is [VACUUMed](https://sqlite.org/lang_vacuum.html) to make sure there's no stale sensitive data in the document file. Resulting file is stored in `anonymized` directory (placed in the [[data directory]]). You can safely attach it with your bug report. -Note that [[attributes]] are not cleared because they can contain important metadata for debugging. - #### Command line anonymization If the database is corrupted in a way which prevents Trilium to start up, you won't be able to trigger the anonymization from the UI. For such a case, anonymization is also available from command line: